Discussion: Cluster integration is a pain point for local dev
Goal: Standardize on a set of best practices/minimize pain points
-
Find out what folks across GitLab are currently doing to handle development w/ clusters. -
Share any helpful scripts you have! -
Create a walk-through of minikube setup & process.
Context from Monitor team call:
Sarah Y: Long setup times for prometheus/metrics dashboard - are other people experiencing the same & are there alternatives worth considering?
- Tristan: +1 for experiencing this too. E.g. there’s an indeterminate wait between setting up a cluster and being able to install Helm. The lack of feedback makes this less efficient.
- Josh: Maybe we can all switch over to the AutoDevOps method, which lets you easily use GKE for a cluster instead of minikube and running it all locally? It sets up a internet facing proxy over a VPN to use. https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/howto/auto_devops.md
- Peter has tried KIND and k3s:
- kind works but is not persistent yet (restarting docker doesn’t work yet)
- k3s has certs problems
- Minikube works pretty well though
- Ben: Maybe we should do a walkthrough of our setups and figure out how we need to standardize… upload to GitLab unfiltered
Edited by Peter Leitzen