Chkk’s Project Upgrade Recommendation feature identifies which Cloud Native Projects, application services, and operators in your clusters require upgrading, which upgrades are optional, and which can remain unchanged. Powered by Chkk’s Collective Learning, the feature evaluates factors such as end-of-life (EOL) status, compatibility with your target Kubernetes version, known operational risks, and any enterprise policies you’ve defined (for example, preferring the latest version or sticking with stable releases). Based on these assessments, Chkk classifies each Cloud Native Project, application service, and operator upgrade as Required, Optional, or Not Recommended. A Project upgrade is deemed Required if it faces major compatibility concerns or presents critical risks. Optional upgrades are flagged when the Project remains compatible but may be outdated or has known issues. For each Required or Optional upgrade, Chkk recommends a target version that meets criteria such as compatibility, production mileage, and freedom from known risks. If your organization’s internal standards differ from Chkk’s recommendations—whether you prefer to upgrade all Cloud Native Projects, application services, and operators or only those that are required—you can override the suggested version. Chkk will factor in your feedback during Template Regeneration, producing updated recommendations tailored to your policies. By integrating these upgrade insights directly into your workflow, Chkk helps shorten research time, manage complex Cloud Native Project dependencies, and maintain smooth cluster operations with minimal disruptions. The image below shows an example of a Cluster Upgrade Template with Project Upgrade Recommendations:Documentation Index
Fetch the complete documentation index at: https://docs.chkk.io/llms.txt
Use this file to discover all available pages before exploring further.
