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

NodePoolLabelSet always use default namespace #26

Open
Links2004 opened this issue Nov 23, 2021 · 0 comments
Open

NodePoolLabelSet always use default namespace #26

Links2004 opened this issue Nov 23, 2021 · 0 comments

Comments

@Links2004
Copy link

Describe the bug
we want to deploy the controller in the kube-system name, but it always use the NodePoolLabelSet from the default ns.

Steps to reproduce the issue:
config.yaml

    controller:
      namespace: kube-system
      nodepoolNameLabels:
      - nodepool.banzaicloud.io/name
      - kubernetes.io/hostname
    labeler:
      forbiddenLabelDomains:
      - google.com
      managedLabelsAnnotation: nodepool.banzaicloud.io/managed-labels
    log:
      format: logfmt
      level: debug
    healthcheck:
      listenAddress: ":8882"
      endpoint: "/healthz"

broken:

---
apiVersion: labels.banzaicloud.io/v1alpha1
kind: NodePoolLabelSet
metadata:
  name: test-host
  namespace: kube-system
spec:
  labels:
    test-label2: "test-value2"

working:

---
apiVersion: labels.banzaicloud.io/v1alpha1
kind: NodePoolLabelSet
metadata:
  name: test-host
  namespace: default
spec:
  labels:
    test-label2: "test-value2"

Expected behavior
NodePoolLabelSet is working in namespaces

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant