Description
This is a side effect of the fix to K8S-2589
Causing ReadinessProbe port to differ on pods created by 2.3.0 than previous releases.
Therefore, upgrading tls clusters will always result in Pod upgrade because a diff is detected in the PodSpec.
Specifically, 2.2.0 readiness code hardcoded 8091 even with TLS
container.ReadinessProbe = &v1.Probe{
|
Handler: v1.Handler{
|
TCPSocket: &v1.TCPSocketAction{
|
Port: intstr.FromInt(8091), |
},
|
},
|
vs 2.3.0
if cluster.IsTLSEnabled() { |
port = AdminServicePortTLS
|
}
|
|
|
|
|
container.ReadinessProbe = &v1.Probe{
|
ProbeHandler: v1.ProbeHandler{
|
TCPSocket: &v1.TCPSocketAction{
|
Port: intstr.FromInt(port),
|
},
|
},
|
Attachments
Issue Links
- blocks
-
K8S-2757 Cloud Native Verification fix : 2.3.0-VF
-
- Resolved
-
| For Gerrit Dashboard: K8S-2743 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 175680,2 | K8S-2743: Only set tls readiness for strict mode | 2.3.x | couchbase-operator | Status: MERGED | +2 | +1 |