Deploy Stage FY25 Roadmap
Kubernetes Dashboard
The built-in Kubernetes dashboard will allow application operators to understand the status of their applications and support debugging without leaving GitLab.
For technical reasons, the dashboard will not support port-forwarding, and metrics integration is currently not planned. The latter will depend on the work of ~"group::observability".
The primary target user is the application operator, but infrastructure engineers might rely on the dashboard too.
For the buyer persona, the built-in dashboard removes the need to give direct access to clusters to developers that often require cloud account management, thus improving the security of the stack and reducing its complexity.
Supporting materials
Related work items
Remove the cert-based Kubernetes integration
We deprecated the certificate-based integration in favour of the GitLab agent for Kubernetes in GitLab 15.0. Our data shows minimal usage, but we don't have very reliable data, and there is occasional customer feedback that they can not migrate away from the cert-based integration to the agent-based integration because of missing functionality.
We collect the issues blocking the removal in https://gitlab.com/gitlab-org/configure/general/-/issues/199+. Once the issues are shipped, we should give at least 4 months to our customers to migrate (and giving only 4 months will cause a lot of headaches to our users).
Supporting materials
Related work items
Enterprise FluxCD SKU
See https://gitlab.com/gitlab-com/Product/-/issues/13665+ for details
Delivery framework
Today, GitLab users need to build their own frameworks and tooling to support develop self-service application delivery processes. (e.g. Runway is GitLab's internal delivery tool) We want to provide a framework, a set of conventions and supporting tooling that when followed will enable platform teams to define the processes and templates, and enable developers to self-serve their application delivery and related infrastructure provisioning needs.
While we might ship a specific flavor of templates together with the delivery framework, extending the IaC capabilities of GitLab is not in scope here. We want to build upon the existing Terraform/Tofu and Kubernetes integrations to provide the application delivery framework.
Supporting materials
Related work items
Not planned
Single-page deployment approvals
The current deployment approvals functionality built around multiple approval rules while quite flexible, it's hard to manage as part of a pipeline as the approval is the property of a job depending on its environment.
Moreover, as approval related functionalities were added iteratively to GitLab, the related UI was always squeezed in to various places. In the end, it's not possible to provide a direct link to a pending approval and it's difficult to find the collaboration that happened around an approval.
We want to offer a dedicated page around deployment approvals and we want to build approvals into the pipeline as special jobs.
The current Environment list includes 2-levels of collapsibles. We want to change this by moving at least the cluster UI into the environment detail page.
Supporting materials
Related work items
- Category Epic: Deployment approvals (gitlab-org&9992)
- External CI jobs MVC (gitlab-org&10866)
- Move the cluster UI component under the environ... (gitlab-org/gitlab#431746 - closed)
Add Services to GitLab
We learned through user research that the current model of Projects and Environments does not fit the mental model of our users. Users prefer to think in terms of Applications composed of Services, deployed to Environments. GitLab misses the Application and Service resources. (Glossary)
We want to add a Service resource to GitLab and integrate it into application delivery processes, including Environments, Deployment approvals and Releases. We are working with ~"group::observability" to add service-level metrics to services.
The initial iteration will add service views at the project level, focusing on data already available in GitLab.
Supporting materials
Related work items
- Designs for the first MVC
- Overall epic (includes issues not in scope for this issue)
Group and organization level services lists
We learned through user research that the current model of Projects and Environments does not fit the mental model of our users. Users prefer to think in terms of Applications composed of Services, deployed to Environments. GitLab misses the Application and Service resources. (Glossary)
While Group level environment views were an often requested feature for years when we run solution validation and did more research, we learned that what users really want are services lists at the group and organization levels. We learned as well that the project level service concept generalizes easily to group and organization levels.