| @@ -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 / Fix MetalLB
Last active 2 months ago
At first the MetalLB is working well, but in a meanwhile strange issue coming and fixed by this script
supanadit revised this gist 1 year ago · 1947646
No changes
supanadit revised this gist 1 year ago · 34fbcdb
1 file changed, 1 insertion
supanadit revised this gist 1 year ago · 633f422
1 file changed, 2 insertions
| @@ -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 | |