Skip to content

[rhacs] Fix yaml callouts #102971

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: rhacs-docs-main
Choose a base branch
from
Open

[rhacs] Fix yaml callouts #102971

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 11 additions & 4 deletions modules/configure-proxy-during-installation.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,14 +57,21 @@ stringData:
# username: username
# password: password
----
* `username` and `password` are optional, both at the beginning and in the `http` and `https` sections.
* `url` supports the following URL schemes:
+
where:

`username` and `password`:: (Optional) Specifies the username and password. These fields are optional at the beginning and in the `http` and `https` sections.

`url`:: Specifies the URL of the proxy. Supports the following URL schemes:
+
** `http://` for an HTTP proxy
** `https://` for a TLS-enabled HTTP proxy
** `socks5://` for a SOCKS5 proxy
* `excludes` is a list that can contain DNS names, with or without `*` wildcards, IP addresses, or IP blocks in CIDR notation, for example, `10.0.0.0/8`.

`excludes`:: Specifies a list of DNS names, with or without `*` wildcards, IP addresses, or IP blocks in CIDR notation, for example, `10.0.0.0/8`.
The values in this list are applied to all outgoing connections, regardless of protocol.
* `|-` in the `stringData` section indicates the start of the configuration data.

`|-`:: Specifies the start of the configuration data when inserted into the `stringData` section.
+
[NOTE]
====
Expand Down
2 changes: 1 addition & 1 deletion modules/configure-proxy-on-an-existing-deployment.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ To configure a proxy in an existing deployment, you must export the `proxy-confi
====
If you have configured a global proxy on your {ocp} cluster, the Operator Lifecycle Manager (OLM) automatically configures Operators that it manages with the cluster-wide proxy. However, you can also configure installed Operators to override the global proxy or inject a custom certificate authority (CA) certificate.

For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/operators/administrator-tasks#olm-configuring-proxy-support[Configuring proxy support in Operator Lifecycle Manager].
For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-latest-version}/html/operators/administrator-tasks#olm-configuring-proxy-support[Configuring proxy support in Operator Lifecycle Manager].
====

.Procedure
Expand Down