~Is there a known bug with `values` using `kuberne...
# general
b
Is there a known bug with
values
using
kubernetes.helm.v2.Chart
?
I’m having issues with values not being applied to the templates, specifically the
targetPorts
on an Ingress Chart
Chart had the wrong values documented, my bad.
Copy code
// create ingress controller
    const ingressController = new k8s.helm.v2.Chart(
      name,
      {
        fetchOpts: {
          repo: "<https://helm.nginx.com/stable>"
        },
        chart: "nginx-ingress",
        version: "0.3.0",
        values: {
          controller: {
            service: {
              targetPorts: {
                https: "http",
                http: "http"
              },
              annotations: {
                "<http://service.beta.kubernetes.io/aws-load-balancer-ssl-cert|service.beta.kubernetes.io/aws-load-balancer-ssl-cert>": certificate.arn,
                "<http://service.beta.kubernetes.io/aws-load-balancer-backend-protocol|service.beta.kubernetes.io/aws-load-balancer-backend-protocol>": "http",
                "<http://service.beta.kubernetes.io/aws-load-balancer-ssl-ports|service.beta.kubernetes.io/aws-load-balancer-ssl-ports>": "https",
                "<http://service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout|service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout>": "3600"
              }
            }
          }
        }
      }, {});
  }
c
there are no known issues
we’re pretty dumb about this though, whatever’s in there just gets serialized and sent off to helm
if values are hidden behind something that msut be expanded on tiller, they would get elided though.
b
I don’t think I’m running Tiller on the K8S Cluster
c
I meant, the chart might expect you are
we don’t support tiller
but it’s up to the charts to not use tiller features.
👍 1