-
Notifications
You must be signed in to change notification settings - Fork 33
Closed
Milestone
Description
Currently, the docker image works only for the amd64 (x86_64) systems
https://hub.docker.com/r/apache/cloudstack-kubernetes-provider
Since CloudStack added support for arm64 hypervisor , we need a docker image for arm64 build
Current behavior
On deploying a cks cluster on a arm64 cluster , the kubernertes provider pod goes into crash state
k logs -f cloud-controller-manager-857cd68cf5-4d94r -n kube-system
exec /app/cloudstack-ccm: exec format error
[6:42](https://shapeblue.slack.com/archives/D06D81CQ5MW/p1762175550473179)
apache/cloudstack-kubernetes-provider:v1.1.0
k describe pod cloud-controller-manager-857cd68cf5-79686 -n kube-system
Name: cloud-controller-manager-857cd68cf5-79686
Namespace: kube-system
Priority: 0
Service Account: cloud-controller-manager
Node: csi-cks-test5-node-19a49bea338/10.1.1.194
Start Time: Mon, 03 Nov 2025 18:31:32 +0530
Labels: k8s-app=cloud-controller-manager
pod-template-hash=857cd68cf5
Annotations: cni.projectcalico.org/containerID: 07fd41dd5edbc6d37f70b750c666e3c64cdeaf8193c7d3fe50142fa2efeaa437
cni.projectcalico.org/podIP: 192.168.51.195/32
cni.projectcalico.org/podIPs: 192.168.51.195/32
Status: Running
IP: 192.168.51.195
IPs:
IP: 192.168.51.195
Controlled By: ReplicaSet/cloud-controller-manager-857cd68cf5
Containers:
cloud-controller-manager:
Container ID: containerd://36b44272c9b40226fc65828246bc19f053c63badde416e53f684671153b89659
Image: apache/cloudstack-kubernetes-provider:v1.1.0
Image ID: sha256:cb2b358a73b6608e71dd677d2085fc8fb5871be38bcb7cf69bd77ba675a3af53
Port: <none>
Host Port: <none>
Args:
--leader-elect=true
--cloud-provider=external-cloudstack
--cloud-config=/config/cloud-config
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 255
Started: Mon, 03 Nov 2025 18:37:39 +0530
Finished: Mon, 03 Nov 2025 18:37:39 +0530
Ready: False
Restart Count: 6
Limits:
cpu: 50m
memory: 120Mi
Requests:
cpu: 10m
memory: 60Mi
Environment: <none>
Mounts:
/config from config-volume (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-g6chk (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
config-volume:
Type: Secret (a volume populated by a Secret)
SecretName: cloudstack-secret
Optional: false
kube-api-access-g6chk:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: node.cloudprovider.kubernetes.io/uninitialized=true:NoSchedule
node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 7m44s default-scheduler Successfully assigned kube-system/cloud-controller-manager-857cd68cf5-79686 to csi-cks-test5-node-19a49bea338
Normal Pulled 5m53s (x5 over 7m33s) kubelet Container image "apache/cloudstack-kubernetes-provider:v1.1.0" already present on machine
Normal Created 5m53s (x5 over 7m33s) kubelet Created container cloud-controller-manager
Normal Started 5m51s (x5 over 7m31s) kubelet Started container cloud-controller-manager
Warning BackOff 2m32s (x23 over 7m26s) kubelet Back-off restarting failed container cloud-controller-manager in pod cloud-controller-manager-857cd68cf5-79686_kube-system(f8418e5d-2d14-4b2b-b6bd-47cfb77c58d4)
Metadata
Metadata
Assignees
Labels
No labels