## Runner executor for K8S roadmap themes: ### Dogfooding the k8s executor - The Kubernetes executor needs more exposure. At the moment, it is only used by the customer relying on it and the developers working on it. This exposure could allow us to find many issues before they are found by the customers in their production setups. - The intent of this theme is to Dogfood using the GitLab Runner Operator starting first with installation and operations on Red Hat OpenShift. ### Migration to the Runner Operator - Today, we perform duplicate work supporting Helm Chart and the GitLab Runner Operator. The Operator provides a more powerful way to handle different improvements. Therefore, this theme aims to (1) address any feature parity gaps and (2) lay the groundwork for migrating from HELM chart installations to the Runner Operator fully. ### CI/CD Job monitoring on Kubernetes - GitLab Runner currently provides some information about the running job, but that information is not enough to provide the right pipeline data or metrics for runner execution on K8S that's critical for both pipeline reliability and efficiency. That metadata includes: - Stage duration - Specific k8s relation details: - image pulling time, artifact/cache restoration/uploading - relevant error/information that would help investigate a failure. We already have FF to retrieve/stream (warning) events but unfortunately, it is not always useful. ### Admissions controller for Kubernetes pod creation - Customers have complained about their jobs getting stuck in a "waiting for resources" state. This issue is often due to a lack of resources on the Kubernetes cluster, leading to numerous support requests for both Support and GitLab Runner team members. Our customer base is diverse, ranging from Kubernetes experts to users with only basic knowledge of Kubernetes. This variety in expertise results in a significant load of investigations and support requests for both the Support team and our team. ### PodSpec YAML complete Support - Customers want to better configure the job Pod. All Kubernetes properties cannot be supported in the config.toml and this unfortunately prevents access to them when using the config.toml - We currently have support for PodSpec in the config.toml, but the configuration provided doesn't always apply to all the jobs ran by the GitLab Manager. - We should allow user to provide custom PodSpec through the gitlab-ci YAML to solve those limitations while providing necessary tools to admins to better control what can be configured.