split service from workload resource
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Andy in the tilt channel asks:
is there a way to mark a k8s resource as not part of a tilt resource? i.e. I've got a k8s deployment that also has a k8s service, and if I hit the rebuild it deletes the service and the deployment and then starts them both back up, but the service is part of a GCP ingress, so recreating the service causes the whole GCP ingress to have to update and can take a minute or 2.
I don't think there's a straightforward way to do this right now :(
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
No source file, test, or entry point is named. Start by tracing how Kubernetes resources are grouped and deleted during a rebuild, then determine how a service could be kept separate from its workload. Done means the workload can rebuild without recreating the service or forcing the GCP ingress to update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100