godaddy / godaddy/kubernetes-client
Getting a 404 when requesting ingresses on gcloud
- Dominant language
- JavaScript
- Stars
- 963
- Forks
- 189
- PR merge metrics
- No merged PRs in 30d
Description
Since a few weeks, the library is returning a `404` error when requesting old style ingress rules on gcloud:
```
await client.apis.extensions.v1beta1.ingresses.get()
```
It does not happen on our bare metal clusters or on Azure.
Any ideas what's going on?
Contributor guide
Research direction
Start by reproducing client.apis.extensions.v1beta1.ingresses.get() against a gcloud cluster and compare it with bare metal or Azure, as described in the report. Read the Kubernetes API-client entry points involved in that request and determine whether the 404 comes from the endpoint or request construction. Done means the cause is established and the supported ingress request behavior is covered by a verified regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, kubernetes, nodejs
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100