Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-2743

Unexpected upgrades due to TLS readiness mismatch

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 2.4.0
    • None
    • operator
    • None
    • 21: Auto., crackn' on Krakken
    • 1

    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

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              tommie Tommie McAfee (Inactive)
              tommie Tommie McAfee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty