cluster-api-provider-aws icon indicating copy to clipboard operation
cluster-api-provider-aws copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Support EKS Pod Identity

Open richardcase opened this issue 1 year ago • 8 comments
trafficstars

/kind feature

Describe the solution you'd like

Add support for EKS Pod Identity to CAPA for EKS clusters. This will be an alternative to IRSA and is simpler as it doesn't require creation of OIDC providers

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

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

richardcase avatar Jan 19 '24 08:01 richardcase

/priority important-shorterm /triage accepted /area provider/eks

richardcase avatar Jan 19 '24 08:01 richardcase

@richardcase: The label(s) priority/important-shorterm cannot be applied, because the repository doesn't have them.

In response to this:

/priority important-shorterm /triage accepted /area provider/eks

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Jan 19 '24 08:01 k8s-ci-robot

/priority important-soon

richardcase avatar Jan 19 '24 08:01 richardcase

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Deprioritize it with /priority important-longterm or /priority backlog
  • 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 avatar Apr 21 '24 17:04 k8s-triage-robot

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 avatar Jul 20 '24 18:07 k8s-triage-robot

/remove-lifecycle stale

richardcase avatar Jul 20 '24 18:07 richardcase