-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
OSDOCS-2466: Created configuration instructions for cluster-wide proxy. #39830
OSDOCS-2466: Created configuration instructions for cluster-wide proxy. #39830
Conversation
✔️ Deploy Preview for osdocs ready! 🔨 Explore the source changes: d7decb3 🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/61f815304feae00007858a78 😎 Browse the preview: https://deploy-preview-39830--osdocs.netlify.app/openshift-rosa/latest/networking/configuring-cluster-wide-proxy |
9dee857
to
17be367
Compare
modules/osd-cluster-wide-proxy.adoc
Outdated
<other arguments here> \ | ||
--additional-trust-bundle-file $CA_BUNDLE_FILE \ | ||
--http-proxy $HTTP_PROXY \ | ||
--https-proxy $HTTPS_PROXY |
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.
This card has not been implemented yet. It isn't ok to expose this function.
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.
@yingzhanredhat it is the expectation that when this feature and documentation goes live, both ocm
and rosa
CLI will support it. We have confirmation that ocm
is expected to match the arguments of rosa
so I think it is safe to leave in as part of this PR.
7e6a0b3
to
94ddb9c
Compare
modules/osd-cluster-wide-proxy.adoc
Outdated
<other arguments here> \ | ||
--additional-trust-bundle-file <path-to-CA-bundle-file> \ | ||
--http-proxy http://<username>:<pswd>@<ip>:<port> \ | ||
--https-proxy https://<username>:<pswd>@<ip>:<port> |
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.
--https-proxy
field can also use **http**://<username>:<pswd>@<ip>:<port>
Do we need to explain?
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.
I think <other arguments here>
is simple.User will confuse about how to configure
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.
Agree on the https-proxy
point. Not sure what is the best way to represent that.
Maybe
--https-proxy https://<username>:<pswd>@<ip>:<port> | |
--https-proxy http(s)://<username>:<pswd>@<ip>:<port> |
Regarding the <other arguments here>
, I also agree that it is simplistic, but I am not sure what is the best way to represent that other arguments will be required when creating a cluster (and we can't be able to predict what each customer's individual argument set may look like). Maybe we just point them at the install docs? (ie https://docs.openshift.com/rosa/rosa_getting_started/rosa-installing-rosa.html)
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.
@mrbarge @yingzhanredhat Fixed the address with the http(s)
change, but for the link, would this be the OSD version? https://docs.openshift.com/dedicated/osd_cluster_create/creating-your-cluster.html
I can add a note in the considerations section with a link to the respective documentation.
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.
If only link to the creating cluster url, it is still confused. I think we should point that user need prepare a CCS cluster with VPC which the proxy can be accessible.
@EricPonvelle This is looking good, thank you! I added a couple more comments but am otherwise happy. |
c926b7e
to
6baf3ae
Compare
8ea8c3a
to
240586a
Compare
@mrbarge Check out the updates to the ROSA documentation. I conditioned the CCS item to only display on the OSD side. Is this correct? |
Thanks @EricPonvelle ! Yes that looks good to me. |
@EricPonvelle I will verify the command when the it is ready.And everything else is fine |
@yingzhanredhat Re GCP that's a good point, I will sync with you separately on that topic outside of this PR concerning the state of GCP support. |
(With regards to GCP support) I think for now it's fine to leave it as-is, just in case we're able to go live with GCP support included. Even if someone tries to run the command for a GCP cluster and we don't have GCP support yet, they will receive the message "cluster_wide_proxy is only supported for AWS clusters" so it will be self-explanatory what the problem is. |
240586a
to
299370a
Compare
0635d7e
to
1001255
Compare
/lgtm |
1001255
to
d7decb3
Compare
/lgtm |
/cherry-pick enterprise-4.9 |
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.
Reviewed for OSD output. After leveloffset fix, seems copacetic to me.
/cherry-pick enterprise-4.10 |
@EricPonvelle: new pull request created: #41219 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@EricPonvelle: new pull request created: #41220 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR adds cluster-wide proxy information to the OSD and ROSA documentation.
JIRA: https://issues.redhat.com/browse/OSDOCS-2466
PREVIEW: