Description of problem: As of Kubernetes 1.16 deprecation of selLink has been announced. With Kubernetes 1.20 it will be disabled, thus it will not be propagated with all the objects sent/retrieved from API. In Kuryr-Kubernetes there are several places where selLink information is used and relied on. How reproducible: Steps to Reproduce: 1. Upgrade to Kubernetes 1.20 or pass parameter "--feature-gates=RemoveSelfLink=true" in versions prior to 1.20 2. Run the stack 3. Try to create some pod/deployment Actual results: Failure on Kuryr controller due to lack of selfLink key in several places Expected results: Create pod/deployment without any issue
Verified on OCP4.7.0-0.nightly-2021-01-27-110023 on OSP16.1 (RHOS-16.1-RHEL-8-20201214.n.3) with OVN-Octavia. All kuryr-tempest-plugin, NP and Conformance tests are passing. Logs attached. selflink is still enabled on OCP4.7 nightly builds, so tests are passing without actually testing the scenario where selflink is disabled. It is agreed that we will cover this as soon as selflink is disabled through our CI jobs.
Created attachment 1751614 [details] test results with the fix
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633