We need to better equip our team so that they are blocked less frequently
The engineers (and sometimes UX designers) on the monitor team tend to get blocked during their development and or reviewing MRs because of their development environment (Eg. triaging minikube not working..etc). Our development time takes a hit and engineers are less productive as a result.
We need to better equip our team so that they are blocked less frequently by these issues. Currently it seems to waste a few days of development time per person each milestone (based on 1:1 conversations with team).
Proposals on how to better equip the team:
- Dedicate GKE workspace that the team can leverage.
- Engineers are constantly asked to remove their clusters from
gitlab-internal
because it is running out of IP space and is "wasting company money". GKE is known to be the fastest way for us to develop/review. During times in which engineers are blocked by minikube, it could be more effective for the team member to use GKE to get moving and resolve minikube at a later time. I think that is a more effective use of company resources. - GKE in general is also more stable than minikube
- Engineers are constantly asked to remove their clusters from
- Improve training resources for the team
- Video walkthroughs on
how to setup gdk + minikube
,how to setup gdk + gke
,how to test review apps + gke
,how to test cluster health charts
could be potential great resources for the team as a reference as well as onboarding.
- Video walkthroughs on
- Improved E2E tests for our charts could help us catch more bugs effectively
- Weekly or bi-weekly minikube/GKE debugging session to dedicate a time for the team to help each other get unstuck. We could also pull in team members from the configure team. Hopefully we could document the learnings from these meetings and eventually phase out these debugging meetings.