WIP: Configure bootstrap for insecure registry with ignition#820
WIP: Configure bootstrap for insecure registry with ignition#820derekhiggins wants to merge 1 commit intoopenshift-metal3:masterfrom
Conversation
No longer build a custom version
|
Doesn't work, get the following warning during cluster create any ideas ? |
|
Hmm I've seen that before when either assets generated in the earlier installer stages (e.g generated manifests etc) get modified, or if there is a long delay between the generation of the ignition-config so that e.g certs need to be regenerated. Not sure why either would happen in this case though... |
|
Yup, we saw this before, but it was because the generated install-config.yaml wasn't identical to the one we created by the shell script, it was just a missing field that wasn't really relevant to anything. It looks like you're modifying the bootstrap ignition, I'm not sure you can do that when doing IPI installs, maybe ask the installer team on slack if there's a way to make it ignore the discrepancy? |
| if [ -e ./assets/generated/99_local-registry.yaml ] ; then | ||
| cp ${assets_dir}/install-config.yaml{.tmp,} | ||
| $OPENSHIFT_INSTALLER --dir "${assets_dir}" --log-level=debug create ignition-configs | ||
| yq .spec.config.storage.files[0] ./assets/generated/99_local-registry.yaml | \ |
There was a problem hiding this comment.
Where is it specified that yq is a requirement to run dev-scripts?
There was a problem hiding this comment.
It's installed along with the other dependencies here:
It'd be nice to remove that requirement since it's a pip install, there are other approaches we could use such as https://github.com/ashcrow/filetranspiler but for now yq works.
|
We can probably just close this, the approach being discussed in |
|
closing per comment from @derekhiggins |
4 participants
No longer build a custom version