Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1686117 - No documentation for how to change payload pull secret [NEEDINFO]
Summary: No documentation for how to change payload pull secret
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.1.0
Assignee: Antonio Murdaca
QA Contact: Micah Abbott
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-06 18:31 UTC by David Eads
Modified: 2019-04-12 13:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:
amurdaca: needinfo? (deads)

Attachments (Terms of Use)

Description David Eads 2019-03-06 18:31:44 UTC
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.

Comment 1 Antonio Murdaca 2019-03-17 19:29:45 UTC
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)

Comment 2 Antonio Murdaca 2019-03-25 12:04:01 UTC
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.

Comment 3 Antonio Murdaca 2019-04-12 13:03:24 UTC
Opened this which contains a doc change as well

Note You need to log in before you can comment on or make changes to this bug.