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
{{ message }}
This repository has been archived by the owner on Nov 11, 2024. It is now read-only.
Is your feature request related to a problem? Please describe.
in the current environment and project setting, any team will receive an own cicd namespace holding project specific CI/CD pipeline definition. The namespace has a dedicated name, let's say prj-common-cicd
The kam bootstrap command generates files for predefined namespaces, like cicd. It is possible to set a --prefix, this is not enough. Changing the namespace in the generated configuration is not possible in case SealedSecret with strict scope is used.
Describe the solution you'd like
Possibility to define the target namespaces for all aspects (cicd, stages, common ArgoCD resources etc)
Describe alternatives you've considered
n/a
Additional context
I did not checked the interactive mode of kam if this is supported?! :)
The text was updated successfully, but these errors were encountered:
@haf-tech I agree prefix wouldn't be sufficient. IMO there should be means to update the namespace after the bootstrap as well. One option could be updating it in the manifest file and Kam will update the namespace and the structure accordingly. I suppose kam build cmd was introduced for this purpose which is not ready yet.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
in the current environment and project setting, any team will receive an own cicd namespace holding project specific CI/CD pipeline definition. The namespace has a dedicated name, let's say
prj-common-cicd
The
kam bootstrap
command generates files for predefined namespaces, likecicd
. It is possible to set a--prefix
, this is not enough. Changing the namespace in the generated configuration is not possible in caseSealedSecret
withstrict
scope is used.Describe the solution you'd like
Possibility to define the target namespaces for all aspects (cicd, stages, common ArgoCD resources etc)
Describe alternatives you've considered
n/a
Additional context
I did not checked the interactive mode of
kam
if this is supported?! :)The text was updated successfully, but these errors were encountered: