openshift-ci-robot
commented
5 months ago @tjungblu: This pull request references ETCD-607 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.
In response to [this](https://github.com/openshift/cluster-etcd-operator/pull/1269):
>Drafting, since we're waiting for #1268 to merge first
>---
>
>This implements a gate to avoid triggering leaf cert generation in the
>same static pod revision as an update to the signer certificates (and
>their respective bundles).
>
>This PR also removes the openshift-config dependency on signer
>certificates. With 4.17 we should be safe to remove any reference, as
>the newly generated signer certificate in openshift-etcd should already
>be distributed and ready for consumption.
>
>In plain words: an upgrade to 4.17 will automatically rotate your etcd
>signer certificates for the first time and every refresh period happily
>ever after.
>
Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-etcd-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci[bot]
tjungblu
hasbro17
This implements a gate to avoid triggering leaf cert generation in the same static pod revision as an update to the signer certificates (and their respective bundles).
This PR also removes the openshift-config dependency on signer certificates. With 4.17 we should be safe to remove any reference, as the newly generated signer certificate in openshift-etcd should already be distributed and ready for consumption.
In plain words: an upgrade to 4.17 will automatically rotate your etcd signer certificates for the first time and every refresh period happily ever after.