Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support Flatcar linux for nodes #540

Open
AverageMarcus opened this issue Feb 23, 2022 · 11 comments
Open

Support Flatcar linux for nodes #540

AverageMarcus opened this issue Feb 23, 2022 · 11 comments
Assignees
@jayesh-srivastava
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@AverageMarcus
Copy link
Member

/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:
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 23, 2022
@AverageMarcus AverageMarcus mentioned this issue Feb 23, 2022
Closed
15 tasks
@sayantani11
Copy link
Contributor

/assign @AverageMarcus

@cpanato
Copy link
Member

cpanato commented Feb 23, 2022

That sounds like a great addition are you willing to work on this @AverageMarcus?

@AverageMarcus
Copy link
Member Author

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/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.

@sayantani11
Copy link
Contributor

@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.

@sayantani11
Copy link
Contributor

/unassign @AverageMarcus

@AverageMarcus
Copy link
Member Author

Here's the PR in CAPA adding support - kubernetes-sigs/cluster-api-provider-aws#2271

@jayesh-srivastava
Copy link
Member

/assign

@alex-dabija alex-dabija mentioned this issue Apr 12, 2022
Closed
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 29, 2022
@AverageMarcus
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 29, 2022
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 27, 2022
@AverageMarcus
Copy link
Member Author

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 27, 2022
@t-lo t-lo mentioned this issue Jan 4, 2023
Open
@tormath1 tormath1 mentioned this issue Oct 25, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jayesh-srivastava jayesh-srivastava

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@AverageMarcus @cpanato @k8s-ci-robot @jayesh-srivastava @k8s-triage-robot @sayantani11