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

CCM will remove the space behind the tag, may cause issue on Kubenet AKS cluster #7048

Open
gsxmax opened this issue Sep 12, 2024 · 1 comment
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@gsxmax
Copy link

gsxmax commented Sep 12, 2024

What happened:

When using a tag like "Null "(Null+space) on kubenet AKS, if we do an action like scale up the nodepool, we will hit "InvalidReservedTagValue" error while updating the routetable.

What you expected to happen:

Able to update the routetable.

How to reproduce it (as minimally and precisely as possible):

  • Add tag "test:Null "(test:Null+space) on kubenet AKS cluster.
  • Scale up the nodepool

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version): 1.29.7 (Any AKS version should be able to reproduce this)
  • Cloud provider or hardware configuration:
  • OS (e.g: cat /etc/os-release): Ubuntu 22.04.4 LTS
  • Kernel (e.g. uname -a): Linux aks-agentpool-26712724-vmss00000I 5.15.0-1071-azure Setup artifacts volume for runner #80-Ubuntu SMP Tue Aug
    6 19:27:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  • Install tools: None
  • Network plugin and version (if this is a network-related bug): Kubenet
  • Others:
@gsxmax gsxmax added the kind/bug Categorizes issue or PR as related to a bug. label Sep 12, 2024
@nilo19 nilo19 self-assigned this Sep 22, 2024
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 21, 2024
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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants