-
Notifications
You must be signed in to change notification settings - Fork 20
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
Unable to enable Azure CAPIProvider #483
Comments
Hi @mantis-toboggan-md, thanks for reporting this. I was able to reproduce the issue with the following configuration:
Looks like this may be related to missing resources For some reason CAPZ is not detecting the api resource via RKE2 but, if installing Kubeadm and the re-trying CAPZ installation, it applies the changes successfully. I did apply this yaml file before installing CAPZ: ---
apiVersion: v1
kind: Namespace
metadata:
name: capi-kubeadm-bootstrap-system
---
apiVersion: turtles-capi.cattle.io/v1alpha1
kind: CAPIProvider
metadata:
name: kubeadm-bootstrap
namespace: capi-kubeadm-bootstrap-system
spec:
name: kubeadm
type: bootstrap
version: v1.4.6
configSecret:
name: variables
---
apiVersion: v1
kind: Namespace
metadata:
name: capi-kubeadm-control-plane-system
---
apiVersion: turtles-capi.cattle.io/v1alpha1
kind: CAPIProvider
metadata:
name: kubeadm-control-plane
namespace: capi-kubeadm-control-plane-system
spec:
name: kubeadm
type: controlPlane
version: v1.4.6
configSecret:
name: variables And then the Azure provider was successfully installed via Rancher UI and the controller did not report any errors. The custom resource that the logs report as missing should be available via the RKE2 provider so we need to investigate this a bit further to propose a solution. |
Could it be because there is no |
Opened a new upstream issue kubernetes-sigs/cluster-api-provider-azure#4854 to track the fix on CAPZ. Once the community accepts this proposal, we'll submit the PR effectively removing the dependency on Kubeadm when enabling |
Upstream PR: kubernetes-sigs/cluster-api-provider-azure#4868 |
done |
What steps did you take and what happened?
The Azure CAPIProvider fails to enable correctly in the 0.4.0 capi ui. The status changes from
Provisioning
toReady
but eventually becomesUnavailable
. The capz-controller-manager pod is in CrashLoopBackoff with the errorWhat did you expect to happen?
I would expect the capz-controller-manager pod to be running and azure capiprovider resource to be in Ready state
How to reproduce it?
No response
Rancher Turtles version
No response
Anything else you would like to add?
No response
Label(s) to be applied
/kind bug
The text was updated successfully, but these errors were encountered: