Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-1203

Update MCO kube-rbac-proxy templates to use tlsSecurityProfile

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • MCO Sprint 256, MCO Sprint 257
    • 0

      With the global tlsSecurityProfile available in renderconfig(or some other local store), the operator can now inject these as new "templated" arguments into the MCC & MCD deployment manifests. These are the standard kube rbac proxy containers launched alongside the MCO containers. This would mean that the MCC/MCS will redeployed if there is an update to the global tlsSecurityProfile.

      Done when:

      • The tls-ciperhsuites and tls-min-version arguments of kube-rbac-proxy sidecars are dynamically updated when the APIServer object is updated with new tlsSecurityProfile settings

              djoshy David Joshy
              djoshy David Joshy
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: