Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
control-service: ingress allow for multiple hosts (#2911)
Why: Our Helm chart currently lacks the functionality to specify multiple Ingress hosts. What: Enhance the Ingress template to support multiple hosts. Testing done: helm template before: ```yaml kind: Ingress metadata: name: release-name-pipelines-control-service labels: app.kubernetes.io/name: pipelines-control-service helm.sh/chart: pipelines-control-service-0.0.1-SNAPSHOT app.kubernetes.io/instance: release-name app.kubernetes.io/managed-by: Helm annotations: {} apiVersion: networking.k8s.io/v1 spec: ingressClassName: class rules: - host: "vdk.com" http: paths: - path: data-jobs pathType: "ImplementationSpecific" backend: service: name: release-name-ui port: number: 8091 - path: data-jobs pathType: "ImplementationSpecific" backend: service: name: release-name-svc port: number: 8092 tls: - hosts: - "vdk.com" secretName: secret ``` after: ```yaml kind: Ingress metadata: name: release-name-pipelines-control-service labels: app.kubernetes.io/name: pipelines-control-service helm.sh/chart: pipelines-control-service-0.0.1-SNAPSHOT app.kubernetes.io/instance: release-name app.kubernetes.io/managed-by: Helm annotations: {} apiVersion: networking.k8s.io/v1 spec: ingressClassName: class rules: - host: vdk.com http: paths: - path: "/data-jobs" backend: service: name: release-name-svc port: number: 8092 - path: "/" backend: service: name: release-name-ui port: number: 8091 tls: - hosts: - vdk.com secretName: secret ``` Signed-off-by: Miroslav Ivanov [email protected] Signed-off-by: Miroslav Ivanov [email protected]
- Loading branch information