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

AKS: unable to add tags with empty values #12917

Open
mantis-toboggan-md opened this issue Dec 18, 2024 · 2 comments
Open

AKS: unable to add tags with empty values #12917

mantis-toboggan-md opened this issue Dec 18, 2024 · 2 comments
Labels
area/aks kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/2 Size Estimate 2
Milestone

Comments

@mantis-toboggan-md
Copy link
Member

mantis-toboggan-md commented Dec 18, 2024

Setup

  • Rancher version:2.9
  • Rancher UI Extensions:
  • Browser type & version:

Describe the bug
Relates to: rancher/aks-operator#640
During cluster creation, the ui seems to be removing tags with empty values.

To Reproduce
Create a cluster with a few tags and an empty tag, for e.g: {"owner": "pvala", "testLine": "somefile_L45", "empty-tag": ""}

Result
empty tags are removed

Expected Result
empty tags should be reflected in the POST request to create the cluster

Screenshots
image

Additional context

@mantis-toboggan-md mantis-toboggan-md added this to the v2.11.0 milestone Dec 18, 2024
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Dec 18, 2024
@gaktive gaktive added the size/2 Size Estimate 2 label Dec 18, 2024
@rancher-max
Copy link
Member

This ticket will be focused on AKS, but when testing we should look into functionality of GKE and EKS as well, and create tickets accordingly if they need to be updated as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/aks kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/2 Size Estimate 2
Projects
None yet
Development

No branches or pull requests

4 participants