ホーム
製品
Red Hat build of MicroShift
4.16
Networking
1.2. MicroShift networking configuration matrix

1.2. MicroShift networking configuration matrix

The following table summarizes the status of networking features and capabilities that are either present as defaults, supported for configuration, or not available with the MicroShift service:

Expand

表1.1 MicroShift networking features and capabilities overview
Network capability	Availability	Configuration supported
Advertise address	Yes	Yes
Kubernetes network policy	Yes	Yes
Kubernetes network policy logs	Not available	N/A
Load balancing	Yes	Yes
Multicast DNS	Yes	Yes
Network proxies	Yes	CRI-O
Network performance	Yes	MTU configuration
Egress IPs	Not available	N/A
Egress firewall	Not available	N/A
Egress router	Not available	N/A
Firewall	No	Yes
Hardware offloading	Not available	N/A
Hybrid networking	Not available	N/A
IPsec encryption for intra-cluster communication	Not available	N/A
IPv6	Not available	N/A
Ingress router	Yes	Yes
Multiple networks plugin	Yes	Yes

Additional details about networking capabilities

Advertise address: If unset, the default value is set to the next immediate subnet after the service network. For example, when the service network is 10.43.0.0/16, the advertiseAddress is set to 10.44.0.0/32.
Multicast DNS: You can use the multicast DNS protocol (mDNS) to allow name resolution and service discovery within a Local Area Network (LAN) using multicast exposed on the 5353/UDP port.
Network proxies: There is no built-in transparent proxying of egress traffic in MicroShift. Egress must be manually configured.
Firewall: Setting up the firewalld service is supported by RHEL for Edge.
Ingress router: Configure by using the MicroShift config.yaml file.

1.2.1. Default settings
リンクのコピー

If you do not create a config.yaml file, default values are used. The following example shows the default configuration settings.

To see the default values, run the following command:
```
$ microshift show-config
```
Default values example output in YAML form
```
apiServer:
  advertiseAddress: 10.44.0.0/32 
```
1
```
  auditLog:
    maxFileAge: 0 
```
2
```
    maxFileSize: 200 
```
3
```
    maxFiles: 10 
```
4
```
    profile: Default 
```
5
```
  namedCertificates:
    - certPath: ""
      keyPath: ""
      names:
        - ""
  subjectAltNames: [] 
```
6
```
debugging:
  logLevel: "Normal" 
```
7
```
dns:
  baseDomain: microshift.example.com 
```
8
```
etcd:
  memoryLimitMB: 0 
```
9
```
ingress:
  listenAddress:
    - "" 
```
10
```
  ports: 
```
11
```
    http: 80
    https: 443
  routeAdmissionPolicy:
    namespaceOwnership: InterNamespaceAllowed 
```
12
```
  status: Managed 
```
13
```
manifests: 
```
14
```
  kustomizePaths:
    - /usr/lib/microshift/manifests
    - /usr/lib/microshift/manifests.d/*
    - /etc/microshift/manifests
    - /etc/microshift/manifests.d/*
network:
  clusterNetwork:
    - 10.42.0.0/16 
```
15
```
  serviceNetwork:
    - 10.43.0.0/16 
```
16
```
  serviceNodePortRange: 30000-32767 
```
17
```
node:
  hostnameOverride: "" 
```
18
```
  nodeIP: "" 
```
19
1
A string that specifies the IP address from which the API server is advertised to members of the cluster. The default value is calculated based on the address of the service network.
2
How long log files are kept before automatic deletion. The default value of 0 in the maxFileAge parameter means a log file is never deleted based on age. This value can be configured.
3
By default, when the audit.log file reaches the maxFileSize limit, the audit.log file is rotated and MicroShift begins writing to a new audit.log file. This value can be configured.
4
The total number of log files kept. By default, MicroShift retains 10 log files. The oldest is deleted when an excess file is created. This value can be configured.
5
Logs only metadata for read and write requests; does not log request bodies except for OAuth access token requests. If you do not specify this field, the Default profile is used.
6
Subject Alternative Names for API server certificates.
7
Log verbosity. Valid values for this field are Normal, Debug, Trace, or TraceAll.
8
By default, etcd uses as much memory as needed to handle the load on the system. However, in memory constrained systems, it might be preferred or necessary to limit the amount of memory etcd can to use at a given time.
9
Base domain of the cluster. All managed DNS records are subdomains of this base.
10
The ingress.listenAddress value defaults to the entire network of the host. The valid configurable value is a list that can be either a single IP address or NIC name or multiple IP addresses and NIC names.
11
Default ports shown. Configurable. Valid values for both port entries are a single, unique port in the 1-65535 range. The values of the ports.http and ports.https fields cannot be the same.
12
Describes how hostname claims across namespaces are handled. By default, allows routes to claim different paths of the same hostname across namespaces. Valid values are Strict and InterNamespaceAllowed. Specifying Strict prevents routes in different namespaces from claiming the same hostname. If the value is deleted in a customized MicroShift config.yaml, the InterNamespaceAllowed value is automatically set.
13
Default router status, can be Managed or Removed.
14
The locations on the file system to scan for kustomization files to use to load manifests. Set to a list of paths to scan only those paths. Set to an empty list to disable loading manifests. The entries in the list can be glob patterns to match multiple subdirectories.
15
A block of IP addresses from which pod IP addresses are allocated. This field is immutable after installation.
16
A block of virtual IP addresses for Kubernetes services. IP address pool for services. A single entry is supported. This field is immutable after installation.
17
The port range allowed for Kubernetes services of type NodePort. If not specified, the default range of 30000-32767 is used. Services without a NodePort specified are automatically allocated one from this range. This parameter can be updated after the cluster is installed.
18
The name of the node. The default value is the hostname. If non-empty, this string is used to identify the node instead of the hostname. You cannot change this immutable setting after MicroShift starts for the first time.
19
The IP address of the node. The default value is the IP address of the default route.

1.2. MicroShift networking configuration matrix

1.2.1. Default settings
リンクのコピー

詳細情報

試用、購入および販売

コミュニティー

会社概要

多様性を受け入れるオープンソースの強化

Red Hat ドキュメントについて

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

1.2. MicroShift networking configuration matrix

1.2.1. Default settingsリンクのコピーリンクがクリップボードにコピーされました!

詳細情報

試用、購入および販売

コミュニティー

会社概要

多様性を受け入れるオープンソースの強化

Red Hat ドキュメントについて

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

1.2.1. Default settings
リンクのコピー