Skip to content

[OSDOCS-16242]: Adding docs about HCP and the CNO #102820

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: main
Choose a base branch
from
Open

[OSDOCS-16242]: Adding docs about HCP and the CNO #102820

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
26 changes: 20 additions & 6 deletions hosted_control_planes/hcp-networking.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,27 +6,41 @@ include::_attributes/common-attributes.adoc[]

toc::[]

From a networking perspective, {hcp-capital} differs from {product-title} in its interactions with the Cluster Network Operator (CNO).

//cno and hcp
include::modules/hcp-cluster-network-operator.adoc[leveloffset=+1]

[role="_additional-resources"]
[id="additional-resources-hcp-cno_{context}"]
== Additional resources

* xref:../networking/networking_operators/cluster-network-operator.adoc#cluster-network-operator[Cluster Network Operator]

[id="hcp-proxy"]
== Proxy support for {hcp}

For standalone {product-title}, proxy support is mainly about ensuring that workloads in the cluster are configured to use the HTTP or HTTPS proxy to access external services, honoring the `NO_PROXY` setting if one is configured, and accepting any trust bundle that is configured for the proxy.

For {hcp}, proxy support involves the following additional use cases.

//cp workloads that need to use a proxy to access external services
include::modules/hcp-proxy-cp-workloads.adoc[leveloffset=+1]
include::modules/hcp-proxy-cp-workloads.adoc[leveloffset=+2]

//workers need a proxy to communicate with ignition endpoint
include::modules/hcp-proxy-ignition.adoc[leveloffset=+1]
include::modules/hcp-proxy-ignition.adoc[leveloffset=+2]

//workers need proxy to communicate with cp
include::modules/hcp-proxy-api.adoc[leveloffset=+1]
include::modules/hcp-proxy-api.adoc[leveloffset=+2]

//cp workloads that need access to external services and must use the proxy for the management cluster
include::modules/hcp-proxy-mgmt-cluster.adoc[leveloffset=+1]
include::modules/hcp-proxy-mgmt-cluster.adoc[leveloffset=+2]

//proxy configuration on the mgmt cluster when the hosted cluster has a secondary network and no default pod network
include::modules/hcp-proxy-addl-network.adoc[leveloffset=+1]
include::modules/hcp-proxy-addl-network.adoc[leveloffset=+2]

[role="_additional-resources"]
[id="additional-resources_{context}"]
[id="additional-resources-hcp-proxy_{context}"]
== Additional resources

* xref:../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[Configuring the cluster-wide proxy]
14 changes: 14 additions & 0 deletions modules/hcp-cluster-network-operator.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
// Module included in the following assemblies:
//
// * hosted_control_planes/hcp-networking.adoc

:_mod-docs-content-type: CONCEPT
[id="hcp-cluster-network-operator_{context}"]
= Cluster Network Operator and {hcp}

For {hcp}, networking features must be configured on the management cluster. In addition, not all fields and options for the Cluster Network Operator (CNO) are supported on {hcp}.

The following features in `network.operator.openshift.io` do not work in {hcp}:

* Hybrid networking with OVN-Kubernetes