Closed MatousJobanek closed 3 months ago
that's exactly why I created the other PR so you can see what it looks like: https://github.com/codeready-toolchain/sandbox-sre/pull/1926
and what do you mean by "Kustomize folder", by the way?
a folder that contains the whole structure of the generated manifests with the kustomization.yaml files
Let me improve the comment there
I'm a bit confused with the new
that's exactly why I created the other PR so you can see what it looks like: codeready-toolchain/sandbox-sre#1926
yes, I've seen it, but I'm still a bit confused :/
Not by the fact that the generated manifests will be in a separate folder (here, components/auth/devsandbox-production/generated-manifests/member-intel
), but rather, how to we specify the path to this particular folder?
and what do you mean by "Kustomize folder", by the way?
a folder that contains the whole structure of the generated manifests with the kustomization.yaml files
Let me improve the comment there
may I suggest "Kustomize output folder"?
I updated the comment 7719c2a (before seeing your last message) please take a look and feel free to make a suggestion in the GH PR view
Not by the fact that the generated manifests will be in a separate folder (here, components/auth/devsandbox-production/generated-manifests/member-intel), but rather, how to we specify the path to this particular folder?
I'm confused, what do you want to have different there?
I updated the comment 7719c2a (before seeing your last message) please take a look and feel free to make a suggestion in the GH PR view
great, thanks for taking my questions/comments into account!
Attention: Patch coverage is 78.26087%
with 5 lines
in your changes missing coverage. Please review.
Project coverage is 69.59%. Comparing base (
ed47159
) to head (7719c2a
). Report is 1 commits behind head on master.
Files | Patch % | Lines |
---|---|---|
pkg/cmd/generate/admin-manifests.go | 70.58% | 2 Missing and 3 partials :warning: |
add two new fields into kubesaw-admins.yaml file
separateKustomizeComponent
can be used in a member cluster config - when set to true, then the manifests for the member cluster is gonna be generated in a separate Kustomize component/folderselector.skipMembers
which can be defined either for a ServiceAccount or for a Users. It's a list of members the generation should be skipped for the given SA or User entity.These two fields together enable us to generate manifests for a given member cluster (the intel hackathon one) in a separate folder and skip some users/sa there. With this, we can still generate manifests needed to execute ksctl commands in the intel hackathon cluster, but it won't include the manifests for the crtadmin users of the 3rd party components (the components won't be installed there).
NOTE: You may ask why did I use the "selector" as a parent field for the "skipMembers" one. I'd like to move the
AllClusters
field there as well and manage any other fields related to filtering/selecting the items under this generic one.. (But if it would be too confusing, then I can remove the parent field and store it all at the root level of the entity)To be done in the next PR:
generate cli-configs
command