astonishing-dusk-99990
04/10/2023, 9:13 AM# 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.0lively-cat-88289
04/10/2023, 9:13 AMastonishing-answer-96712
04/12/2023, 6:47 PMpowerful-finland-16210
04/18/2023, 5:56 AMastonishing-answer-96712
04/18/2023, 4:27 PMbrainy-tent-14503
04/22/2023, 1:26 AMpod 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 podAnnotationsastonishing-dusk-99990
05/02/2023, 3:46 AMspec section:
{{- 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.