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

Support Kubernetes resource types in MeshSync #225

Closed
21 of 29 tasks
Aritra8438 opened this issue Aug 18, 2023 · 3 comments · Fixed by #231
Closed
21 of 29 tasks

Support Kubernetes resource types in MeshSync #225

Aritra8438 opened this issue Aug 18, 2023 · 3 comments · Fixed by #231
Assignees
Labels
issue/stale Issue has not had any activity for an extended period of time kind/enhancement Improvement in current feature

Comments

@Aritra8438
Copy link
Contributor

Aritra8438 commented Aug 18, 2023

Current Behavior

Currently, MeshSync supports a few resource types:

Desired Behavior

There are many that we need to add support for:

  • EndPointSlice
  • CronJob
  • ReplicationController
  • APIService
  • StorageClass
  • VolumeAttachment
  • Event
  • EventSeries
  • Binding
  • ClusterRole
  • ComponentStatus
  • ResourceQuota
  • Role
  • IngressClass

And there are many more to add, will update this list as we go on adding.

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

@Aritra8438 Aritra8438 added the kind/enhancement Improvement in current feature label Aug 18, 2023
@Aritra8438
Copy link
Contributor Author

Aritra8438 commented Aug 18, 2023

// @leecalcote, will you review and assign me? :3

@stale
Copy link

stale bot commented Oct 11, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the issue/stale Issue has not had any activity for an extended period of time label Oct 11, 2023
@stale
Copy link

stale bot commented Oct 21, 2023

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

@stale stale bot closed this as completed Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/stale Issue has not had any activity for an extended period of time kind/enhancement Improvement in current feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant