Implement existing service bindings migration #3820
Assignees
Milestone
Comments
danail-branekov
changed the title
uzabanov
added a commit
that referenced
this issue
Mar 7, 2025
- It will delete the redundant sbio bindings, making sure they are refclected in the app status AND restart the app so that it sees the new environment - The migration can be disabled Co-authored-by: Yusmen Zabanov <[email protected]> fixes #3820
uzabanov
added a commit
that referenced
this issue
Mar 7, 2025
- It will delete the redundant sbio bindings, making sure they are refclected in the app status AND restart the app so that it sees the new environment - The migration can be disabled Co-authored-by: Yusmen Zabanov <[email protected]> fixes #3820 Co-authored-by: Yusmen Zabanov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When implementing #1949 we considered how wether our new implementation is backwards compatible with 0.14.0. We have managed to migrate a 0.14.0 deployment to main by the following steps:
korifi-controllersdeploymentServiceBindings for the appAs deleting the servicebindingio binding should take place while korifi controllers are down, we could implement those steps in a pre-update helm hook
The manual app restart step is a bit tedious. In order to avoid it could we delete the
AppWorkloadwhile korifi controllers are down? Thus when the controllers are upgraded, they would reconcile the apps and create the app workload with desired bindingsThe text was updated successfully, but these errors were encountered: