Adds RMQ operators ArgoCd configs for prod#294
Conversation
There was a problem hiding this comment.
These configs seem to have quite a few differences to the ones in the management-dev directory.
Those specify a cluster to deploy to that's one (or potentially both depending on what the generators enable) of our cloud or isis microk8s clusters, while these are only deploying to https://kubernetes.default.svc, which I think would be the cluster where we run argocd, and I've a feeling that that's the management clusters and would make rabbitmq inaccessible to our apps
ACLay
left a comment
ACLay
left a comment
There was a problem hiding this comment.
To keep the environments consistent, should we also move the dev versions of these files from argocd/management-dev to argocd/dev/shared?
| # Uncomment if you want to deploy to dev-microk8s-alternative | ||
| #- name: dev-microk8s-alternative |
There was a problem hiding this comment.
To reduce the risk of misconfiguration in the future, could the commented out cluster names in these files be updated to prod-fallback instead of the dev value?
…hared , updated the commented code in configsfor prod -fallback in
4 participants
closes: #293