cluster-api-provider-ibmcloud
cluster-api-provider-ibmcloud copied to clipboard
Explore clusterclass, machineset, machinehealth apis
/kind feature /area provider/ibmcloud
Describe the solution you'd like https://github.com/kubernetes-sigs/cluster-api/blob/main/api/v1beta1/clusterclass_types.go https://github.com/kubernetes-sigs/cluster-api/blob/main/api/v1beta1/machineset_types.go https://github.com/kubernetes-sigs/cluster-api/blob/main/api/v1beta1/machinehealthcheck_types.go
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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:
- Mark this issue or PR as fresh with
/remove-lifecycle stale
- Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
- Need to create a IBMPowerVSClusterTemplate: for reference https://github.com/kubernetes-sigs/cluster-api-provider-gcp/issues/397
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged 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:
- Mark this issue as fresh with
/remove-lifecycle stale
- Close this issue with
/close
- Offer to help out with Issue Triage
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:
- 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:
- Mark this issue as fresh with
/remove-lifecycle rotten
- Close this issue with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
cluster class for vpc is already addressed via https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud/issues/974, hence closing this PR.