New message center and cluster compliance scoring function, KubeOperator V2.5 is released 丨 Release Notes

On April 13, the open source container platform KubeOperator released version V2.5. KubeOperator V2.5 version adds new functions such as message center, cluster compliance score, and LDAP connection. At the same time, the Argo CD continuous deployment tool is added to the Kubeapps Plus application store, which can completely cover CI / CD application scenarios.

new features

1. Message Center

With the help of the message center, cluster administrators can receive timely notifications when abnormal clusters occur. Currently supported message types include:

● Cluster installation events, such as cluster installation success / failure;

● Cluster scaling events, such as cluster scaling success / failure;

● Cluster uninstallation events, such as cluster uninstallation success / failure;

● Cluster event alarms, such as worker node down, insufficient CPU / memory / disk resources, and failure to start the Pod process due to image pull failure.



▲ Figure 1 Click the cluster event alarm to view detailed information

The current message receiving methods include: internal letter, mail, enterprise WeChat and Dingding. Enterprises can set the receiving source according to their own needs, as shown in Figure 2:

▲ Figure 2 Setting the message receiving source in the message center

2. Cluster compliance score

The cluster compliance scoring function can help cluster administrators to intuitively understand the overall health status of the cluster and quickly locate usage within the cluster that does not meet best practices. KubeOperator's checkpoints include:

● Whether fixed IP and PID are set;

● Whether the file system is read-only;

● Whether to run the container with root authority;

● Whether the request value and limit value of CPU / memory are set;

● Whether the label is a built-in specific label, such as Master;

● Whether the mirroring policy is standardized;

● Whether fixed network and port are set;

● Whether the Liveness and Readiness probes of the health check are normal, etc.

▲ Figure 3 Cluster compliance scoring interface

3. The application store adds Argo CD to completely cover the application scenarios of CI to CD

Argo CD is a continuous deployment tool for Kubernetes that follows the declarative GitOps philosophy. Argo CD can automatically synchronize and deploy applications when Git repositories change. Its advantages include:

1. Application definition, configuration and environment information are declarative and can be versioned;

2. Application deployment and life cycle management are fully automated and auditable, clear and easy to understand;

3. Argo CD is an independent deployment tool that can evolve independently and supports unified deployment and management of applications on multiple environments and multiple Kubernetes clusters.

Combined with the existing GitLab, Jenkins, and Harbor in the Kubeapps Plus app store, KubeOperator can help companies implement the entire CI / CD process.

▲ Figure 4 CI / CD process topology based on Argo CD in Kubernetes

▲ Figure 5 The Kubeapps Plus application store provides various applications required by the CI / CD process

4. LDAP connection

KubeOperator V2.5 version supports LDAP connection to achieve unified user authentication.

▲ Figure 6 supports LDAP unified identity authentication

Bug fix

1. Fix the bug that some Helm external application warehouse failed to sync to Kubeapps Plus application store;

2. Fix the bug that the event can still be seen after the cluster is uninstalled;

3. Fix the bug of F5 service exposure failure;

4. Fix the bug that the Nexus repeatedly reports errors and causes the log file to be too large.

Optimization and improvement

1. The Kubeapps Plus application store adds a label function, which can be used to categorize applications;

2. KubeOperator uses Gunicorn to run, effectively improve HTTP processing performance;

3. Move the Kubernetes Dashboard and Weave-scope from the original built-in application to the Kubeapps Plus application store;

4. Support Excel batch import to host;

5. Realize batch expansion of cluster worker nodes in manual mode;

6. In addition to the original Trafik, the Ingress solution supports Nginx-ingress.