# OpenSearch Operator cluster stuck after TLS cert renewal – security not initialized

**URL:** <https://forum.opensearch.org/t/opensearch-operator-cluster-stuck-after-tls-cert-renewal-security-not-initialized/27663>\
**Category:** Security\
**Created:** [January 5, 2026, 5:31pm UTC](https://forum.opensearch.org/t/opensearch-operator-cluster-stuck-after-tls-cert-renewal-security-not-initialized/27663 "2026-01-05T17:31:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![v1k1ng0](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/v1k1ng0/32/9825_2.png) [@v1k1ng0](https://forum.opensearch.org/u/v1k1ng0)\
**Post date:** [January 5, 2026, 5:31pm UTC](https://forum.opensearch.org/t/opensearch-operator-cluster-stuck-after-tls-cert-renewal-security-not-initialized/27663/1 "2026-01-05T17:31:22Z")

</div>

Hello,

I’m running OpenSearch on Kubernetes using the **OpenSearch Operator** and I’m currently stuck after renewing TLS certificates. I’d appreciate confirmation on the correct recovery procedure.

**Environment**

- OpenSearch version: 2.11.1

- Deployment method: OpenSearch Operator (Helm)

- Kubernetes managed via Rancher

- TLS certificates generated by the operator (`security.tls.http.generate: true`, `security.tls.transport.generate: true`)

- Security configuration provided via `securityconfig-secret`

- LDAP + internal auth configured

- Multiple node pools: masters (3), datas, coordinators, mls

**What happened**

- One of the TLS certificates expired (PKIX / CertificateExpired errors).

- Pods started failing SSL handshakes and cluster communication.

- I deleted the expired TLS secrets (http/transport), and the operator correctly regenerated them with valid dates.

- After that, all OpenSearch pods start but remain in `Running` (not Ready).

- Logs on the master show repeatedly:

**Current state**

- `opensearch-operator-controller-manager` is running fine.

- The Job `opensearch-cluster-securityconfig-update` exists but is **Completed (1/1)** and does not rerun.

- No OpenSearch pod ever becomes Ready.

- Cluster health remains `unknown`.

**Important detail**  
The security configuration is fully defined in `securityconfig-secret` and referenced in the `OpenSearchCluster` CR:

```auto
security:
  config:
    adminCredentialsSecret: admin-credentials-secret
    securityConfigSecret: securityconfig-secret

```

No dynamic security changes were made outside this secret.

**Question**  
Is the correct and safe recovery step to:

1. Delete the completed Job `opensearch-cluster-securityconfig-update`

2. Let the operator recreate and rerun it to re-apply the same security configuration

3. Allow the cluster to initialize again

I want to confirm that:

- Deleting this Job will **not wipe users/roles beyond what is defined in `securityconfig-secret`**

- This is the expected procedure after TLS renewal when the cluster is no longer initialized

Any confirmation or recommended best practice would be very helpful.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![synhershko](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/synhershko/32/9861_2.png) [@synhershko](https://forum.opensearch.org/u/synhershko)\
**Post date:** [January 14, 2026, 6:52am UTC](https://forum.opensearch.org/t/opensearch-operator-cluster-stuck-after-tls-cert-renewal-security-not-initialized/27663/2 "2026-01-14T06:52:48Z")

</div>

Duplicate of [Cluster stuck in "Security not initialized" loop after TLS certificate rotation (2.11.1)](https://forum.opensearch.org/t/cluster-stuck-in-security-not-initialized-loop-after-tls-certificate-rotation-2-11-1/27711)

---

<div class="post-metadata">

**Author:** ![kris](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/kris/32/2208_2.png) [@kris](https://forum.opensearch.org/u/kris)\
**Post date:** [January 14, 2026, 7:47pm UTC](https://forum.opensearch.org/t/opensearch-operator-cluster-stuck-after-tls-cert-renewal-security-not-initialized/27663/3 "2026-01-14T19:47:26Z")

</div>

Closed on January 14, 2026, 7:47pm UTC


