Skip to content

Conversation

cardoe
Copy link
Contributor

@cardoe cardoe commented Apr 18, 2025

Updating the ArgoCD AppSets to make dev and prod closer together.

@cardoe
Copy link
Contributor Author

cardoe commented Apr 18, 2025

@ctria @abhimanyu003 @skrobul @nicholaskuechler would definitely appreciate some feedback on the documentation changes

@cardoe cardoe force-pushed the argocd-deploy-update branch from 9cc0e84 to 5274d56 Compare April 18, 2025 14:32
@cardoe cardoe force-pushed the argocd-deploy-update branch 13 times, most recently from e23aef3 to bedcf4b Compare April 25, 2025 00:45
@cardoe
Copy link
Contributor Author

cardoe commented Apr 25, 2025

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.

@cardoe cardoe force-pushed the argocd-deploy-update branch 3 times, most recently from 9773dbc to c2483e5 Compare May 5, 2025 20:59
@skrobul
Copy link
Collaborator

skrobul commented May 6, 2025

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.

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)

@cardoe cardoe force-pushed the argocd-deploy-update branch 4 times, most recently from 3073118 to 08ff65b Compare June 4, 2025 18:06
@cardoe cardoe force-pushed the argocd-deploy-update branch from 08ff65b to 5bbe0a8 Compare June 4, 2025 18:24
@cardoe
Copy link
Contributor Author

cardoe commented Jun 4, 2025

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.

@cardoe cardoe force-pushed the argocd-deploy-update branch 4 times, most recently from cb269bf to c70b57c Compare June 5, 2025 00:55
@cardoe cardoe changed the title feat: update ArgoCD AppSets and docs to make dev/prod closer feat: update ArgoCD AppSets to make dev/prod closer Jun 5, 2025
@cardoe
Copy link
Contributor Author

cardoe commented Jun 5, 2025

Really close. The Argo Workflows patch needs the DNS zone templated in.

@cardoe cardoe force-pushed the argocd-deploy-update branch from 31015a2 to ae9898d Compare June 5, 2025 17:44
@cardoe cardoe marked this pull request as ready for review June 5, 2025 17:47
@cardoe cardoe requested a review from abhimanyu003 June 5, 2025 17:47
cardoe added 5 commits June 6, 2025 11:13
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.
@cardoe cardoe force-pushed the argocd-deploy-update branch from ceae95a to fc7f123 Compare June 6, 2025 16:14
@cardoe cardoe added this pull request to the merge queue Jun 6, 2025
Merged via the queue into main with commit af78b63 Jun 6, 2025
16 checks passed
@cardoe cardoe deleted the argocd-deploy-update branch June 6, 2025 17:26
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 this pull request may close these issues.

4 participants