In AMQ Streams, encountered KubernetesClientException during patch the Kafka custom resource
Issue
Once we upgrade the AMQ Stream Operator, we encountered this problem in our Kafka status:
status:
conditions:
- lastTransitionTime: "2023-MM-DDTHH:mm:ss"
message: 'Failure executing: PATCH at: https://xxxxxx:443/api/v1/namespaces/xxxx/services/my-cluster-zookeeper-client. Message: the server rejected our request due to an error in our request. Received status: Status(apiVersion=v1, code=422, details=StatusDetails(causes=[], group=null, kind=null, name=null, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=the server rejected our request due to an error in our request, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Invalid, status=Failure, additionalProperties={}).'
reason: KubernetesClientException
status: "True"
type: NotReady
observedGeneration: ##
Environment
AMQ Streams 2.x
Openshift 4.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.