We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It is my belief that the helm chart default values and the way that those values are converted into manifests are far too opinionated.
See my solution below to "overwrite" the opinionated config to end up in a place that worked.
I would love to see the ingress and service manifest templates in the chart updated to support a wider range of options.
service: internalType: ClusterIP externalType: LoadBalancer ports: - name: api port: 9000 protocol: TCP external: false - name: leadercomm port: 4200 protocol: TCP external: true extraObjects: - apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: cribl-leader spec: ingressClassName: nginx rules: - host: cribl-leader.local.domain http: paths: - path: / pathType: Prefix backend: service: name: cribl-leader-internal port: number: 9000
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It is my belief that the helm chart default values and the way that those values are converted into manifests are far too opinionated.
See my solution below to "overwrite" the opinionated config to end up in a place that worked.
I would love to see the ingress and service manifest templates in the chart updated to support a wider range of options.
The text was updated successfully, but these errors were encountered: