Stop adding kubernetes.azure.com/cluster label to unbounded-managed nodes#17
Open
Stop adding kubernetes.azure.com/cluster label to unbounded-managed nodes#17
Conversation
…odes Agent-Logs-Url: https://github.com/Azure/unbounded-kube/sessions/6477b6e1-1ec8-4c3b-9508-8b1e3e0eead0 Co-authored-by: bcho <1975118+bcho@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Remove kubernetes.azure.com/cluster label from unbounded managed node
Stop adding kubernetes.azure.com/cluster label to unbounded-managed nodes
Apr 9, 2026
bcho
requested changes
Apr 9, 2026
Agent-Logs-Url: https://github.com/Azure/unbounded-kube/sessions/aec606b5-dd1b-47d9-bbac-bba383dd7065 Co-authored-by: bcho <1975118+bcho@users.noreply.github.com>
Member
|
Partial kubelet logs: |
bcho
requested changes
Apr 13, 2026
…ide test Agent-Logs-Url: https://github.com/Azure/unbounded-kube/sessions/e1ee4530-dba0-4c04-ba9b-c8d7488e1c0f Co-authored-by: bcho <1975118+bcho@users.noreply.github.com>
bcho
approved these changes
Apr 13, 2026
Agent-Logs-Url: https://github.com/Azure/unbounded-kube/sessions/bbe6e477-5a0a-4974-b5c0-5cd0f40c6682 Co-authored-by: bcho <1975118+bcho@users.noreply.github.com>
Contributor
Author
bcho
approved these changes
Apr 13, 2026
bcho
requested changes
Apr 13, 2026
Co-authored-by: bcho <1975118+bcho@users.noreply.github.com>
Contributor
Author
Resolved in ba67e7e. Kept both Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
jwilder
approved these changes
Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AKS unbounded-managed nodes were being stamped with
kubernetes.azure.com/cluster, which is an AKS-internal label that should only appear on natively provisioned nodes. Removing it is a prerequisite for deploying our own kube-proxy and konnectivity agent on unbounded nodes.Changes
internal/cloudprovider/provider.go— Dropkubernetes.azure.com/clusterfromAKSProvider.DefaultLabels()and remove theClusterNamefield. SimplifyDetectProvider()to only probe for theaks-cluster-metadataConfigMap; system-node lookup (previously needed only to read the cluster name) is eliminated.internal/cloudprovider/provider_test.go— Update tests to assert the cluster label is absent, and correct previously-expected failures (NoSystemNodes,MissingClusterLabel) that should now succeed.cmd/machina/machina/controller/ssh_integration_test.go— RemoveClusterNamefrom test fixture and assert thatkubernetes.azure.com/clusteris absent from the agent config labels.hack/agent/skills/unbounded-agent-qemu-vm-e2e/scripts/aks-config.sh— Remove the node-label scrape that readkubernetes.azure.com/clusterand appended it to the kubelet labels JSON..github/workflows/agent-e2e-kind.yaml— Addinternal/cloudprovider/**to the path triggers so changes to the cloud provider package also run the kind e2e tests.Before:
After: