Enable DevOps System

KubeSphere DevOps System is designed for CI/CD workflow in Kubernetes. It is based on Jenkins and provides one-stop DevOps console helping developers and maintainers build, test and publish their applications to Kubernetes in a straight-forward way. It also supports plugins management, Binary-to-Image (B2I), Source-to-Image (S2I), code dependency caching, code quality analysis and pipeline logging, etc.

The DevOps system combines application development and automatic publishing on the same platform, also supports to connect with third-party private image registry (e.g. Harbor) and code repositories (e.g. GitLab/GitHub/SVN/BitBucket) to visually construct a complete CI/CD pipeline which is usually useful for air gapped environment.

• : Automatically pack your artifact such as WAR, JAR, Binary executables into Docker without writing Dockerfile and push to image repository, and finally deploy the image into Kubernetes cluster.
• Source to Image: Automatically compile and build your source code from code repository and pack the result into Docker without writing Dockerfile, push to image repository and finally deploy the image into Kubernetes cluster.
• : If your code repository already has Jenkinsfile, you’d better to use this way to create pipeline.
• GitLab and Harbor based CI/CD pipeline：Using on-premise GitLab and Harbor to create pipeline, which is useful for air gapped environment.

KubeSphere DevOps system requires at least 34m of CPU request and 2.69G of memory request for all-in-one installation, or at least 0.47 core of CPU request and 8.6G of memory request for multi-node installation. Please make sure your cluster has enough resource.

If you already have a minimal KubeSphere setup, you still can edit the ConfigMap of ks-installer using the following command.

Then set devops from False to .