-
Hi there, I’m using the RMQ Kubernetes Operator to manage an RMQ cluster on GKE. Recently, I got an alert saying some API clients in my cluster tried to use a v1beta1 API that was removed in Kubernetes 1.25. I checked this documentation about the deprecation: Can you help me understand the impact of this, since there doesn’t seem to be a v1 version for the RMQ Operator? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The API being used is In the user agent you can observe "python". This gives you a hint that the app calling this API is written in Python, therefore, there's some app or service in your Kubernetes cluster, written in Python, that's calling the Pod security policies removed API. |
Beta Was this translation helpful? Give feedback.
The API being used is
v1beta1
ofPodSecurityPolicies
. This API was removed by Kuberneetes upstream in 1.25, as the warning rightly points out. This is unrelated to RabbitMQ operator. Versionv1beta1
ofRabbitmqCluster
is fully supported, with no plans to deprecate in the near future.In the user agent you can observe "python". This gives you a hint that the app calling this API is written in Python, therefore, there's some app or service in your Kubernetes cluster, written in Python, that's calling the Pod security policies removed API.