[Starlingx-discuss] Your v1.18 Certified Kubernetes Expires May 26, 2021 - IMPORTANT

Ildiko Vancsa ildiko.vancsa at gmail.com
Thu May 20 14:17:58 UTC 2021


Hi Greg,

Thanks for the quick reply. Sadness that we cannot certify right away.

It was very short notice. :( I also didn’t follow when v1.19 came out. Need to track deadlines more closer in the future if the certification is a priority for the community.

Well, let’s do things as planned and then we will certify again once the platform has the newer version and is stable enough to run the test suite.

Thanks,
Ildikó


> On May 20, 2021, at 14:44, Waines, Greg <Greg.Waines at windriver.com> wrote:
> 
> Nope ☹ .
> They didn’t give us much warning did they.
>  
> Work has not begun yet on moving to higher versions of kubernetes.  It is a starlingx r6 activity that is planned, but work is likely not starting for a month or so … and would be a month or so before we would be ready to do the certification.
>  
> Greg.
>  
> From: Ildiko Vancsa <ildiko.vancsa at gmail.com> 
> Sent: Thursday, May 20, 2021 8:31 AM
> To: StarlingX ML <starlingx-discuss at lists.starlingx.io>
> Subject: [Starlingx-discuss] Fwd: Your v1.18 Certified Kubernetes Expires May 26, 2021 - IMPORTANT
>  
> [Please note: This e-mail is from an EXTERNAL e-mail address]
> Hi StarlingX Community, 
>  
> I’ve just received this reminder email that our Kubernetes certification expires soon.
>  
> Based on the email below we need to certify STarlingX with a Kubernetes version v1.19 or above __before May 26th__ in order to keep the v1.18 certification as well.
>  
> Do we have a high enough version in StarlingX 5.0 to proceed? If so, do we have a volunteer who can run the test suite so I can upload the results to get certified again?
>  
> Thanks and Best Regards,
> Ildikó
>  
> 
> 
> Begin forwarded message:
>  
> From: Erin Thacker <ethacker at linuxfoundation.org>
> Subject: Your v1.18 Certified Kubernetes Expires May 26, 2021
> Date: May 19, 2021 at 23:20:06 GMT+2
> To: ildiko at openstack.org
>  
> Hello Open Infrastructure Foundation,
>  
> We’re very pleased that your product was included in our v1.18 Certified Kubernetes offerings. However, unless you have acquired a newer certification for your product, StarlingX, your Kubernetes v1.18 certification will expire on May 26, 2021.  Any previous certifications you have for this product will expire as well.
>  
> As stated in Certified Kubernetes Conformance Program – Terms and Conditions, a Participant’s permission to use the Certified Kubernetes Marks and Participant Kubernetes Combinations with its Qualifying Offerings is time-limited. The Certified Kubernetes Marks and Participant Kubernetes Combinations may be used with a Qualifying Offering for a particular version of Kubernetes (e.g., Kubernetes x.y) until the later of:
>  
> 	• 12 months after the release date of Kubernetes x.y, or
> 	• 9 months after the release date of the next minor release (e.g., Kubernetes x.y+1)
>  
> v1.18.0 was released on March 25, 2020
> https://github.com/kubernetes/kubernetes/releases/tag/v1.18.0
>  
> v1.19.0 was released on August 26, 2020
> https://github.com/kubernetes/kubernetes/releases/tag/v1.19.0
>  
> Therefore, the expiration date for v1.18 is May 26, 2021.
>  
> Please make sure to certify your product for Kubernetes v1.19, v1.20, or v1.21 prior to May 26th, in order to have your v1.18 certification remain in effect.  
>  
> To view all Certified Kubernetes Distributions & Platforms, please follow this link:
> https://docs.google.com/spreadsheets/d/1LxSqBzjOxfGx3cmtZ4EbB_BGCxT_wlxW_xgHVVa23es
>  
> If you have any questions, please don’t hesitate to reach out.
>  
> Erin Thacker
> Project Coordinator
> Cloud Native Computing Foundation
> 




More information about the Starlingx-discuss mailing list