MetalLB doesn't assign IP address to Keycloak service

pysquirrel

10/31/23, 10:08 AM

I have installed both MetalLB and Keylcloak to my cluster. Both Keycloak's and MetalLB's pods are running, but the main Keycloak Load balance service is expecting IP (EXTERNAL-IP is in pending state).

Here is my MetalLB config map:

apiVersion: v1
data:
  config: |
    address-pools:
    - addresses:
      - server-ip/32
      name: default
      protocol: layer2
kind: ConfigMap
metadata:
  annotations:
    meta.helm.sh/release-name: metallb
    meta.helm.sh/release-namespace: default
  creationTimestamp: "2022-10-24T07:43:45Z"
  labels:
    app.kubernetes.io/instance: metallb
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: metallb
    helm.sh/chart: metallb-3.0.12
  name: metallb-config
  namespace: default
  resourceVersion: "***"
  uid: ***

According to the MetalLB documentation, all I have to do is to deploy a service with type LoadBalancer. So I did, but it's not assigning IP to it. Any tips?

Thank you

0 + 0

kubernetes

helm

keycloak

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: MetalLB doesn't assign IP address to Keycloak service

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.