linkerd / linkerd/linkerd-examples
External IP in pending state after running "kubectl get svc/linkerd"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 444
- Forks
- 216
- PR merge metrics
- No merged PRs in 30d
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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100