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.

Sign up for GitHub

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

Jump to bottom

About k8s apiVersion backward compatibility policy in Vald project. #946

Closed
kpango opened this issue Jan 22, 2021 · 0 comments
Closed

About k8s apiVersion backward compatibility policy in Vald project. #946

kpango opened this issue Jan 22, 2021 · 0 comments
Labels
area/helm area/internal priority/medium status/draft status/help-wanted status/proposal team/core Core team team/set SET team team/sre SRE team type/feature New feature type/suggestion Suggestion

Comments

@kpango
Copy link
Collaborator

kpango commented Jan 22, 2021 •
edited
Loading

Is your feature request related to a problem? Please describe.:

[feature request & discussion]

As we discussed in #945, I think similar problems will occur not only in our environment, but in many user environments and cloud providers in the future.

Describe the solution you'd like:

I thought we should set a rule for the Vald's k8s apiVersion support and support at least two apiVersions in our Helm Chart, internal/k8s components.
To discuss this, I bring up this issue, please let me know what you think.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/helm area/internal priority/medium status/draft status/help-wanted status/proposal team/core Core team team/set SET team team/sre SRE team type/feature New feature type/suggestion Suggestion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kpango