Hi, is someone know how to make static ip on datah...
# troubleshoot
a
Hi, is someone know how to make static ip on datahub frontend through ingress when deploy using helm chart? Currently my yaml on datahub frontend look like this
Copy code
# Set up ingress to expose react front-end
  ingress:
    enabled: true
    podAnnotations:
      kubernetes.io/ingress.class: "gce-internal"
      kubernetes.io/ingress.regional-static-ip-name: "your-domain-name-internal-address"
    hosts:
    - host: your-domain-name
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: datahub-frontend
                port:
                  name: http
      #path: /
      #redirectPaths: []

  service:
    type: NodePort # ClusterIP or NodePort
    port: 9002
    targetPort: http
    protocol: TCP
    name: http
    annotations:
      cloud.google.com/neg: '{"ingress": true}'
    # annotations:
    #   networking.gke.io/load-balancer-type: Internal
Since in service section we can’t using
arg loadBalancerIP
, is there anyway to make datahub front end from dynamic IP to static IP when we deploy using helm chart? Also when I tried to do helm upgrade it always got an error look like this
Error: UPGRADE FAILED: error validating "": error validating data: ValidationError(Ingress.spec.rules[0].http): missing required field "paths" in io.k8s.api.networking.v1.HTTPIngressRuleValue
Anyone know the problems and how to fix it? Notes: • Image datahub v0.10.0
🔍 1
📖 1
✅ 1
l
Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? Did you find a solution to your issue? ❌ Sorry you weren't able to find a solution. I'm sending you some tips on info you can provide to help the community troubleshoot. Whenever you feel your issue is solved, please react ✅ to your original message to let us know!
a
@astonishing-dusk-99990 @dazzling-yak-93039 may be able to help you here!
p
I'm in the same situation!
a
Looks like we didn’t get to this last week- @brainy-tent-14503 could you take a look
b
It looks like you are confusing
pod
annotations with the annotations on the
ingress
. The helm chart has options to add ingress annotations here and assuming you are running on Google Cloud then the annotations look like they match the docs. Note however I don’t believe that the value is a domain name in that sense. I believe it refers to a label or unique identifier for the IP+hostname combination, perhaps setup like this. In any case, you can use the helm chart to set arbitrary annotations on the ingress being created, just make sure to use the
annotations
key and not
podAnnotations
a
Thank you for the explanation @brainy-tent-14503 Actually I’m still new with this kubernetes setup and already ask my colleagues but all of them still learn about ingress. So as for plan B, we use another method before you replied this thread, I was modified chart in here by adding these lines under
spec
section:
Copy code
{{- if .Values.service.loadBalancerIP }}
  loadBalancerIP: {{ .Values.service.loadBalancerIP }}
{{- end }}
So far it works and the IP datahub frontend always static if we want to redeploy it. Perhaps later we will try ingress method.