vpnkit-expose-port-controller should emit service events
Open
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 1.2k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
We could make good use of events API to provide information to the user, especially in cases of errors, but also inform/remind that services of type NodePort or LoadBalancer are accessible using localhost:<nodePort>.
For example, here is what a GKE user sees when they change service type:
> kubectl describe svc test
Name: default
Namespace: test
Labels: <none>
Selector: app=test
Type: LoadBalancer
IP: 10.39.248.110
Port: <unset> 80/TCP
TargetPort: 8080/TCP
NodePort: <unset> 30482/TCP
Endpoints: 10.24.0.2:8080
Session Affinity: None
External Traffic Policy: Cluster
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Type 2s service-controller NodePort -> LoadBalancer
Normal CreatingLoadBalancer 2s service-controller Creating load balancer
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 locating the vpnkit-expose-port-controller entry point and the events API it would use. Review how NodePort and LoadBalancer services are currently handled, then define completion around emitting user-visible events for service-type changes, errors, and localhost access details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, ocaml
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100