Fix serverURL and caCertData for non bootstrap token modes#108
Merged
Conversation
bcho
approved these changes
Mar 3, 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
2 participants
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.
This pull request introduces a new early bootstrap step to the node bootstrap process that automatically populates the Kubernetes API server URL and CA certificate data in the node configuration. This is specifically for non-bootstrap-token authentication modes (Arc, Service Principal, Managed Identity), ensuring that later bootstrap steps (like starting kubelet and NPD) have the necessary cluster connection details. The main changes are as follows:
Cluster Configuration Enrichment:
Added a new file
cluster_config_enricher.gothat defines theclusterConfigEnricherstep. This step fetches the AKS cluster admin credentials using Azure SDK, extracts the server URL and CA certificate data from the kubeconfig, and updates the live node configuration accordingly. This ensures that required fields are present for subsequent bootstrap steps in non-bootstrap-token scenarios.Integrated the new
clusterConfigEnricherstep into the bootstrap sequence inbootstrapper.go, making sure it runs before steps that require the server URL and CA certificate (such as starting kubelet and NPD).