我们在 GKE 上部署了 Strimzi 0.26.0（版本 - 1.30.5-gke.1014001） 资源 - Kafka、KafkaBrodge、KafkaUser 现在显示错误，原因是 - 未找到 poddisruptionbudgets
kubectl describe kafka versa-kafka-gke -n kafka
Status:
Conditions:
Last Transition Time: 2024-10-16T23:47:20.582Z
Message: Failure executing: POST at: https://10.44.0.1/apis/policy/v1beta1/namespaces/kafka/poddisruptionbudgets. Message: the server could not find the requested resource. Received status: Status(apiVersion=v1, code=404, details=StatusDetails(causes=[], group=null, kind=null, name=null, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=the server could not find the requested resource, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=NotFound, status=Failure, additionalProperties={}).
Reason: KubernetesClientException
Status: True
Type: NotReady
Observed Generation: 29
Events: <none>
strimzi 操作员 pod 中出现错误：
2024-10-17 18:27:20 WARN AbstractOperator:481 - Reconciliation #502876(timer) Kafka(kafka/versa-kafka-gke): Failed to reconcile
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://10.44.0.1/apis/policy/v1beta1/namespaces/kafka/poddisruptionbudgets. Message: the server could not find the requested resource. Received status: Status(apiVersion=v1, code=404, details=StatusDetails(causes=[], group=null, kind=null, name=null, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=the server could not find the requested resource, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=NotFound, status=Failure, additionalProperties={}).
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:693) ~[io.fabric8.kubernetes-client-5.8.0.jar:?]
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:672) ~[io.fabric8.kubernetes-client-5.8.0.jar:?]
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:625) ~[io.fabric8.kubernetes-client-5.8.0.jar:?]
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:565) ~[io.fabric8.kubernetes-client-5.8.0.jar:?]
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:526) ~[io.fabric8.kubernetes-client-5.8.0.jar:?]
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleCreate(OperationSupport.java:314) ~[io.fabric8.kubernetes-client-5.8.0.jar:?]
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:754) ~[io.fabric8.kubernetes-client-5.8.0.jar:?]
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:89) ~[io.fabric8.kubernetes-client-5.8.0.jar:?]
at io.fabric8.kubernetes.client.dsl.base.CreateOnlyResourceOperation.create(CreateOnlyResourceOperation.java:61) ~[io.fabric8.kubernetes-client-5.8.0.jar:?]
at io.strimzi.operator.common.operator.resource.AbstractResourceOperator.internalCreate(AbstractResourceOperator.java:273) ~[io.strimzi.operator-common-0.26.0.jar:0.26.0]
at io.strimzi.operator.common.operator.resource.AbstractResourceOperator.lambda$reconcile$0(AbstractResourceOperator.java:111) ~[io.strimzi.operator-common-0.26.0.jar:0.26.0]
at io.vertx.core.impl.ContextImpl.lambda$null$0(ContextImpl.java:159) ~[io.vertx.vertx-core-4.1.5.jar:4.1.5]
at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100) ~[io.vertx.vertx-core-4.1.5.jar:4.1.5]
at io.vertx.core.impl.ContextImpl.lambda$executeBlocking$1(ContextImpl.java:157) ~[io.vertx.vertx-core-4.1.5.jar:4.1.5]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [io.netty.netty-common-4.1.68.Final.jar:4.1.68.Final]
at java.lang.Thread.run(Thread.java:829) [?:?]
由于这些问题，Kafka、KafkaBridge 和 KafkaUsers 未显示为准备就绪， 顺便说一句，这些服务直到昨天我们对实体运营商进行了滚动重启
来自 Kafka Pod 的日志显示 SSL 连接问题，这可能与 KafkaBridge/KafkaUser 宕机有关
2024-10-17 19:04:53,146 INFO [SocketServer listenerType=ZK_BROKER, nodeId=0] Failed authentication with /10.142.0.103 (SSL handshake failed) (org.apache.kafka.common.network.Selector) [data-plane-kafka-network-thread-0-ListenerName(EXTERNAL-9094)-SSL-14]
2024-10-17 19:04:53,195 INFO [SocketServer listenerType=ZK_BROKER, nodeId=0] Failed authentication with /10.142.0.15 (SSL handshake failed) (org.apache.kafka.common.network.Selector) [data-plane-kafka-network-thread-0-ListenerName(EXTERNAL-9094)-SSL-13]
2024-10-17 19:04:53,207 INFO [SocketServer listenerType=ZK_BROKER, nodeId=0] Failed authentication with /10.40.1.1 (SSL handshake failed) (org.apache.kafka.common.network.Selector) [data-plane-kafka-network-thread-0-ListenerName(EXTERNAL-9094)-SSL-12]
2024-10-17 19:04:53,230 INFO [SocketServer listenerType=ZK_BROKER, nodeId=0] Failed authentication with /10.40.1.240 (SSL handshake failed) (org.apache.kafka.common.network.Selector) [data-plane-kafka-network-thread-0-ListenerName(REPLICATION-9091)-SSL-4]
2024-10-17 19:04:53,310 INFO [SocketServer listenerType=ZK_BROKER, nodeId=0] Failed authentication with /10.142.0.103 (SSL handshake failed) (org.apache.kafka.common.network.Selector) [data-plane-kafka-network-thread-0-ListenerName(EXTERNAL-9094)-SSL-13]
2024-10-17 19:04:53,365 INFO [SocketServer listenerType=ZK_BROKER, nodeId=0] Failed authentication with /10.40.1.240 (SSL handshake failed) (org.apache.kafka.common.network.Selector) [data-plane-kafka-network-thread-0-ListenerName(REPLICATION-9091)-SSL-5]
据我了解，Strimzi 0.26.0 引用了已弃用的 PDB 的“policy/v1beta1”API，而 Kubernetes 1.30 已弃用了“policy/v1beta1”..，因此导致了此问题，即 Strimzi 正在尝试使用检查 PDB Kubernetes 1.30 不支持 apiVersion 'policy/v1beta1'
我的理解正确吗？
我需要做什么才能让集群运行？ 我需要升级集群吗？有没有可以快速修复的方法？
请告诉我！
谢谢！
您必须升级 Strimzi 集群或降级 Kubernetes 版本。 0.26.0 已经有 3 年多了，Kubernetes 1.30 发布时根本不存在。