DevConf.CZ

Detecting To-Be-Removed APIs for Kubernetes Upgrade Readiness
06-15, 11:00–11:35 (Europe/Prague), E104 (capacity 72)

Are you an SRE planning a Kubernetes upgrade but unsure about your workload's compatibility? Join us for a presentation featuring an open-source Ansible role designed to automate the detection of to-be-removed APIs in your workload. Learn to use this role on a cluster with your deployed workload, to generate JUnit output that indicates compatibility with different Kubernetes versions: 'workload is compatible with x.y' or 'workload is incompatible with x.z because the following APIs used will be removed in x.z.'

This development was done for a practical use case: upgrading from OpenShift 4.11 to OpenShift 4.12 while ensuring compatibility with Keysight Open RAN SIM CE, a complex telco workload with 20+ operators. We’ll review existing approaches to detect soon-to-be-removed APIs and their limitations, and highlight the benefits of the APIRequestCount API we chose. Short demos will showcase our approach with real-life examples.

See also: