A few months ago, CNCF introduced the CARE Program — Certification Advancement & Recertification Experience — to make it easier for certified professionals to keep their credentials current as they continue growing their cloud native skills.
CARE was designed with a simple idea in mind: certification should recognize ongoing learning, not create unnecessary renewal friction. Since launch, we have continued listening to feedback from the community, especially from candidates and Kubestronauts managing multiple certification timelines. Today, we are introducing the next step in that work.
Starting June 18, passing the Certified Kubernetes Security Specialist (CKS) exam or recertifying your CKS will automatically reinstate or extend your Certified Kubernetes Administrator (CKA) certification.
What is changing?
If you achieve or recertify CKS, your CKA certification will be updated to match the expiration date of your new CKS certification. This applies whether your CKA is still active or has already expired.
In practice, that means one successful CKS exam can now keep both your CKS and CKA certifications current. For candidates who naturally move from Kubernetes administration into Kubernetes security, this creates a simpler and more practical renewal path.
Why CKS and CKA?
CKS builds directly on the knowledge and hands-on skills covered by CKA. Candidates preparing for CKS are expected to understand Kubernetes administration deeply enough to secure clusters, workloads, networking, and runtime environments.
Because of that relationship, passing CKS is a strong signal that a candidate continues to demonstrate the core Kubernetes administration skills represented by CKA.
This update recognizes that progression more clearly.
What this means for Kubestronauts
For Kubestronauts, maintaining five active Kubernetes certifications at the same time can require careful planning. CKA and CKS are both part of that path, and until now, candidates often had to manage separate renewal windows for both.
With this update, renewing your CKS can also bring CKA back into good standing or extend its validity. That gives Kubestronauts and aspiring Kubestronauts one less renewal cycle to manage, while still preserving the value and rigor of the certification path.
Reducing renewal friction
The goal of CARE is not to make certification easier. The goal is to make certification maintenance more aligned with how people actually grow their skills.
Many Kubernetes professionals begin with CKA and later move into security-focused roles or responsibilities. When they continue advancing and pass CKS, the certification program should recognize that progress.
What should candidates do next?
If your CKA is close to expiring, or if it has already expired, achieving CKS can now reinstate or extend it. If you are already preparing for CKS, no additional step is required. Once you pass or renew CKS, your CKA expiration date will be updated to match your CKS expiration date.
The CARE Program will continue to evolve based on feedback from the community. Thank you to everyone who shared their experience, raised questions, and helped us identify where the certification journey could be improved.
We look forward to seeing more candidates continue their Kubernetes journey through CKS, Kubestronaut, and beyond.