Red Hat offers cluster administrators the Network Observability Operator to observe the network traffic for OpenShift Container Platform clusters. The Network Observability uses the eBPF technology to create network flows. The network flows are then enriched with OpenShift Container Platform information and stored in Loki. You can view and analyze the stored network flows information in the OpenShift Container Platform console for further insight and troubleshooting.
Network Observability Operator in OpenShift Container Platform
Default haproxy config Inter 1s (The “inter” parameter sets the interval between two consecutive health checks to milliseconds.)
Fall 2 (The “fall” parameter states that a server will be considered as dead after consecutive unsuccessful health checks.)
Rise 3 (The “rise” parameter states that a server will be considered as operational after consecutive successful health checks.)
HttpCheck GET /readyz HTTP/1.0
global stats socket /var/lib/haproxy/run/haproxy.sock mode 600 level admin expose-fd listeners defaults maxconn 20000 mode tcp log /var/run/haproxy/haproxy-log.
Default versions Kernel versions 4.18 and above default to nfs 4.2. The client will try in order 4.2 then 4.1 then 4.0.
https://access.redhat.com/articles/6907891
https://access.redhat.com/articles/3626571
Default mount options rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,local_lock=none,addr=<nfs_server>
Customize mount options https://access.redhat.com/solutions/6065961
apiVersion: v1 kind: PersistentVolume spec: [...] mountOptions: - nfsvers=4.1 [...]You can make a RPC call to the NFS server to get supported versions :
$ rpcinfo -p 192.168.0.10 | grep nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfsAnd adapt mount options according to your nfs server.
