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

Make it easier to upgrade from ancient (pre v0.9.0) controllers #466

Closed
mkmik opened this issue Oct 28, 2020 · 0 comments · Fixed by #467
Closed

Make it easier to upgrade from ancient (pre v0.9.0) controllers #466

mkmik opened this issue Oct 28, 2020 · 0 comments · Fixed by #467
Assignees
Milestone

Comments

@mkmik
Copy link
Collaborator

mkmik commented Oct 28, 2020

by embracing strong backward compatibility and switching back accept-deprecated-v1-data to true by default.

Rationale

While sealed-secrets is a tool in many people's tool boxes, it's a rather "invisible" tool.

It stays there, does it's job and people focus on other things, often for years before putting back the spotlight on sealed secrets (usually when installing a new cluster etc). A 1yo version may appear ancient for us maintainers, but we do have
people out there running those versions, and we should make it easier (not harder!) for people to upgrade.

Furthermore, sealed-secrets's support is best effort and backward compatibility is a good idea if it can reduce the amount of questions by confused users who just happen to have to install sealed secrets in a new clusters, after having used a >2y old version in a previous cluster with no problems.

@mkmik mkmik added this to the v0.13.0 milestone Oct 28, 2020
@mkmik mkmik self-assigned this Oct 28, 2020
@mkmik mkmik changed the title Make upgrades from ancient controllers easy Make it easier to upgrade from ancient (pre v0.7.0) controllers Oct 28, 2020
@mkmik mkmik changed the title Make it easier to upgrade from ancient (pre v0.7.0) controllers Make it easier to upgrade from ancient (pre v0.9.0) controllers Oct 28, 2020
mkmik pushed a commit that referenced this issue Oct 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant