Skip to content
This repository has been archived by the owner on Apr 25, 2019. It is now read-only.

[Task] Check how pull secret can be modified for the cluster. #30

Open
praveenkumar opened this issue Feb 4, 2019 · 1 comment
Open

Comments

@praveenkumar
Copy link
Member

As of now, we know that pull secret is part of the secrets/coreos-pull-secret and that is in the etcd database, to make change we need to edit it. This task is to check once we edit it does it sustain a reboot?

$ oc edit secrets/coreos-pull-secret -o yaml -n kube-system
<---Edit the base64 encoded Pull secret to new one -->
@praveenkumar
Copy link
Member Author

I tested to edit the secrets/coreos-pull-secret and then reboot the system and it comes up with changed one which means during start=>stop=>start scenario we are good in case we change it for the specific user.

Another thing is we can't put there a place holder but we need to have a dummy pull secret which can be identified as a pull secret by the validator.

$ ./oc edit secrets/coreos-pull-secret -o yaml -n kube-system
error: secrets "coreos-pull-secret" is invalid
A copy of your changes has been stored to "/tmp/oc-edit-kdv1n.yaml"
error: Edit cancelled, no valid changes were saved.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant