openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 09:46:53 +01:00
Code Issues Releases Activity

Merge pull request #35960 from MirzWeiss/TELCODOCS-303

Browse Source 
TELCODOCS-303: Added additional resources at the bottom of the assembly with info about the operator in disconnected mode
This commit is contained in:
Vikram Goyal
2021-10-18 23:11:41 +10:00
committed by GitHub
parent 4b76479189 12c983b9bd
commit 5dc2bf5744
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
sandboxed_containers/deploying-sandboxed-container-workloads.adoc
View File

@@ -37,3 +37,9 @@ include::modules/sandboxed-containers-triggering-installation-kata-runtime.adoc[
include::modules/sandboxed-containers-selecting-nodes.adoc[leveloffset=+3]
include::modules/sandboxed-containers-scheduling-workloads.adoc[leveloffset=+3]
include::modules/sandboxed-containers-viewing-workloads-from-cli.adoc[leveloffset=+2]
[id="{context}_additional-resources"]
== Additional resources
* The {sandboxed-containers-operator} is supported in a restricted network environment. For more information, xref:../operators/admin/olm-restricted-networks.adoc#olm-restricted-networks[Using Operator Lifecycle Manager on restricted networks].
* When using a disconnected cluster on a restricted network, you must xref:../operators/admin/olm-configuring-proxy-support.adoc#olm-configuring-proxy-support[configure proxy support in Operator Lifecycle Manager] to access the OperatorHub. Using a proxy allows the cluster to fetch the {sandboxed-containers-operator}.