Lost Access To CNCC Because "cncc-iam-kc" STS Can't Be Rescheduled (Doc ID 2932541.1)

Last updated on MARCH 07, 2023

Applies to:

Goal

We had confirmed that STS pods are not rescheduled automatically when a node goes down, and this impacting the service as fellow: there is one single replica for "cncc-iam-kc" STS so when the node which is hosting this pod goes down we lose access to CNCC.
So we need your help to answer these questions:
Is it expected that each time the node(on which this keycloak pod is running) goes down, the access to CNCC is lost?
Why this "cncc-iam-kc" is a stateful pod(knowing that it doesn't have no PVC associated to it)?
How can we overcome this?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.