Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

External IP in pending state after running "kubectl get svc/linkerd"

Open
  • Is something wrong?
#166 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes
Domain
devops, infrastructure

Research direction

Start by reproducing the documented setup and running kubectl get svc/linkerd to confirm the External IP remains pending. Review the Linkerd service configuration and Kubernetes load-balancer requirements; done means identifying the cause and documenting a supported alternative or required setup.

Written by the indexing model from the issue text.

Description

I have followed your documentation and looks like when the service type is load balancer then the External Ip remains in the pending state.

kubectl get svc/linkerd

NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
linkerd 10.3.0.52 4140:31286/TCP,9990:30618/TCP 13m

Is there some alternative to this?

Dominant language
Go
Stars
444
Forks
216
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linkerd/linkerd-examples

All issues in linkerd/linkerd-examples

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.