Closed lusche closed 6 months ago
Encountered the same problem. I tried against many clusterctl versions with no luck. Please help.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
What steps did you take and what happened: Following the documentation https://github.com/kubernetes-sigs/cluster-api-provider-nested/tree/main/docs and try to init a cluster: bin/clusterctl init --core cluster-api:v0.4.0 --control-plane nested:v0.1.0 --infrastructure nested:v0.1.0 Fetching providers Error: current version of clusterctl is only compatible with v1beta1 providers, detected v1alpha4 for provider cluster-api
we get this error. We tried the latest clusterctl version 1.3.5 as well as download the code and build the master tree. Same result in all tested binaries.
What did you expect to happen: If i follow the documentation i would expact the same results as in the documenttion. S in this case a yaml that can be applied to a kubernets cluster.
Environment:
kubectl version
): v1.26.3/etc/os-release
): Debian GNU/Linux 11 (bullseye)/kind bug