Changing a pull secret when it expires is a critical task for cluster maintenance. My pull secret became invalid and there was no documentation available for how to change it. Without a valid pull secret, upgrades don't work because new payloads cannot be retrieved.
I'm unsure on where do we need to have such docs, is the github repository and an md file enough? (dumb question, I suspect we need official docs but not sure where to ask)
In any case, changing the pullsecret for the cluster is done using the `coreos-pull-secret` secret from the namespace `kube-system`: oc get -o yaml secrets coreos-pull-secret -n kube-system The above will show the .dockerconfigjson pull secret, editing the object above will change the pull secrets to what provided and regenerate the related objects.
Opened this https://github.com/openshift/machine-config-operator/pull/632 which contains a doc change as well
PR merged with docs added to the repo
Verified documention is in codebase from PR https://github.com/openshift/machine-config-operator/pull/632 and verified steps in $ oc adm release info Name: 4.1.0-0.okd-2019-05-07-153426 Digest: sha256:6beec1fa752f80230c6cd4f6ac1f9301937aefa76c92b7328719b4e340d2136f Created: 2019-05-07T15:34:36Z OS/Arch: linux/amd64 Manifests: 289
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days