Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add meshery docker extension #2870

Closed
YashKamboj opened this issue Jun 7, 2022 · 3 comments · Fixed by #2877
Closed

Add meshery docker extension #2870

YashKamboj opened this issue Jun 7, 2022 · 3 comments · Fixed by #2877
Assignees
Labels
component/ui Issues related to UI kind/chore Necessary task

Comments

@YashKamboj
Copy link
Contributor

YashKamboj commented Jun 7, 2022

Current Behavior

Meshery docker extension is missing from the list

Desired Situation

Add meshery docker extension on [layer5.io/projects](https://layer5.io/projects)

[Optional] Alternatives

[Optional] Additional context


Contributor Resources

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

@YashKamboj YashKamboj added kind/chore Necessary task component/ui Issues related to UI labels Jun 7, 2022
@YashKamboj YashKamboj self-assigned this Jun 7, 2022
@Nikhil-Ladha
Copy link
Contributor

But, it is a part of Meshery itself. Not a separate project 🤔

@YashKamboj
Copy link
Contributor Author

@Nikhil-Ladha @leecalcote told me to do it

@leecalcote
Copy link
Member

@Nikhil-Ladha has a good point. I had wondered this myself, but figured that we would list it as some of the other projects are also sub-projects (e.g. SMI Conformance, Service Mesh Patterns ) like the Docker Extension is. I figure that we might as well toot our own horn and that we should point people to this easy deployment method of Meshery when we can. What do you guys think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/ui Issues related to UI kind/chore Necessary task
Development

Successfully merging a pull request may close this issue.

3 participants