cluster-api-provider-gcp
cluster-api-provider-gcp copied to clipboard
kubernetes-sigs
Support Flatcar linux for nodes
/kind feature
Describe the solution you'd like I would like to be able to use Flatcar linux for the control plane and worker nodes with CAPG.
Anything else you would like to add:
- Ignition support in CAPI
- Issue: https://github.com/kubernetes-sigs/cluster-api/issues/3430
- PR: https://github.com/kubernetes-sigs/cluster-api/pull/4172
- Flatcar feature request in CAPA - https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/1979
- Flatcar feature request in CAPZ - https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/629
That sounds like a great addition are you willing to work on this @AverageMarcus?
It's not something I'm currently able to work on but I wanted to make sure the feature was at least tracked here as Flatcar has a ticket tracking progress across various providers - https://github.com/flatcar-linux/Flatcar/issues/445
We (Giant Swarm) are starting to work with GCP and CAPG so this will eventually be something we'd like to have but not top priority for us currently.
@AverageMarcus I though you meant you want to work on this with like to be able to. My bad!
Umm! if you can reference any PR that has made the changes, I can have a look at it.
It's not something I'm currently able to work on but I wanted to make sure the feature was at least tracked here as Flatcar has a ticket tracking progress across various providers - flatcar-linux/Flatcar#445
We (Giant Swarm) are starting to work with GCP and CAPG so this will eventually be something we'd like to have but not top priority for us currently.
Here's the PR in CAPA adding support - https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/2271
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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