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.

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

Recommendations for using ALB with Karpenter #2747

Open
chrisnegus opened this issue Aug 2, 2022 · 4 comments
Open

Recommendations for using ALB with Karpenter #2747

chrisnegus opened this issue Aug 2, 2022 · 4 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@chrisnegus
Copy link

Is your feature request related to a problem?
Not particularly.

Describe the solution you'd like
Guidance for using ALB with Karpenter.

Describe alternatives you've considered
We are removing the FAQ entry from the Karpenter docs related to using the AWS load balancer controller with Karpenter. We were thinking that the ALB docs would be a more appropriate place for this type of guidance.

@kishorj
Copy link
Collaborator

kishorj commented Aug 5, 2022

/kind documentation

@k8s-ci-robot k8s-ci-robot added the kind/documentation Categorizes issue or PR as related to documentation. label Aug 5, 2022
@kishorj kishorj added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Aug 5, 2022
@johngmyers
Copy link
Contributor

Whether the node provisioner is Karpenter or not has little relevance to the choice of target type. The only thing is that Karpenter is more likely than other provisioners to end up with nodes of disparate sizes.

If one is using a CNI with a masqueraded pod network then one needs to use "instance". Otherwise one should use "ip".

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages 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 PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this 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 Feb 8, 2023
@orsenthil orsenthil removed their assignment Jun 16, 2023
@hakanbakacak
Copy link

Hello, I would like to contribute to this issue. Where do you think is the appropriate place to put this document?

Also can you share the AWS load balancer controller with Karpenter page. Maybe I can prepare a document using the information the FAQ page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

7 participants