-
Notifications
You must be signed in to change notification settings - Fork 11
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
Added rancher-proxy package, proxy changes for custom clusters and rke2 packages #68
base: main
Are you sure you want to change the base?
Conversation
registry_ip: | ||
type: string | ||
readOnly: true | ||
description: "Public IP address of the proxy bastion node" | ||
registry_private_ip: | ||
type: string | ||
readOnly: true | ||
description: "Private IP address of the proxy bastion node" |
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.
Is this needed?
export HTTP_PROXY=http://${CORRAL_registry_private_ip}:3219 | ||
export HTTPS_PROXY=http://${CORRAL_registry_private_ip}:3219 | ||
export http_proxy=http://${CORRAL_registry_private_ip}:3219 | ||
export https_proxy=http://${CORRAL_registry_private_ip}:3219 | ||
export proxy_host=${CORRAL_registry_private_ip}:3219 |
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.
We already implemented half of the registry -> bastion rename output. Would this work if we used bastion_private_ip
instead of registry_private_ip
?
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.
LGTM, awaiting offline confirmation that this is good to merge.
No description provided.