<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 14/02/23 08:53, Kendall Nelson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJ6yrQgEnKCesqJAEoE9nOtM5JOwAS7DoQ5oep_zcPW6XesuBg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">Hello
All! </div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">First of
all, I want to say a huge thanks to Guilherme Steinmuller for
all his help ensuring that OpenStack Magnum remains Kubernetes
Certified [1]! We are certified for v1.24!</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">However,
in digging into the set of conformance tests this round, it
appears that we will not be able to get 1.25 certified with
the current Magnum. This means that in May when we have to
re-cert (every 3 months they reach an EOL because that's k8s
release cadence) we will not be able to maintain this which is
the other part of why I wanted to write this email - to raise
awareness and ask for help digging into what needs to happen
to make sure we can retain this. </div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">Tangentially
related, Guilherme has posted a patch with documentation for
how to run the conformance tests for yourself and it could use
some reviews [2]. </div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small"> </div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">And one
last thing, I have begun conversation with the opendev folks
about what it might take to setup jobs to run the conformance
tests periodically so that we don't have to manually run them
when it's time to recert. I am planning on submitting a forum
topic for this for those interested :) </div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">Long
live LOKI!</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">-
Kendall Nelson</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">[1] <a
href="https://github.com/cncf/k8s-conformance/pull/2446"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/cncf/k8s-conformance/pull/2446</a></div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">[2] <a
href="https://review.opendev.org/c/openstack/magnum/+/849156"
moz-do-not-send="true" class="moz-txt-link-freetext">https://review.opendev.org/c/openstack/magnum/+/849156</a></div>
</div>
</blockquote>
<p><br>
</p>
<p>Hi Kendall,</p>
<p><br>
</p>
<p>I have submitted Kubernetes Conformance tests for 1.24[1] and
1.25[2] for Catalyst Cloud, which is Openstack Magnum (Wallaby,
with several backports).</p>
<p>I've submitted the required changes upstream to Magnum for a few
fixes, including Calico, containerd and Fedora CoreOS 37 support.<br>
</p>
<p>Do you know which tests are currently failing for 1.25? Perhaps
there are some changes we've not submitted yet, or a differing
Magnum template.<br>
</p>
<br>
<p>cheers,</p>
<p>Dale</p>
<p><br>
</p>
<p>[1] <a class="moz-txt-link-freetext" href="https://github.com/cncf/k8s-conformance/pull/2388">https://github.com/cncf/k8s-conformance/pull/2388</a></p>
<p>[2] <a class="moz-txt-link-freetext" href="https://github.com/cncf/k8s-conformance/pull/2414">https://github.com/cncf/k8s-conformance/pull/2414</a></p>
<p><br>
</p>
<p></p>
</body>
</html>