Skip to content
This repository was archived by the owner on Nov 11, 2024. It is now read-only.
This repository was archived by the owner on Nov 11, 2024. It is now read-only.

Define target namespace separately  #246

@haf-tech

Description

@haf-tech

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?! :)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions