Crc: Retrigger certificate rotation/generation for internal cluster communication

Created on 1 Mar 2019  路  11Comments  路  Source: code-ready/crc

Blocked by; https://github.com/openshift/api/pull/199

At the moment, this renders the cluster install useless for distribution, as the expired certificates prevent communication.

sizM

All 11 comments

The development/test window of 2h Validness/Refresh has been changed to a new default with https://github.com/openshift/cluster-kube-apiserver-operator/pull/338. Still waiting for more information about reprovisioning of certificates when the API server is unreachable/certificates are expired.

As mentioned by @sspeiche in the mail thread, now there's a proposal to automate the steps of certificate recovery: https://github.com/openshift/enhancements/pull/1

Interesting comment in the proposal:
https://github.com/openshift/enhancements/pull/1/files#diff-0c95263e1bf132f7346ccef277aec7fcR122

This process can be run by a laborious and error prone manual process that three existent teams have already had trouble with.

@derekwaynecarr suggested to describe our requirements as part of the OpenShift enhancement process.

A new issue has been created for the issue with 4.2 as a single node cluster: https://bugzilla.redhat.com/show_bug.cgi?id=1760181

@cfergeau can this be tested and verified by others?

@cfergeau can this be tested and verified by others?

The script is linux-only (hardcoded IP), but apart from this, yes, hopefully this should work on other people's machines.

@cfergeau @gbraad Just noticed this issue has been closed, does it mean the cert expiration issue happened w/ CRC has gone? If that's the case, does it mean we can stay at a certain OpenShift version, instead of keeping upgrading CRC monthly?

This will only work with the latest releases.

Was this page helpful?
0 / 5 - 0 ratings