JTBD for Kubernetes Management
Goal
Have a verified list of JTBD for Kubernetes Management
We have three personas to think about:
- application operator
- platform engineer
- developer
Initial collection of user stories: https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/blob/master/doc/user_stories.md
Main Jobs
- When I have a new version of my application, I want to deploy it into production following my preferred deployment strategy, so that I can reap the fruits of my work and can celebrate success. - application operator
- When I push a new version into production, I want to monitor core metrics related to the deployment, so that I can be assured about the quality of the new release and act when necessary. - application operator
- When there is a problem with a just released version, I want an easy way to roll forward or backward. - application operator
- When I set up a new cluster, I want to make sure that application operators can easily target their developments at it, so they can start using the cluster immediately. - platform engineer
- When the engineers need a new cluster, I want to make sure that they can self-serve and the cluster will be set up following company requirements. - platform engineer
Scenarios
- Connect a cluster to GitLab and deploy a
nodejs
app on it using CI/CD - Connect a cluster to GitLab and deploy
nginx ingress
using pull based deployments
Definition of Done
Once you have your 1-2 job statements, add them to the JTBD SSoT (data/jobs_to_be_done.yml) and your category's (or group's) direction page.
Edited by Viktor Nagy (GitLab)