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

Making MeshSync Dynamic: Fingerprinting (What negative ramifications are involved in removing the “v1“? Any? If not, please do.) #122

Open
leecalcote opened this issue Apr 14, 2022 · 2 comments
Labels
issue/willfix This issue will be worked on kubernetes

Comments

@leecalcote
Copy link
Member

What negative ramifications are involved in removing the “v1“? Any? If not, please do.

Originally posted by @leecalcote in #120 (comment)

@stale
Copy link

stale bot commented May 29, 2022

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 May 29, 2022
@theBeginner86 theBeginner86 added the issue/willfix This issue will be worked on label Jun 5, 2022
@stale stale bot removed the issue/stale Issue has not had any activity for an extended period of time label Jun 5, 2022
@trupti2003
Copy link

I wanna work on this issue how can i ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/willfix This issue will be worked on kubernetes
Projects
None yet
Development

No branches or pull requests

3 participants