Describe the solution you'd like
With #101 we're now able to create the scs Cluster Stacks in various versions without code repetition.
That makes it possible to create releases with one code base.
The downside ist, that the code for the releases doesn't exist in the repository.
To solve this the different versions should be stored in release branches, named after Kubernetes versions.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
/kind feature
Describe the solution you'd like With #101 we're now able to create the
scsCluster Stacks in various versions without code repetition. That makes it possible to create releases with one code base. The downside ist, that the code for the releases doesn't exist in the repository. To solve this the different versions should be stored in release branches, named after Kubernetes versions.Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version)/etc/os-release):