summaryrefslogtreecommitdiffstats
path: root/roles/openshift_nfs/meta
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2018-01-11 09:23:49 -0800
committerGitHub <noreply@github.com>2018-01-11 09:23:49 -0800
commitdc6ee13c88384c4be0deca622dba9452c096a746 (patch)
treed956efb226637c28630cbf56418293d3048a85be /roles/openshift_nfs/meta
parent9ce10b8415cd53042e80520a918b4541a9e785d1 (diff)
parent53bd951747c03e181d0a3fcdb4f93354d7258ed6 (diff)
downloadopenshift-dc6ee13c88384c4be0deca622dba9452c096a746.tar.gz
openshift-dc6ee13c88384c4be0deca622dba9452c096a746.tar.bz2
openshift-dc6ee13c88384c4be0deca622dba9452c096a746.tar.xz
openshift-dc6ee13c88384c4be0deca622dba9452c096a746.zip
Merge pull request #6687 from jpeeler/sc-cert-fix
Automatic merge from submit-queue. Update deployment and apiserver with new certs Since new certificates are generated for every run, the apiservice caBundle needs updating in order to have the on disk CA match what is in Kubernetes. Because the secrets are updated, the daemonset needs to do a rolling update for the apiserver to pick up the new certs. Implemented here is an added annotation to the api server such that the update occurs automatically when the CA is changed. --- There may be a better way to make the rolling update occur without adding an annotation, such as within ansible itself (I just didn't know how to do that). Also, I think that probably the controller needs to be updated too in order to ensure staying in sync with the api server. Edit: I did not think that doing "oc apply" would cause the daemonset to pick up a change since the yaml may be exactly the same, but if it does then the annotation part can definitely be changed.
Diffstat (limited to 'roles/openshift_nfs/meta')
0 files changed, 0 insertions, 0 deletions