namespacePrefix and namespaceSuffix feature similar to namePrefix and nameSuffix

[dyapas]

I think it would be more helpful if we have common namespacePrefix & namespaceSuffix similar to namePrefix and nameSuffix to update namespace for different environments.

example: current namespace value is : myNameSpace
for dev environment: under overlays/dev/kustomization.yaml namespaceSuffix: -dev resulting myNameSpace-dev
for qa environment: under overlays/dev/kustomization.yaml namespaceSuffix: -qa resulting myNameSpace-qa
for prod environment: under overlays/dev/kustomization.yaml namespaceSuffix: -prod resulting myNameSpace-prod

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[stormqueen1990]

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@stormqueen1990: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[stormqueen1990]

/kind feature

[stormqueen1990]

/lifecycle frozen

[stormqueen1990]

@koba1t @varshaprasad96: could you check out if this is something we would like to support?
On the surface this seems valuable to me, since it would allow to break down Kustomize resources based on enviroments, configurations, etc.

[stormqueen1990]

/triage under-consideration

[koba1t]

HI @dyapas
Thanks for your idea.
I think this feature is interesting and convenient if we have it.

But, I only care about making any effects on the current features if we add this feature.

Hi @stormqueen1990
Could you investigate this feature?