Difference between revisions of "StarlingX/Containers/Applications/app-ipsec-policy-operator"
< StarlingX | Containers | Applications
m (→Building) |
|||
| Line 5: | Line 5: | ||
== Building == | == Building == | ||
* Get the .tgz file located at | * Get the .tgz file located at | ||
| − | + | /usr/local/share/applications/helm/ | |
* From the Debian Build environment: | * From the Debian Build environment: | ||
| − | + | build-pkgs [-c] -p ipsec-policy-manager-helm,ipsec-policy-agent-helm,python3-k8sapp-ipsec-policy-operator,stx-ipsec-policy-operator | |
== Testing == | == Testing == | ||
Installation and testing steps are mentioned [https://docs.starlingx.io/security/kubernetes/configure-ipsec-for-selected-inter-host-pod-to-pod-traffic-usi-8cb9b4342b5d.html#configure-ipsec-for-selected-inter-host-pod-to-pod-traffic-usi-8cb9b4342b5d here]. After installation please verify if there is a single pod running for ipsec-policy-manager-controller-manager and one pod running on each controller/compute node for ipsec-policy-agent-controller-manager. | Installation and testing steps are mentioned [https://docs.starlingx.io/security/kubernetes/configure-ipsec-for-selected-inter-host-pod-to-pod-traffic-usi-8cb9b4342b5d.html#configure-ipsec-for-selected-inter-host-pod-to-pod-traffic-usi-8cb9b4342b5d here]. After installation please verify if there is a single pod running for ipsec-policy-manager-controller-manager and one pod running on each controller/compute node for ipsec-policy-agent-controller-manager. | ||
| + | |||
| + | kubectl get pods -n ipsec-policy-operator | ||
| + | |||
| + | NAME READY STATUS RESTARTS AGE | ||
| + | ipsec-policy-agent-controller-manager-qmnuh 2/2 Running 0 1m51s | ||
| + | ipsec-policy-agent-controller-manager-xz3a4 2/2 Running 0 1m51s | ||
| + | ipsec-policy-manager-controller-manager-814d94dcea-s4sxb 2/2 Running 0 3m37s | ||
| + | |||
| + | kubectl get daemonsets -n ipsec-policy-operator | ||
| + | |||
| + | NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE | ||
| + | ipsec-policy-agent-controller-manager 2 2 2 2 2 ipsec-policy-agent-operator=enabled 2m47s | ||
| + | |||
| + | kubectl get deployment -n ipsec-policy-operator | ||
| + | |||
| + | NAME READY UP-TO-DATE AVAILABLE AGE | ||
| + | ipsec-policy-manager-controller-manager 1/1 1 1 3m42s | ||
Revision as of 18:56, 14 January 2026
Application: app-ipsec-policy-operator
Source
Building
- Get the .tgz file located at
/usr/local/share/applications/helm/
- From the Debian Build environment:
build-pkgs [-c] -p ipsec-policy-manager-helm,ipsec-policy-agent-helm,python3-k8sapp-ipsec-policy-operator,stx-ipsec-policy-operator
Testing
Installation and testing steps are mentioned here. After installation please verify if there is a single pod running for ipsec-policy-manager-controller-manager and one pod running on each controller/compute node for ipsec-policy-agent-controller-manager.
kubectl get pods -n ipsec-policy-operator
NAME READY STATUS RESTARTS AGE ipsec-policy-agent-controller-manager-qmnuh 2/2 Running 0 1m51s ipsec-policy-agent-controller-manager-xz3a4 2/2 Running 0 1m51s ipsec-policy-manager-controller-manager-814d94dcea-s4sxb 2/2 Running 0 3m37s
kubectl get daemonsets -n ipsec-policy-operator NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE ipsec-policy-agent-controller-manager 2 2 2 2 2 ipsec-policy-agent-operator=enabled 2m47s
kubectl get deployment -n ipsec-policy-operator NAME READY UP-TO-DATE AVAILABLE AGE ipsec-policy-manager-controller-manager 1/1 1 1 3m42s
