Skip to content

Commit 0c35fbb

Browse files
authored
Update k8s-best-practices-spk-integration-via-spk-operator.adoc
1 parent 75235f3 commit 0c35fbb

File tree

1 file changed

+2
-7
lines changed

1 file changed

+2
-7
lines changed

modules/k8s-best-practices-spk-integration-via-spk-operator.adoc

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
[id="k8s-best-practices-spk-integration-via-spk-operator"]
22
[id="spk-integration-via-spk-operator"]
33
= SPK Integration via SPK Operator
4-
The SPK runs in a separate namespace from the CNF. The CNF will not have direct permissions to access this namespace. In order to allow applications to manage the lifecycle of the SPK deployment, the SPK operator is used. The SPK Operator defines several CRDs for which CRs are created in the CNF namespace:
4+
5+
The SPK runs in a separate namespace from the workload. The workload will not have direct permissions to access this namespace. In order to allow applications to manage the lifecycle of the SPK deployment, the SPK operator is used. The SPK Operator defines several CRDs for which CRs are created in the CNF namespace:
56

67
[id="cnf-best-practices-spkprofile"]
78
== SPKProfile
@@ -70,9 +71,3 @@ spec:
7071
----
7172

7273
More details on the SPK operator are in the "SPK Operator User Guide".
73-
74-
.VCP CNF requirement - Doors Id 94142
75-
[IMPORTANT]
76-
====
77-
The application MUST integrate with the SPK Operator to perform lifecycle management of the SPK.
78-
====

0 commit comments

Comments
 (0)