-
Notifications
You must be signed in to change notification settings - Fork 6
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
Consolidate cluster-stacks folder structure #56
Comments
We can also place an additional explanation file in the folder to explain the purpose and the guarantees of stable and unstable cluster-stacks. For example we could guarantee that specific variables will be maintained or warn that they might change in case of an unstable clusterstack. |
Hi @paulphys, |
In todays container call i learned that a clusterstack is the sum of all node-definitions, cluster-classes and cluster-addons over all k8s-versions over all providers that share the same clusterstack name. Therefore i think the following folder-structure would better reflect this relation:
instead of
actual folder names:
Regarding CSO and CSPO this change would not do any harm, as the operators do not care about the git-state (only reading the GitHub releases) and in the release itself there are only assets of the most deeply nested path. The question is if csctl would have issues with this change. Maybe @janiskemper or @michal-gubricky know? |
I have another question: does the most deeply nested folder (the kubernetes version) that contains cluster-class, cluster-addon and node-image have a name?
|
@mxmxchere you are 100% correct and there wouldn't be any issues. I strongly recommend to not choose "alpha" as cluster stack name in the future, because "alpha" should be rather "an alpha state of cluster stack xyz", so like a release channel stable, alpha, beta. The cluster stack names should ideally be independent of both "scs" and anything like "stable", "alpha", etc. to not confuse this. For example, what do we do if we have beta releases of the "alpha" cluster stack? And what if there is an "scs" cluster stack, but now we want to do a second one? Is that called "scs2" then? |
Hi @janiskemper I chose the name |
Right now we have two cluster-stacks,
alpha
andscs
, it is not clear which one is the mainly maintained cluster-stack. Therefore we should either remove one of them or give it a name that describes the purpose of each cluster-stacks, e.g. stable/unstable/dev.scs
catch up withalpha
#93The text was updated successfully, but these errors were encountered: