Skip to content

Commit 809fb42

Browse files
ShaunaDiazShaunaDiaz
committed
OSDOCS-4566 MicroShift adding networking assembly and firewall module to config
1 parent 35067ce commit 809fb42

20 files changed

+680
-23
lines changed

‎_topic_maps/_topic_map_ms.yml

Lines changed: 21 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -51,9 +51,9 @@ Name: Installing
5151
Dir: microshift_install
5252
Distros: microshift
5353
Topics:
54-
- Name: Installing MicroShift from RPM
54+
- Name: Installing from RPM
5555
File: microshift-install-rpm
56-
- Name: Installing MicroShift in a RHEL for Edge Image
56+
- Name: Installing in a RHEL for Edge Image
5757
File: microshift-install-rhel-for-edge
5858
---
5959
Name: API reference
@@ -104,25 +104,17 @@ Name: Configuring
104104
Dir: microshift_configuring
105105
Distros: microshift
106106
Topics:
107-
- Name: Configuring MicroShift
107+
- Name: Configuring
108108
File: microshift-using-config-tools
109-
# ---
110-
# Name: Storage
111-
# Dir: storage
112-
# Distros: microshift
113-
# Topics:
114-
# - Name: Persistent storage
115-
# Dir: persistent_storage
116-
# Topics:
117-
# - Name: Persistent storage using ODF-LVM
118-
# File: microshift-persistent-storage-odf-lvm
119-
# ---
120-
# Name: Networking
121-
# Dir: networking
122-
# Distros: microshift
123-
# Topics:
109+
---
110+
Name: Networking
111+
Dir: microshift_networking
112+
Distros: microshift
113+
Topics:
114+
- Name: Understanding networking
115+
File: microshift-networking
124116
# - Name: Understanding the Ingress Operator
125-
# File: ingress-operator
117+
# File: ingress-operator-microshift
126118
# - Name: Configuring a cluster-wide proxy during installation
127119
# File: configuring-cluster-wide-proxy
128120
# - Name: CIDR range definitions
@@ -141,6 +133,16 @@ Topics:
141133
# - Name: Configuring multitenant isolation with network policy
142134
# File: multitenant-network-policy
143135
# ---
136+
# Name: Storage
137+
# Dir: storage
138+
# Distros: microshift
139+
# Topics:
140+
# - Name: Persistent storage
141+
# Dir: persistent_storage
142+
# Topics:
143+
# - Name: Persistent storage using ODF-LVM
144+
# File: microshift-persistent-storage-odf-lvm
145+
# ---
144146
# Name: Updating clusters
145147
# Dir: updating
146148
# Distros: microshift

‎microshift_configuring/microshift-using-config-tools.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
:_content-type: ASSEMBLY
22
[id="microshift-using-config-tools"]
3-
= Configuring {product-title}
3+
= Configuring
44
include::_attributes/attributes-microshift.adoc[]
55
:context: microshift-configuring
66
toc::[]

‎microshift_networking/_attributes

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../_attributes

‎microshift_networking/images

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../images

‎microshift_networking/ingress-operator-microshift.adoc

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
:_content-type: ASSEMBLY
2+
[id="configuring-ingress-microshift"]
3+
= Ingress Operator in {product-title}
4+
include::_attributes/attributes-microshift.adoc[]
5+
:context: configuring-ingress
6+
7+
toc::[]
8+
include::modules/nw-ne-openshift-ingress.adoc[leveloffset=+1]
9+
include::modules/nw-installation-ingress-config-asset.adoc[leveloffset=+1]
10+
include::modules/nw-ingress-controller-configuration-parameters.adoc[leveloffset=+1]
11+
12+
[id="configuring-ingress-controller-tls"]
13+
=== Ingress Controller TLS security profiles
14+
15+
TLS security profiles provide a way for servers to regulate which ciphers a connecting client can use when connecting to the server.
16+
17+
// Understanding TLS security profiles
18+
include::modules/tls-profiles-understanding.adoc[leveloffset=+3]
19+
20+
// Configuring the TLS profile for the Ingress Controller
21+
include::modules/tls-profiles-ingress-configuring.adoc[leveloffset=+3]
22+
23+
include::modules/nw-mutual-tls-auth.adoc[leveloffset=+3]
24+
25+
include::modules/nw-ingress-view.adoc[leveloffset=+1]
26+
27+
include::modules/nw-ingress-operator-status.adoc[leveloffset=+1]
28+
29+
include::modules/nw-ingress-operator-logs.adoc[leveloffset=+1]
30+
31+
include::modules/nw-ingress-controller-status.adoc[leveloffset=+1]
32+
33+
[id="configuring-ingress-controller"]
34+
== Configuring the Ingress Controller
35+
36+
include::modules/nw-ingress-setting-a-custom-default-certificate.adoc[leveloffset=+2]
37+
38+
include::modules/nw-ingress-custom-default-certificate-remove.adoc[leveloffset=+2]
39+
40+
include::modules/nw-autoscaling-ingress-controller.adoc[leveloffset=+2]
41+
42+
include::modules/nw-scaling-ingress-controller.adoc[leveloffset=+2]
43+
44+
include::modules/nw-configure-ingress-access-logging.adoc[leveloffset=+2]
45+
46+
include::modules/nw-ingress-setting-thread-count.adoc[leveloffset=+2]
47+
48+
include::modules/nw-ingress-sharding.adoc[leveloffset=+2]
49+
50+
include::modules/nw-ingress-sharding-route-labels.adoc[leveloffset=+3]
51+
52+
include::modules/nw-ingress-sharding-namespace-labels.adoc[leveloffset=+3]
53+
54+
include::modules/nw-ingress-setting-internal-lb.adoc[leveloffset=+2]
55+
56+
include::modules/nw-ingress-controller-configuration-gcp-global-access.adoc[leveloffset=+2]
57+
58+
include::modules/nw-ingress-controller-config-tuningoptions-healthcheckinterval.adoc[leveloffset=+2]
59+
60+
include::modules/nw-ingress-default-internal.adoc[leveloffset=+2]
61+
62+
include::modules/nw-route-admission-policy.adoc[leveloffset=+2]
63+
64+
include::modules/using-wildcard-routes.adoc[leveloffset=+2]
65+
66+
include::modules/nw-using-ingress-forwarded.adoc[leveloffset=+2]
67+
68+
include::modules/nw-http2-haproxy.adoc[leveloffset=+2]
69+
70+
include::modules/nw-ingress-controller-configuration-proxy-protocol.adoc[leveloffset=+2]
71+
72+
include::modules/nw-ingress-configuring-application-domain.adoc[leveloffset=+2]
73+
74+
include::modules/nw-ingress-converting-http-header-case.adoc[leveloffset=+2]
75+
76+
include::modules/nw-configuring-router-compression.adoc[leveloffset=+2]
77+
78+
include::modules/nw-customize-ingress-error-pages.adoc[leveloffset=+2]
79+
//include::modules/nw-ingress-select-route.adoc[leveloffset=+2]
80+
81+
include::modules/nw-ingress-setting-max-connections.adoc[leveloffset=+2]
82+
83+
//[role="_additional-resources"]
84+
//== Additional resources
85+
86+
//* xref:../networking/configuring-a-custom-pki.adoc#configuring-a-custom-pki[Configuring a custom PKI]
87+

‎microshift_networking/microshift-networking.adoc

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
:_content-type: ASSEMBLY
2+
[id="microshift-understanding-networking"]
3+
= Understanding networking
4+
include::_attributes/attributes-microshift.adoc[]
5+
:context: microshift-networking
6+
7+
toc::[]
8+
9+
Learn how to apply networking customization and default settings to {product-title} deployments. Each node is contained to a single machine and single {product-title}, so each deployment requires individual configuration, pods, and settings.
10+
11+
Cluster Administrators have several options for exposing applications that run inside a cluster to external traffic and securing network connections:
12+
13+
* A service such as NodePort
14+
15+
* API resources, such as `Ingress` and `Route`
16+
17+
By default, Kubernetes allocates each pod an internal IP address for applications running within the pod. Pods and their containers can have traffic between them, but clients outside the cluster do not have direct network access to pods except when exposed with a service such as NodePort.
18+
19+
include::modules/microshift-cni.adoc[leveloffset=+1]
20+
include::modules/microshift-configuring-ovn.adoc[leveloffset=+1]
21+
//include::modules/microshift-man-config-ovs-bridge.adoc[leveloffset=+1]
22+
include::modules/microshift-http-proxy.adoc[leveloffset=+1]
23+
include::modules/microshift-cri-o-container-runtime.adoc[leveloffset=+1]
24+
include::modules/microshift-ovs-snapshot.adoc[leveloffset=+1]
25+
include::modules/microshift-firewall-config.adoc[leveloffset=+1]

‎microshift_networking/modules

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../modules

‎microshift_networking/snippets

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../snippets/

‎microshift_troubleshooting/microshift-known-issues.adoc

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,11 @@
11
:_content-type: ASSEMBLY
22
[id="microshift-known-issues"]
3-
= Troubleshoot known issues
3+
= Troubleshooting and known issues
44
include::_attributes/attributes-microshift.adoc[]
55
:context: microshift-known-issues
66
toc::[]
77

8-
Read about known issues and possible solutions.
8+
Read about troubleshooting, known issues, and possible solutions.
99

1010
include::modules/microshift-ki-cni-iptables-deleted.adoc[leveloffset=+1]
11+
include::modules/microshift-troubleshooting-nodeport.adoc[leveloffset=+1]

‎microshift_troubleshooting/microshift-version.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@
33
= Checking which version you have installed
44
include::_attributes/attributes-microshift.adoc[]
55
:context: microshift-version
6+
67
toc::[]
78

89
To begin troubleshooting, determine which version of {product-title} you have installed.

0 commit comments

Comments
 (0)