Summary: | No documentation for how to change payload pull secret | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | David Eads <deads> |
Component: | Machine Config Operator | Assignee: | Antonio Murdaca <amurdaca> |
Status: | CLOSED ERRATA | QA Contact: | Micah Abbott <miabbott> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.0 | CC: | mnguyen, sponnaga |
Target Milestone: | --- | Flags: | amurdaca:
needinfo?
(deads) |
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:45:04 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: |
Description
David Eads
2019-03-06 18:31:44 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) 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 |