We are deprecating the certificate-based integration with Kubernetes in GitLab 14.5

GitLab is transitioning from its certificate-based Kubernetes integration, introduced in 2018, to the more secure and reliable GitLab Agent for Kubernetes, which became available in 2020. This shift is driven by the inherent security risks and limitations of the certificate-based system, such as requiring elevated cluster-admin privileges and exposing the Kubernetes API, issues that are mitigated by the Agent. The deprecation of the certificate-based integration will affect all related features, which will be removed starting with GitLab 15.0, although self-managed users can temporarily revert to them until complete removal. The GitLab Agent offers several advantages, including enhanced security, scalability, and support for modern GitOps approaches, with functionalities that allow cluster configuration through code and seamless integration with existing GitLab CI/CD workflows. GitLab plans to address the Agent’s observability shortcomings and offer solutions to simplify Auto DevOps and Auto Deploy setups, ensuring GitLab-Managed Clusters continue to function effectively. The company seeks user feedback to prioritize the migration and development of new features based on the Agent and encourages sharing experiences to refine the integration's capabilities.

No tracked trend matches for this post yet.