[bitnami/metallb] fix failed-to-call-webhook issue

[mmianl]

Description of the change

Benefits

Possible drawbacks

Applicable issues

• fixes [bitnami/metallb] failed to call webhook 503 Service Unavailable #15094

Additional information

Related to #15097

Checklist

• Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
• Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
• Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
• All commits signed off and in agreement of Developer Certificate of Origin (DCO)

[Mauraza]

Hi @mmianl,

Thanks for the contribution! Could you share the values are you using when you get the error with webhook?

[mmianl]

Sure, here they are:

---
rbac:
  create: true
psp:
  create: false
networkPolicy:
  enabled: true
prometheusRule:
  enabled: false

controller:
  image:
    registry: quay.io
    repository: metallb/controller
    tag: "v0.13.9"
    pullPolicy: IfNotPresent
  updateStrategy:
   type: RollingUpdate
   rollingUpdate:
     maxSurge: 1
     maxUnavailable: 0
  rbac:
    create: true
  psp:
    create: false
  resources:
    requests:
      cpu: 100m
      memory: 128Mi
    limits:
      cpu: 100m
      memory: 256Mi
  serviceAccount:
    create: true
    automountServiceAccountToken: true
  containerPorts:
    metrics: 7472
  livenessProbe:
    enabled: true
    failureThreshold: 3
    initialDelaySeconds: 10
    periodSeconds: 10
    successThreshold: 1
    timeoutSeconds: 1
  readinessProbe:
    enabled: true
    failureThreshold: 3
    initialDelaySeconds: 10
    periodSeconds: 10
    successThreshold: 1
    timeoutSeconds: 1
  startupProbe:
    enabled: true
    failureThreshold: 3
    initialDelaySeconds: 10
    periodSeconds: 10
    successThreshold: 1
    timeoutSeconds: 1
  metrics:
    enabled: true
    service:
      port: 7472
      annotations:
        prometheus.io/scrape: "true"
        prometheus.io/port: "7472"
        prometheus.io/path: "/metrics"
    serviceMonitor:
      enabled: true
      namespace: "metallb-system"
      jobLabel: "app.kubernetes.io/name"
      interval: "30s"
      scrapeTimeout: "15s"

speaker:
  image:
    registry: quay.io
    repository: metallb/speaker
    tag: "v0.13.9"
    pullPolicy: IfNotPresent
  updateStrategy:
    type: RollingUpdate
  rbac:
    create: true
  psp:
    create: false
  resources:
    requests:
      cpu: 250m
      memory: 128Mi
    limits:
      cpu: 250m
      memory: 256Mi
  serviceAccount:
    create: true
    automountServiceAccountToken: true
  containerPorts:
    metrics: 7472
  livenessProbe:
    enabled: true
    failureThreshold: 3
    initialDelaySeconds: 10
    periodSeconds: 10
    successThreshold: 1
    timeoutSeconds: 1
  readinessProbe:
    enabled: true
    failureThreshold: 3
    initialDelaySeconds: 10
    periodSeconds: 10
    successThreshold: 1
    timeoutSeconds: 1
  startupProbe:
    enabled: true
    failureThreshold: 3
    initialDelaySeconds: 10
    periodSeconds: 10
    successThreshold: 1
    timeoutSeconds: 1
  metrics:
    enabled: true
    service:
      port: 7472
      annotations:
        prometheus.io/scrape: "true"
        prometheus.io/port: "7472"
        prometheus.io/path: "/metrics"
    serviceMonitor:
      enabled: true
      namespace: "metallb-system"
      jobLabel: "app.kubernetes.io/name"
      interval: "30s"
      scrapeTimeout: "15s"

[Mauraza]

Hi @mmianl,

I'm trying to reproduce the issue but I can't. In the values, I check that you are not using bitnami images. Did you get the same error with bitnami/metallb?

[mmianl]

Hi @Mauraza
I can't test with the bitnami images because they are not available for my platform.

[mmianl]

@Mauraza
Actually, forget what I just said. The same error does indeed also occur in a RKE2 environment using bitnami/metallb-controller and bitnami/metallb-speaker with tag 0.13.7-debian-11-r27.

Does your test environment support Kubernetes Network Policies?

[Mauraza]

Hi @mmianl,

I think it looks good, cloud you resolve the conflicts?

[mmianl]

Hey @Mauraza ,
Thanks for the feedback, I just resolved the conflicts...

[Mauraza]

Hi @mmianl,

Thanks again for the contribution! LGTM!