Can we support ubuntu 22.04?

kubernetes-sigs / cluster-api-provider-aws

Kubernetes Cluster API Provider AWS provides consistent deployment and day 2 operations of "self-managed" and EKS Kubernetes clusters on AWS.

http://cluster-api-aws.sigs.k8s.io/

Apache License 2.0

642 stars 567 forks source link

Can we support ubuntu 22.04? #4050

Open worstkid92 opened 1 year ago

worstkid92 commented 1 year ago

/kind feature

Describe the solution you'd like [A clear and concise description of what you want to happen.] Only kernel 5.10+ support cilumn ebbf feature. We'd like to use ebpf to replace kube-proxy.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] https://docs.cilium.io/en/v1.10/gettingstarted/kubeproxy-free/

Environment:

Cluster-api-provider-aws version: main
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

Ankitasw commented 1 year ago

Thanks for raising this issue. It could be a potential candidate for our roadmap.

/triage accepted /priority important-longterm

k8s-triage-robot commented 8 months ago

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

Confirm that this issue is still relevant with /triage accepted (org members only)
Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

k8s-triage-robot commented 5 months ago

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

k8s-triage-robot commented 4 months ago

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