You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are already starting to see some moc specific implementation (e.g. storage class for JH #22 and possibly superset #35). We need a way to separate these out from general deployments.
We could separate them out into bases/overlays (where overlays have folders like moc and quicklab). The problem is then our argocd-apps repo will become environment specific (since we specify a path). As a solution we could also extend the base/overlays structure to the argocd-apps repo. That's one suggestion, open to other ideas.
The text was updated successfully, but these errors were encountered:
I kinda agree with you. It's not pretty but it sounds like a viable strategy and I have nothing better in my sleeve right now since I was thinking the same. 🙂
We are already starting to see some
moc
specific implementation (e.g. storage class for JH #22 and possibly superset #35). We need a way to separate these out from general deployments.We could separate them out into bases/overlays (where overlays have folders like
moc
andquicklab
). The problem is then ourargocd-apps
repo will become environment specific (since we specify apath
). As a solution we could also extend the base/overlays structure to theargocd-apps
repo. That's one suggestion, open to other ideas.The text was updated successfully, but these errors were encountered: