Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-56082

[release-4.19]Backport UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      === Extended loopback certificate validity to three years for kube-apiserver

      Previously, the self-signed loopback certificate for the Kubernetes API Server expired after one year. With this release, the expiration date of the certificate is extended to three years.
      Show
      === Extended loopback certificate validity to three years for kube-apiserver Previously, the self-signed loopback certificate for the Kubernetes API Server expired after one year. With this release, the expiration date of the certificate is extended to three years.
    • Release Note Not Required
    • Done

      This is a clone of issue OCPBUGS-54208. The following is the description of the original issue:
      —
      Description of problem:

          In order to avoid self-signed loopback certificate in every apiserver from expiring we should cherrypick https://github.com/kubernetes/kubernetes/pull/130047 and backport it to 4.16.z

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

              vrutkovs@redhat.com Vadim Rutkovsky
              openshift-crt-jira-prow OpenShift Prow Bot
              Ke Wang Ke Wang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: