duplicate "namespace:" entries in kustomization.yaml should get detected

[guettli]

Eschewed features

• This issue is not requesting templating, unstuctured edits, build-time side-effects from args or env vars, or any other eschewed feature.

What would you like to have added?

If this is in my kustomization.yaml file, I would like to get an error:

namespace: foo
namespace: bar

Why is this needed?

This helps me to find errors early.

Can you accomplish the motivating task without this feature, and if so, how?

After some time I will find that error.

What other solutions have you considered?

.

Anything else we should know?

No response

Feature ownership

• I am interested in contributing this feature myself! 🎉

[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

[kundan2707]

/remove-lifecycle stale

[koba1t]

HI @guettli

Honestly, we were trying to introduce restricted unmarshaling for kustomization.yaml.
But, that PR was reverted due to breaking current behavior.
#5073

If you can investigate the problem referred to that issue, that would be a big help to improve kustomize!

[koba1t]

/triage under-consideration

[guettli]

To be honest, Kustomize seem unmaintained at the moment. I think about using an alternative. Although I have no clue which other tool we could use.

[koba1t]

/close

[k8s-ci-robot]

@koba1t: Closing this issue.

In response to this:

/close

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-sigs/prow repository.