User journey for Kubernetes environments management
Problem description
As a Platform engineer, I want to set up a process where features can be deployed automatically/on-request to ephemeral environments so that Software Developers don't have to learn anything about the underlying infrastructure.
As a Platfrom engineer, I want to manage my environments and their connection with GitLab from code.
User steps to arrange in the journey:
- Configure Gitlab to support both ephemeral and long-running environments
- Configure Gitlab to clean up when an environment is stopped
- Start a new feature branch
- Deploy the feature branch into an ephemeral environment
- Connect the ephemeral environment with GitLab
- Connect a long-running environment with GitLab
- Merge/Close the feature branch, remove it from GitLab
We envision the "Connect an environment with GitLab" as described in Introduce `Environment` kind CRD for grouping r... (#352186 - closed)
Proposal
I recorded a short video of why I think it's not trivial.
Edited by Viktor Nagy (GitLab)