-
Notifications
You must be signed in to change notification settings - Fork 7
feat: update ArgoCD AppSets to make dev/prod closer #853
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
Conversation
@ctria @abhimanyu003 @skrobul @nicholaskuechler would definitely appreciate some feedback on the documentation changes |
9cc0e84
to
5274d56
Compare
e23aef3
to
bedcf4b
Compare
Well I think this will work except for global. But it requires changes to the deploy repo. For global pieces it will absolutely wreck them. |
9773dbc
to
c2483e5
Compare
Should we go ahead and wreck it rather sooner than later? I read the PR through but have no comments on documentation (maybe aside from fixing linter errors) |
3073118
to
08ff65b
Compare
08ff65b
to
5bbe0a8
Compare
So the Argo kustomize patch isn't working. The etcdbackup is odd but it seems broken in the current config. The rest is a no-op. |
cb269bf
to
c70b57c
Compare
Really close. The Argo Workflows patch needs the DNS zone templated in. |
31015a2
to
ae9898d
Compare
This new AppSet for the OpenStack services is a no-op with the existing AppSet to allow for a transition over without deleting resources. This AppSet follows the split of the regional and global deployments. It further supports using the same AppSet definition for production environments and development environments by using kustomize to adjust how clusters are defined.
In creating the site / global split AppSets there were a few changes in how cluster specific data can be passed down via config files in the deploy repo. This updates the operators and infra AppSet to behave the same way.
These new AppSets encompasses all the site and global services and are a no-op with the existing components AppSet to allow for transition over without deleting resources. These AppSets aims to make it easier to define the same deployment for production and development environments.
So want to use kustomize components for overriding kustomize things. Components work great and allow for URL based data fetching. However within ArgoCD authenticated URLs to components do not seem to work. That appears to be because kustomize wants URI style SSH paths while ArgoCD's repo secrets use the SSH style. Likely the best thing here would be to support cross-repo refs like the helm code does but this does not appear to be supported in upstream ArgoCD at this time. In an effort to land the updates to the deployment process this hack was made as a workaround. It should be retired and go away when components are properly handled.
These have been replaced with newer files which split the components out along the lines of site or global deployments. These are redundant now.
ceae95a
to
fc7f123
Compare
Updating the ArgoCD AppSets to make dev and prod closer together.