Revisit flux dependencies
We started this discussion in our chat today:
v: I need to repeat myself again: I'm not happy about the fact that we bundle so many things together in cental kustomizations, like core. On the init cluster this leads to the bottlneck that when SSO is broken, you can't do anything else. most other HRs depend on this, rendering them unchangeable. I think we should revisit how we structure our dependencies. From a flux deployment point of view, i.e. monitoring doesn't depend on SSO like we speciy it now.
m: In a production environment, if SSO doesn't work, the rest wouldn't work either. Because of that SSO should work before Flux starts installing the apps that depend on it.
v: why not ? for a user it doesn't make a difference if he can't login or the app isn't there at all in both cases the app is not usable and I'm talking about a dev environment here
m: Maybe I'm thinking too much inside the current framework: I wouldn't want to make SSO an optional app like the other apps in flux2/apps, and I don't really see another option atm. What would you suggest?
v: I haven't thought of a concrete solution, I'd like to make SSO optional but it's not a must, having a dedicated kustomization would be enough so other kustomizations are not blocked by SSO not being ready