1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/rosa_hcp/rosa-hcp-cluster-no-cni.adoc
Janelle Neczypor d71844a4d5 OSDOCS-11777
2024-10-08 19:18:33 +00:00

48 lines
2.8 KiB
Plaintext

:_mod-docs-content-type: ASSEMBLY
[id="rosa-hcp-cluster-no-cli"]
= {hcp-title} clusters without a CNI plugin
include::_attributes/attributes-openshift-dedicated.adoc[]
include::_attributes/common-attributes.adoc[]
:context: rosa-hcp-cluster-no-cni
toc::[]
You can use your own Container Network Interface (CNI) plugin when creating a {hcp-title-first} cluster.
You can create a {hcp-title} cluster without a CNI and install your own CNI plugin after cluster creation.
[IMPORTANT]
====
For customers who choose to use their own CNI, the responsibility of CNI plugin support belongs to the customer in coordination with their chosen CNI vendor.
====
The default plugin for {hcp-title} is the xref:../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc#about-ovn-kubernetes[OVN-Kubernetes network plugin]. This plugin is the only Red Hat supported CNI plugin for {hcp-title}.
If you choose to use your own CNI for {hcp-title} clusters, it is strongly recommended that you obtain commercial support from the plugin vendor before creating your clusters. Red Hat support cannot assist with CNI-related issues such as pod to pod traffic for customers who choose to use their own CNI. Red Hat still provides support for all non-CNI issues. If you want CNI-related support from Red Hat, you must install the cluster with the default OVN-Kubernetes network plugin. For more information, see the xref:../rosa_architecture/rosa_policy_service_definition/rosa-policy-responsibility-matrix.adoc#rosa-policy-responsibility-matrix[responsibility matrix].
[id="rosa-hcp-no-cni-cluster-creation"]
== Creating a {hcp-title} cluster without a CNI plugin
=== Prerequisites
* Ensure that you have completed the xref:../rosa_planning/rosa-sts-aws-prereqs.adoc[AWS prerequisites].
* Ensure that you have a configured xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc#rosa-hcp-creating-vpc[virtual private cloud] (VPC).
include::modules/rosa-hcp-creating-account-wide-sts-roles-and-policies.adoc[leveloffset=+2]
include::modules/rosa-sts-byo-oidc.adoc[leveloffset=+2]
include::modules/rosa-operator-config.adoc[leveloffset=+2]
[role="_additional-resources"]
[id="additional-resources_rosa-hcp-operator-prefix-no-cni"]
.Additional resources
* See xref:../rosa_architecture/rosa-sts-about-iam-resources.adoc#rosa-sts-about-operator-role-prefixes_rosa-sts-about-iam-resources[About custom Operator IAM role prefixes] for information on the Operator prefixes.
include::modules/rosa-hcp-sts-creating-a-cluster-cli-no-cni-plugin.adoc[leveloffset=+1]
[id="next-steps-2_{context}"]
== Next steps
* Install your CNI plugin. The nodes will then change from the `not ready` to `ready` state.
* Access your ROSA cluster with the xref:../rosa_install_access_delete_clusters/rosa-sts-accessing-cluster.adoc#rosa-sts-accessing-cluster[Accessing a ROSA cluster] documentation.