In {product-title} version {product-version}, you can install a cluster with a customized network configuration on infrastructure that the installation program provisions on Microsoft Azure. By customizing your network configuration, your cluster can coexist with existing IP address allocations in your environment and integrate with existing MTU and VXLAN configurations.
You must set most of the network configuration parameters during installation,
and you can modify only kubeProxy configuration parameters in a running
cluster.
modules/nw-network-config.adoc modules/nw-modifying-operator-install-config.adoc modules/nw-operator-cr.adoc modules/configuring-hybrid-ovnkubernetes.adoc
|
Note
|
For more information about using Linux and Windows nodes in the same cluster, see Understanding Windows container workloads. |
-
For more details about Accelerated Networking, see Accelerated Networking for Microsoft Azure VMs.
By default, administrator secrets are stored in the kube-system project. If you configured the credentialsMode parameter in the install-config.yaml file to Manual, you must use one of the following alternatives:
-
To manage long-term cloud credentials manually, follow the procedure in Manually creating long-term credentials.
-
To implement short-term credentials that are managed outside the cluster for individual components, follow the procedures in Configuring an Azure cluster to use short-term credentials.
To install a cluster that uses {entra-first}, you must configure the Cloud Credential Operator utility and create the required Azure resources for your cluster.
-
See Accessing the web console for more details about accessing and understanding the {product-title} web console.
-
If necessary, you can opt out of remote health reporting.