Openunison migration from 1.0.18 to Latest
Closed this issue · 2 comments
Hi Team,
As discussed with Marc in the previous ticket:
TremoloSecurity/OpenUnison#780
Please guide us in migrating and refactoring from current Operator concept to currently supported charts and images, that would include OpenUnison as well as other applications within it.
This is not typically how our interactions with Open Source users go. Given that every environment is unique, we ask that open source users make the first attempt at a deployment based on the docs, then we're happy to answer specific questions rather then preemptively walk through potential migration steps. There are unlimited combinations of technologies that can be used to deploy an application onto Kubernetes, so customizing and pre-testing a specific approach is something we reserve for customers with commercial support contracts.
That said, we do have a supported Application for ArgoCD that should be a good starting point - https://openunison.github.io/deployauth/#deploying-with-argocd. That, combined with the instructions for upgrading from 1.0.23 should be able to get you going. There isn't much that's changed from a values.yaml perspective. We added wave annotations to all of our objects and combined them into a single chart for use with argocd. You already have your orchestra-secrets-source Secret, so integrating your current values.yaml into the example Application should get you most of the way there. You can also follow the guidance for upgrading to keep your static secrets - https://openunison.github.io/upgrading/ - but since openunison's login portal is stateless, regenerating those won't impact your users.
Once you get an initial deployment done, please feel free to ask more questions on this thread. please remember to provide log output, errors, etc.
closing due to inactivity