Skip to content

CAPI Operator does not install capd if infrastructure=docker via helm #788

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.

Sign up for GitHub

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

Jump to bottom
Open
thatmlopsguy opened this issue Apr 19, 2025 · 2 comments · May be fixed by #794
Open

CAPI Operator does not install capd if infrastructure=docker via helm #788

thatmlopsguy opened this issue Apr 19, 2025 · 2 comments · May be fixed by #794
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@thatmlopsguy
Copy link

thatmlopsguy commented Apr 19, 2025 •
edited
Loading

What steps did you take and what happened:

Running

$ helm install capi-operator capi-operator/cluster-api-operator --create-namespace -n capi-operator-system --set infrastructure=docker:v1.4.2 --set cert-manager.enabled=true --wait --timeout 90s

$ kubectl get ns                                                                                                                                                                                        
NAME                                STATUS   AGE
argocd                              Active   3m14s
capi-kubeadm-bootstrap-system       Active   6s
capi-kubeadm-control-plane-system   Active   6s
capi-operator-system                Active   111s
capi-system                         Active   5s
cert-manager                        Active   2m5s
default                             Active   3m43s

What did you expect to happen:

$ clusterctl init --infrastructure docker

$ kubectl get ns   
                                                                                                                                                                          
NAME                                STATUS   AGE
argocd                              Active   7m38s
capd-system                         Active   22s <- difference
capi-kubeadm-bootstrap-system       Active   4m30s
capi-kubeadm-control-plane-system   Active   4m30s
capi-operator-system                Active   6m15s
capi-system                         Active   4m29s
cert-manager                        Active   6m29s
default                             Active   8m7s

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api-operator version: 0.18.1
  • Cluster-api version:
  • Minikube/KIND version: 0.24.0
  • Kubernetes version: (use kubectl version): v1.31.0
  • OS (e.g. from /etc/os-release): Ubuntu 22.04.5 LTS (via wsl)

/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-operator/labels?q=area for the list of labels]
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 19, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@thatmlopsguy thatmlopsguy changed the title CAPI Operator dos not install capd if infrastructure=docker CAPI Operator does not install capd if infrastructure=docker via helm Apr 19, 2025
@rbjorklin
Copy link
Contributor

Hey @thatmlopsguy! Thanks for reporting this! What version of the chart are you on? If you are on 0.19.0 could you try:

helm install capi-operator capi-operator/cluster-api-operator --create-namespace -n capi-operator-system --set infrastructure.docker.version=v1.4.2 --set cert-manager.enabled=true --wait --timeout 90s

Also what version of Helm are you on?

@rbjorklin rbjorklin linked a pull request Apr 25, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

📖 fix helm install instructions rbjorklin/cluster-api-operator
3 participants
@rbjorklin @k8s-ci-robot @thatmlopsguy