🌱 Support CAPI ClusterResourceSet about cluster-api-provider-nested HOT 12 OPEN

Hey @gyliu513 thanks for filing this issue. Because this project is based on CAPI methodologies and interfaces we should be able to piggy back on the ClusterResourceSet type that is exposed via CAPI, this currently supports mode: "ApplyOnce" which will apply the addon/extra resources once the cluster comes up and we're able to address the control plane. This should accomplish what you are looking for once CAPN is up to date.

Links:

• https://cluster-api.sigs.k8s.io/tasks/experimental-features/cluster-resource-set.html
• https://github.com/kubernetes-sigs/cluster-api/blob/master/docs/proposals/20200220-cluster-resource-set.md

from cluster-api-provider-nested.

@gyliu513 so we can keep this issue open and make sure we track this I'm going to retitle this and purpose it towards testing that ClusterResourceSet's from CAPI work CAPN's design. wdyt?

from cluster-api-provider-nested.

@christopherhein sounds good, thanks!

from cluster-api-provider-nested.

@gyliu513 Now that we have a CAPI integration setup would you like to try this and report if it works or not?

from cluster-api-provider-nested.

@gyliu513 check out - #105 (comment) for a walkthrough, the README is still getting updated, check out https://cluster-api.sigs.k8s.io/tasks/experimental-features/cluster-resource-set.html for setting up CAPI with this deployed and the linked proposal for how it works.

from cluster-api-provider-nested.

/kind feature

from cluster-api-provider-nested.

/remove-kind feature

from cluster-api-provider-nested.

/retitle 🌱 Support CAPI ClusterResourceSet

from cluster-api-provider-nested.

/kind support

from cluster-api-provider-nested.

@christopherhein Awesome! Any document that I can refer? Thanks!

from cluster-api-provider-nested.

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

from cluster-api-provider-nested.

/remove-lifecycle stale
/lifecycle frozen

from cluster-api-provider-nested.