-
Notifications
You must be signed in to change notification settings - Fork 434
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
Nodes fail to come up when using custom CA and Kubeconfig #2778
Comments
@karansinghneu can you please upload any logs that you've collected (controller logs, cloud init logs would be helpful - see https://capz.sigs.k8s.io/topics/troubleshooting.html) and the cluster yaml spec you used for the AzureCluster ? (make sure to redact any secrets) |
@CecileRobertMichon
$kubectl get azuremachines
From control plane node:
YAML Spec:
|
Update: It's most likely the custom FQDN causing the issue. Further investigation: |
@CecileRobertMichon I think I have reached a point where I am now intermittently hitting this: kubernetes-sigs/cluster-api#6029 |
@karansinghneu did you ever figure this one out? Is there anything that needs to be fixed in CAPZ and/or CAPI? |
As far as I recall it was a minor mistake from my end where I used an incorrect region name in the subdomain of the FQDN field. I should have closed this earlier, sorry about that. |
/kind bug
[Before submitting an issue, have you checked the Troubleshooting Guide?]
Yes
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
What did you expect to happen:
Workload cluster to provision successfully
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
): Client Version: v1.25.3, Kustomize Version: v4.5.7, Server Version: v1.25.0/etc/os-release
): Linux (ubuntu 20.04)The text was updated successfully, but these errors were encountered: