You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/k8s-best-practices-container-runtime.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ OpenShift uses CRI-O as a CRI interface for Kubernetes. CRI-O manages `runC` for
8
8
====
9
9
Images should be OCI compliant. Red Hat recommends that you build images using Red Hat's open Universal Base Image (UBI).
10
10
11
-
See <<cnf-best-practices-ubi>> for additional information about UBI and support.
11
+
See <<k8s-best-practices-ubi>> for additional information about UBI and support.
12
12
13
13
See test case link:https://github.com/test-network-function/cnf-certification-test/blob/main/CATALOG.md#platform-alteration-isredhat-release[platform-alteration-isredhat-release]
Copy file name to clipboardExpand all lines: modules/k8s-best-practices-csi.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
4
4
Pod volumes are supported via local storage and the CSI for persistent volumes. Local storage is truly ephemeral storage, it is local only to the physical node that a pod is running on and is lost when a pod is killed and recreated. If a pod requires persistent storage, the CSI can be used via Kubernetes native primitives `persistentVolume` (`PV`) and `persistentVolumeClaim` (`PVC`) to get persistent storage, such as an NFS share via the CSI backed by NetApp Trident.
5
5
6
-
When using storage with Kubernetes, you can use storage classes. Refer to <<cnf-best-practices-block-storage>> for a description of the available storage classes. Using storage classes, you can create volumes based on the parameters of the required storage.
6
+
When using storage with Kubernetes, you can use storage classes. Refer to <<k8s-best-practices-block-storage>> for a description of the available storage classes. Using storage classes, you can create volumes based on the parameters of the required storage.
7
7
8
8
Workloads should clear persistent storage by deleting the associated `PV` resources when removing the application from a cluster.
Copy file name to clipboardExpand all lines: modules/k8s-best-practices-developer-guide.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,17 +3,17 @@
3
3
4
4
This section discusses recommendations and requirements for workload application builders.
5
5
6
-
[id="cnf-best-practices-preface"]
6
+
[id="k8s-best-practices-preface"]
7
7
== Preface
8
8
9
9
Cloud-native workload applications are containerized instances of classic physical or virtual applications which have been decomposed into microservices supporting elasticity, lifecycle management, security, logging, and other capabilities in a Cloud-Native format.
10
10
11
-
[id="cnf-best-practices-goal"]
11
+
[id="k8s-best-practices-goal"]
12
12
== Goal
13
13
14
14
This document is mainly for the developers of workloads, who need to build high-performance applications in a containerized environment. We have created a guide that any partner can take and follow when developing their workloads so that they can be deployed on the OpenShift Container Platform (OCP) in a secure, efficient and supportable way.
15
15
16
-
[id="cnf-best-practices-non-goal"]
16
+
[id="k8s-best-practices-non-goal"]
17
17
== Non-goal
18
18
19
19
This is not a guide on how to build workload functionality.
Copy file name to clipboardExpand all lines: modules/k8s-best-practices-numa-awareness.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,5 +3,5 @@
3
3
4
4
If the pod is using a guaranteed QoS class and the kubelet is configured with a suitable topology manager policy (restricted, single-numa node) then the VF assigned to the pod will belong to the same NUMA node as the other assigned resources (CPU and other NUMA aware devices). Please note that HugePages are currently not NUMA aware.
5
5
6
-
See <<cnf-best-practices-performance-addon-operator-pao>> for NUMA awareness and more information about how HugePages are turned on.
6
+
See <<k8s-best-practices-performance-addon-operator-pao>> for NUMA awareness and more information about how HugePages are turned on.
* For all the networks, the IP/MAC address should be assigned to the interface during pod creation.
24
24
25
25
* MULTUS also allows users to override the IP/MAC address. Refer to link:https://docs.openshift.com/container-platform/latest/networking/multiple_networks/attaching-pod.html[Attaching a pod to an additional network] for more information.
* By default, the default route of the pod will point to the cluster network, with or without the additional networks. MULTUS also allows users to override the default route of the pod. Refer to link:https://docs.openshift.com/container-platform/latest/networking/multiple_networks/attaching-pod.html[Attaching a pod to an additional network] for more information.
@@ -44,7 +44,7 @@ The SR-IOV Network Operator also supports configuring the following parameters f
44
44
* `spoofChk`
45
45
* `trust`
46
46
47
-
[id="cnf-best-practices-multicast"]
47
+
[id="k8s-best-practices-multicast"]
48
48
== Configuring multicast
49
49
50
50
In OpenShift, multicast is supported for both the default interface (OVN or OpenShift-SDN) and the additional interfaces such as macvlan, SR-IOV, etc. Multicast is disabled by default. To enable it, refer to the following procedures:
Workloads should use the service name only as a configuration parameter for attaching to a service within your namespace, the cluster will append namespace name and kubernetes service nomenclature on behalf of the application via search string in DNS. This allows a generic name for a service that works in all clusters no matter what the namespace name is and what the cluster base FQDN is.
0 commit comments