Skip to content

feat: re-introduce capms sonic flavor#292

Draft
ma-hartma wants to merge 3 commits into
masterfrom
capi-lab-tests
Draft

feat: re-introduce capms sonic flavor#292
ma-hartma wants to merge 3 commits into
masterfrom
capi-lab-tests

Conversation

@ma-hartma
Copy link
Copy Markdown
Contributor

@ma-hartma ma-hartma commented Apr 21, 2026

Description

Users without a license do not have access to our Dell SONiC images, meaning they can't test the capms flavor.
This PR tries to re-introduce the option to run on SONiC community as well but keep Dell SONiC.

Commit 43b95e6 replaced SONiC Community with Dell SONiC and was used as reference.

Used AI-Tools ✨

  • TOOL used for generation

@ma-hartma
Copy link
Copy Markdown
Contributor Author

ma-hartma commented May 26, 2026

I unfortunately can't get the capi-lab running on Community SONiC.
Only 2/3 nodes (fw and control-plane node) come up, but the last node - the worker - can't be created. The capi-kubeadm-bootstrap-controller-manager cannot reach the cluster, as there is no route to the control plane node. For Enterprise SONiC, this part actually doesn't make problems.
@iljarotar any ideas or maybe we can take a look at it together?
See the test run here: https://github.com/metal-stack/cluster-api-provider-metal-stack/actions/runs/26468213362/job/77934158477?pr=142

kubectl logs -n capi-kubeadm-bootstrap-system capi-kubeadm-bootstrap-controller-manager-58c6c458b6-c5j8n | grep error
E0526 12:09:58.732565       1 cluster_accessor.go:259] "Connect failed" err="error creating REST config: error getting kubeconfig secret: Secret \"metal-test-kubeconfig\" not found" controller="clustercache" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" Cluster="default/metal-test" reconcileID="44b1c306-2e76-46ae-b81b-3e36e4f4fade" duration="101.145329ms"
E0526 12:10:31.720130       1 cluster_accessor.go:259] "Connect failed" err="error creating HTTP client and mapper: cluster is not reachable: Get \"https://203.0.113.129:443/?timeout=5s\": dial tcp 203.0.113.129:443: connect: no route to host" controller="clustercache" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" Cluster="default/metal-test" reconcileID="023a2790-0d11-44ff-baa6-ce78f64f6ba8" duration="2.986547116s"
E0526 12:11:06.722206       1 cluster_accessor.go:259] "Connect failed" err="error creating HTTP client and mapper: cluster is not reachable: Get \"https://203.0.113.129:443/?timeout=5s\": context deadline exceeded" controller="clustercache" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" Cluster="default/metal-test" reconcileID="a52f7895-4c56-40f8-8860-3ff67cc846fd" duration="5.001177408s"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant