search

kubernetes-sigs / cluster-api-provider-nested

Cluster API Provider for Nested Clusters
Apache License 2.0
298 stars 65 forks source link

Unable to init Cluster with the nested provider #343

Closed lusche closed 6 months ago

lusche commented 1 year ago

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:

/kind bug

groundnuty commented 1 year ago

Encountered the same problem. I tried against many clusterctl versions with no luck. Please help.

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 7 months ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 6 months ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 6 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-nested/issues/343#issuecomment-1951148022): >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: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.