Difference between revisions of "StarlingX/Containers/Applications/app-ipsec-policy-operator"
< StarlingX | Containers | Applications
m |
m |
||
| Line 6: | Line 6: | ||
* Get the .tgz file located at | * Get the .tgz file located at | ||
/usr/local/share/applications/helm/ | /usr/local/share/applications/helm/ | ||
| − | * | + | * Or build it 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 | build-pkgs [-c] -p ipsec-policy-manager-helm,ipsec-policy-agent-helm,python3-k8sapp-ipsec-policy-operator,stx-ipsec-policy-operator | ||
Latest revision as of 19:09, 14 January 2026
Application: app-ipsec-policy-operator
Source
Building
- Get the .tgz file located at
/usr/local/share/applications/helm/
- Or build it 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
