Kubernetes upgrade notes: 1.26.x to 1.27.x
If you used my Kubernetes the Not So Hard Way With Ansible blog posts to setup a Kubernetes (K8s) cluster this notes might be helpful for you (and maybe for others too that manage a K8s cluster on their own e.g.). I’ll only mention changes that might be relevant because they will either be interesting for most K8s administrators anyways (even in case they run a fully managed Kubernetes deployment) or if it’s relevant if you manage your own bare-metal/VM based on-prem Kubernetes deployment. I normally skip changes that are only relevant for GKE, AWS EKS, Azure or other cloud providers.
I’ve a general upgrade guide Kubernetes the Not So Hard Way With Ansible - Upgrading Kubernetes that worked quite well for me for the last past K8s upgrades. So please read that guide if you want to know HOW the components are updated. This post here is esp. for the
1.27.x upgrade and WHAT was interesting for me.
As usual I don’t update a production system before the
.2 release of a new major version is released. In my experience the
.1 are just too buggy. Nevertheless it’s important to test new releases (and even beta or release candidates if possible) already in development environments and report bugs!
I only upgrade from the latest version of the former major release. At the time writing this blog post
1.26.8 was the latest
1.26.x release. After reading the 1.26 CHANGELOG to figure out if any important changes where made between the current
1.26.x and latest
1.26.8 release I didn’t see anything that prevented me updating and I don’t needed to change anything.
So I did the
1.26.8 update first. If you use my Ansible roles that basically only means to change
k8s_release variable from
1.26.8 and deploy the changes for the control plane and worker nodes as described in my upgrade guide.
After that everything still worked as expected so I continued with the next step.
As it’s normally no problem to have a newer
kubectl utility that is only one major version ahead of the server version I updated
1.26.x to latest
1.27.x using my kubectl Ansible role.
Since K8s 1.14 there are also searchable release notes available. You can specify the K8s version and a K8s area/component (e.g. kublet, apiserver, …) and immediately get an overview what changed in that regard. Quite nice! 😉
As always before a major upgrade read the Urgent Upgrade Notes! If you used my Ansible roles to install Kubernetes and used most of the default settings then there should be no need to adjust any settings. For K8s
1.27 release I actually couldn’t find any urgent notes that were relevant for my Ansible roles or my own on-prem setup.
In general K8s
1.27 seems to be quite “conservative” if it comes to breaking changes if you manage a K8s cluster 😉
- SeccompDefault graduates to stable I’ve written about that already in my Kubernetes
1.23upgrade notes when this feature was in Alpha state. As this is a really useful security related feature please also check Enable default seccomp profile which was part of the upgrade notes mentioned above. It contains some more useful information esp. how to test once this feature was enabled.
- DownwardAPIHugePages graduates to stable In Kubernetes v1.20, support for
limits.hugepages-<pagesize>was added to the downward API to be consistent with other resources like cpu, memory, and ephemeral storage. This feature graduates to stable in this release.
- Pod Scheduling Readiness goes to beta
- Node log access via Kubernetes API This feature helps cluster administrators debug issues with services running on nodes by allowing them to query service logs e.g. For example, to fetch the
kubeletlogs from a node, you can run:
kubectl get --raw "/api/v1/nodes/node-1/proxy/logs/?query=kubelet". Also see Kubernetes 1.27: Query Node Logs Using The Kubelet API
- ReadWriteOncePod PersistentVolume access mode goes to beta Kubernetes v1.22 introduced a new access mode
ReadWriteOncePodfor PersistentVolumes (PVs) and PersistentVolumeClaims (PVCs). This access mode enables you to restrict volume access to a single pod in the cluster, ensuring that only one pod can write to the volume at a time. This can be particularly useful for stateful workloads that require single-writer access to storage.
- Faster SELinux volume relabeling using mounts
- CSIStorageCapacity The
storage.k8s.io/v1beta1API version of
CSIStorageCapacitywill no longer be served in v1.27.
- Support for the alpha seccomp annotations
container.seccomp.security.alpha.kubernetes.iowere deprecated since v1.19, now have been completely removed. The seccomp fields are no longer auto-populated when pods with seccomp annotations are created. Pods should use the corresponding pod or container securityContext.seccompProfile field instead.
For more information see:
- Added warnings about workload resources (Pods, ReplicaSets, Deployments, Jobs, CronJobs, or ReplicationControllers) whose names are not valid DNS labels.
- Adds feature gate NodeLogQuery which provides cluster administrators with a streaming view of logs using kubectl without them having to implement a client side reader or logging into the node.
- Encryption of API Server at rest configuration now allows the use of wildcards in the list of resources. For example, . can be used to encrypt all resources, including all current and future custom resources.
Kubelet Topology Managerto GA.
KubeletTracing(Kubelet OpenTelemetry Tracing) to beta, which means that the feature gate is now enabled by default.
- Graduated seccomp profile defaulting to GA. Also see Enable default seccomp profile and seccomp tutorial
CronJobTimeZonefeature to GA
- The PodDisruptionBudget
spec.unhealthyPodEvictionPolicyfield has graduated to beta and is enabled by default. On servers with the feature enabled, this field may be set to
AlwaysAllowto always allow unhealthy pods covered by the
PodDisruptionBudgetto be evicted.
APIServerTracingfeature gate is now enabled by default. Tracing in the API Server is still disabled by default, and requires a config file to enable.
PodSpec.Container.Resourcesbecame mutable for CPU and memory resource types. That’s a pretty insteresting in-place Pod vertical scaling feature as it allows to change CPU and memory setting without restarting a pod. Also In-Place Update of Pod Resources
--image-service-endpointto kubelet config
StatefulSetto control start replica ordinal numbering graduating to beta. Also see Kubernetes 1.27: StatefulSet Start Ordinal Simplifies Migration
kubectlwill now display SeccompProfile for pods, containers and ephemeral containers, if values were set.
- Kubelet TCP and HTTP probes are now more effective using networking resources: conntrack entries, sockets. This is achieved by reducing the TIME-WAIT state of the connection to 1 second, instead of the defaults 60 seconds. This allows kubelet to free the socket, and free conntrack entry and ephemeral port associated.
kubelet: remove deprecated flag
CoreDNS: Updated to
etcd: Updated to
If you use CSI then also check the CSI Sidecar Containers documentation. Every sidecar container contains a matrix which version you need at a minimum, maximum and which version is recommend to use with whatever K8s version.
Nevertheless if your K8s update to
v1.27 worked fine I would recommend to also update the CSI sidecar containers sooner or later.
- Kubernetes v1.27: Chill Vibes
- Kubernetes 1.27 – What’s new?
- Kubernetes 1.27: More fine-grained pod topology spread policies reached beta
- Kubernetes 1.27: Efficient SELinux volume relabeling (Beta)
- Kubernetes 1.27: Single Pod Access Mode for PersistentVolumes Graduates to Beta
- Kubernetes 1.27: Avoid Collisions Assigning Ports to NodePort Services
- Kubernetes 1.27: In-place Resource Resize for Kubernetes Pods (alpha)
- Kubernetes 1.27 Release: Enhancements and Security Updates
- Effortless In-Cluster Validation with Kubernetes: Introducing Validating Admission Policies - Streamlining Kubernetes Resource Validation with Validating Admission Policies and CEL
Now I finally upgraded the K8s controller and worker nodes to version
1.27.x as described in Kubernetes the Not So Hard Way With Ansible - Upgrading Kubernetes.
That’s it for today! Happy upgrading! ;-)