-
Notifications
You must be signed in to change notification settings - Fork 104
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.
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
Tilt provider support for CAPI #358
Comments
~/.cluster-api/clusterctl.yaml file example as follows:
|
Thanks for the really helpful feature request, @jds9090: TIL about CAPI addons, thanks for sharing! Definitely a green light to set up a TILT-based dev environment scaffolding, it seems a popular project and I definitely should give it a try. In regard to the CAPI addons, I think there's a pre-requisite issue, #292, since manifests would be required to get exposed using a GitHub release, and we're working on there. However, just installing Kamaji is not enough since along with that a Datastore must be created, and configured properly. The preferred way to install Kamaji is via Helm which offers hooks to automate some tasks using Kubernetes jobs, like the creation of an etcd cluster, properly configured with multi-tenancy. By default, when installing Kamaji, a default one is created, although I would suggest a more fine-grained control using the kamaji-etcd chart which offers a more robust lifecycle management (such as backup). I'd like to start a discussion on how to address this, just sharing my thoughts.
Tagging for visibility @maxgio92 @ptx96 @bsctl and @dierbei who did the Go releaser implementation. |
I agree with you. I also had to install datastore with this command for each tenant:
In my case, I wanted tenant clusters to be deployed with their own datastore for security. Please, consider also this case because some people are more interested in this case for some specific policy of companies . I hope you will come up with more fine-grained control. |
@prometherion In the view of CAPI, we can use this addon to install datastore(https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm/blob/main/docs/quick-start.md) per tenant. If tenant uses the default, it may say "already installed". |
Unfortunately, the addon-provider is not what I want to find.. this is a replacement of ClusterResourceSet(https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20220712-cluster-api-addon-orchestration.md#motivation) |
Most people who use CAPI provision clusters using clusterctl(https://cluster-api.sigs.k8s.io/clusterctl/overview.html). When we want to use kamaji as control plane with CAPI, we can use cluster-api-control-plane-provider-kamaji.(https://github.com/clastix/cluster-api-control-plane-provider-kamaji). But it still needs kamaji to be installed(clastix/cluster-api-control-plane-provider-kamaji#49).
Recently, from CAPI v1.5.0(https://github.com/kubernetes-sigs/cluster-api/releases/tag/v1.5.0), we can use the addon option of clusterctl and I suggest we deploy both kamaji and cluster-api-control-plane-provider-kamaji with the option.
Here is my suggestion using the addon option of clusterctl.
You can also create a pre-configured kind cluster (if you have not already done so) and launch your development environment, run
The text was updated successfully, but these errors were encountered: