Последняя активность 1759997447

At first the MetalLB is working well, but in a meanwhile strange issue coming and fixed by this script

supanadit ревизий этого фрагмента 1759997447. К ревизии

Без изменений

supanadit ревизий этого фрагмента 1759997339. К ревизии

1 file changed, 1 insertion

metallb.sh

@@ -1,2 +1,3 @@
1 + # This is how we fix loadbalancer IP that couldn't be accessed in MetalLB
1 2 kubectl patch ds speaker -n metallb-system --context default --type='json' -p='[{"op":"add","path":"/spec/template/spec/containers/0/securityContext","value":{"privileged":true,"capabilities":{"add":["NET_ADMIN","NET_RAW"]},"seccompProfile":{"type":"Unconfined"}}}]'
2 3 kubectl rollout restart ds/speaker -n metallb-system --context default

supanadit ревизий этого фрагмента 1759997299. К ревизии

1 file changed, 2 insertions

metallb.sh(файл создан)

@@ -0,0 +1,2 @@
1 + kubectl patch ds speaker -n metallb-system --context default --type='json' -p='[{"op":"add","path":"/spec/template/spec/containers/0/securityContext","value":{"privileged":true,"capabilities":{"add":["NET_ADMIN","NET_RAW"]},"seccompProfile":{"type":"Unconfined"}}}]'
2 + kubectl rollout restart ds/speaker -n metallb-system --context default
Новее Позже