-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
accept pull-secret when we use hack script to create a clsuter #3486
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you tested what happens if you leave the environment variable empty? Does cluster creation still work?
yes it does. also |
/azp run ci, e2e |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run ci |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run e2e, ci |
Azure Pipelines successfully started running 2 pipeline(s). |
LGTM, as a follow-up, can you add a comment to our doc to document the use of this new var: |
Which issue this PR addresses:
This is the same PR as #3360 but it was made from a branch not a fork to pass the E2E.
What this PR does / why we need it:
There is no way to specify pull-secret when we use the hack script to create a cluster.
When testing the installer, if the installer image is hosted in quay.io, hive doesn't changes the domains of other images required during installation to ACR domain and it causes Authentication error if it doesn't have the pull-secret.
This pull-secret enables us to access to those images in quay.io and make the installer test convenient.
Test plan for issue:
I was able to create a cluster with ACR domain installer and quay.io domain installer.