End of Maintenance Check
Rule Details
Parameter |
Description |
---|---|
Rule Name |
cce-cluster-end-of-maintenance-version |
Identifier |
End of Maintenance Check |
Description |
If the version of a CCE cluster is no longer supported for maintenance, this cluster is non-compliant. |
Tag |
cce |
Trigger Type |
Configuration change |
Filter Type |
cce.clusters |
Rule Parameters |
None |
Application Scenarios
CCE strictly complies with community consistency authentication. It releases three Kubernetes versions each year and offers a maintenance period of at least 24 months after each version is released. CCE ensures the stable running of Kubernetes versions during the maintenance period.
To ensure your service rights and benefits, upgrade your Kubernetes clusters before a maintenance period ends. You can check the Kubernetes version of your cluster on the cluster list page and check whether a new version is available. Proactive cluster upgrades help you:
- Reduce security and stability risks: During the iteration of Kubernetes versions, known security and stability vulnerabilities are continuously fixed. Long-term use of EOS clusters will result in security and stability risks to services.
- Experience the latest functions: During the iteration of Kubernetes versions, new functions and optimizations are continuously released. For details about the features of the latest version, see the release notes for CCE cluster versions.
- Minimize compatibility risks: During the iteration of Kubernetes versions, APIs are continuously modified and functions are deprecated. If a cluster has not been upgraded for a long time, more O&M assurance investment will be required when the cluster is upgraded. Periodic upgrades can effectively mitigate compatibility risks caused by accumulated version differences. It is a good practice to upgrade a patch version every quarter and upgrade a major version to the latest version every year.
- Obtain more effective technical support: CCE does not provide security patches or issue fixing for EOS Kubernetes cluster versions, and does not ensure technical support for the EOS versions.
For the versions that have reached EOS, see the Cluster Version Release Notes.
Solution
Rule Logic
- If the version of a CCE cluster is no longer supported for maintenance, the cluster is non-compliant.
- If the version of a CCE cluster is still supported for maintenance, the cluster is compliant.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot