Observation
On a TemporalCluster with spec.MTLS unset (mTLS disabled), the status still includes an MTLSReady = True condition with reason CertificatesReady / message "all certificates are ready". The operator UI (#63) correctly hides the mTLS Overview row when spec.MTLS == nil, but the Conditions table then shows MTLSReady: OK, which is misleading for a cluster that has no mTLS configured.
Ask
Investigate the MTLSReady condition lifecycle:
- When
spec.MTLS == nil, either omit the MTLSReady condition entirely, or set it to a non-applicable state (e.g. reason MTLSDisabled) rather than True/"all certificates are ready".
Repro
- Cluster
temporal-test/test (no spec.MTLS) shows MTLSReady OK in the UI conditions table while no mTLS row appears in Overview.
Related to #63.
Observation
On a TemporalCluster with
spec.MTLSunset (mTLS disabled), the status still includes anMTLSReady = Truecondition with reasonCertificatesReady/ message "all certificates are ready". The operator UI (#63) correctly hides the mTLS Overview row whenspec.MTLS == nil, but the Conditions table then showsMTLSReady: OK, which is misleading for a cluster that has no mTLS configured.Ask
Investigate the MTLSReady condition lifecycle:
spec.MTLS == nil, either omit theMTLSReadycondition entirely, or set it to a non-applicable state (e.g. reasonMTLSDisabled) rather thanTrue/"all certificates are ready".Repro
temporal-test/test(nospec.MTLS) showsMTLSReadyOK in the UI conditions table while no mTLS row appears in Overview.Related to #63.