mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
95 lines
4.1 KiB
Plaintext
95 lines
4.1 KiB
Plaintext
:context: post-install-network-configuration
|
|
[id="post-install-network-configuration"]
|
|
= Post-installation network configuration
|
|
include::modules/common-attributes.adoc[]
|
|
include::modules/ossm-document-attributes.adoc[]
|
|
toc::[]
|
|
|
|
After installing {product-title}, you can further expand and customize your
|
|
network to your requirements.
|
|
|
|
[id="post-install-configuring-network-policy"]
|
|
== Configuring NetworkPolicy with OpenShift SDN
|
|
|
|
Understand and work with network policy.
|
|
|
|
include::modules/nw-networkpolicy-about.adoc[leveloffset=+2]
|
|
include::modules/nw-networkpolicy-object.adoc[leveloffset=+2]
|
|
include::modules/nw-networkpolicy-create.adoc[leveloffset=+2]
|
|
include::modules/nw-networkpolicy-delete.adoc[leveloffset=+2]
|
|
include::modules/nw-networkpolicy-view.adoc[leveloffset=+2]
|
|
include::modules/nw-networkpolicy-multitenant-isolation.adoc[leveloffset=+2]
|
|
|
|
ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
|
|
[id="post-install-nw-networkpolicy-creating-default-networkpolicy-objects-for-a-new-project"]
|
|
=== Creating default network policies for a new project
|
|
|
|
As a cluster administrator, you can modify the new project template to
|
|
automatically include NetworkPolicy objects when you create a new project.
|
|
|
|
include::modules/modifying-template-for-new-projects.adoc[leveloffset=+2]
|
|
|
|
include::modules/nw-networkpolicy-project-defaults.adoc[leveloffset=+3]
|
|
endif::[]
|
|
|
|
include::modules/private-clusters-setting-dns-private.adoc[leveloffset=+1]
|
|
|
|
include::modules/nw-proxy-configure-object.adoc[leveloffset=+1]
|
|
|
|
include::modules/nw-operator-cr.adoc[leveloffset=+1]
|
|
|
|
[id="post-install-configuring_ingress_cluster_traffic"]
|
|
== Configuring ingress cluster traffic
|
|
|
|
// This section is sourced from networking/configuring_ingress_cluster_traffic/overview-traffic.adoc
|
|
|
|
{product-title} provides the following methods for communicating from
|
|
outside the cluster with services running in the cluster:
|
|
|
|
* If you have HTTP/HTTPS, use an Ingress Controller.
|
|
* If you have a TLS-encrypted protocol other than HTTPS, such as TLS with the SNI
|
|
header, use an Ingress Controller.
|
|
* Otherwise, use a Load Balancer, an External IP, or a `NodePort`.
|
|
|
|
[options="header"]
|
|
|===
|
|
|
|
|Method |Purpose
|
|
|
|
|xref:../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc#configuring-ingress-cluster-traffic-ingress-controller[Use an Ingress Controller]
|
|
|Allows access to HTTP/HTTPS traffic and TLS-encrypted protocols other than HTTPS such as, TLS with the SNI header.
|
|
|
|
|xref:../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc#configuring-ingress-cluster-traffic-load-balancer[Automatically assign an external IP by using a load balancer service]
|
|
|Allows traffic to non-standard ports through an IP address assigned from a pool.
|
|
|
|
|xref:../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-service-external-ip.adoc#configuring-ingress-cluster-traffic-service-external-ip[Manually assign an external IP to a service]
|
|
|Allows traffic to non-standard ports through a specific IP address.
|
|
|
|
|xref:../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#configuring-ingress-cluster-traffic-nodeport[Configure a `NodePort`]
|
|
|Expose a service on all nodes in the cluster.
|
|
|===
|
|
|
|
include::modules/ossm-supported-configurations.adoc[leveloffset=+1]
|
|
|
|
include::modules/ossm-installation-activities.adoc[leveloffset=+2]
|
|
|
|
.Next steps
|
|
|
|
* xref:../service_mesh/v2x/installing-ossm.adoc#installing-ossm[Install {ProductName}] in your {product-title} environment.
|
|
|
|
[id="post-installationrouting-optimization"]
|
|
== Optimizing routing
|
|
|
|
The {product-title} HAProxy router scales to optimize performance.
|
|
|
|
include::modules/baseline-router-performance.adoc[leveloffset=+2]
|
|
|
|
include::modules/router-performance-optimizations.adoc[leveloffset=+2]
|
|
|
|
[id="post-installation-osp-fips"]
|
|
== Post-installation {rh-openstack} network configuration
|
|
|
|
You can configure some aspects of a {product-title} on {rh-openstack-first} cluster after installation.
|
|
|
|
include::modules/installation-osp-configuring-api-floating-ip.adoc[leveloffset=+1]
|