Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configMapGenerator doesn't create the correct suffix when metadata.namespace: is set. #5757

Open
shlomodaari opened this issue Sep 3, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@shlomodaari
Copy link

What happened?

When the namespace is set in the deployment the kustomize doesn't add the suffix to the configMap

What did you expect to happen?

adding the suffix correctly

How can we reproduce it (as minimally and precisely as possible)?

# kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- resources.yaml
# resources.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: test-object
data:
  placeholder: data

Expected output

      - configMap:
          name: spinnaker-hb4d76k25c
      - configMap:
          name: orca-c88mftkf6c

Actual output

      - configMap:
          name: spinnaker
      - configMap:
          name: orca

Kustomize version

5.4.3

Operating system

None

@shlomodaari shlomodaari added the kind/bug Categorizes issue or PR as related to a bug. label Sep 3, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 3, 2024
@shlomodaari
Copy link
Author

workaround is to set the namespace on the kustomize instead the deployment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants