https://pulumi.com logo
Powered by
Title
b

busy-journalist-6936

07/29/2021, 8:22 PM
Okay, first pulumi experience, I have EKS building with my index.ts, I wanted to also deploy a helm chart as part of my base platform IaC. Can 
k8s.helm.v3.Chart
inherit the credentials for the cluster it built? How do I go from building the cluster to also deploying stuff to it? if I manually pull the kubeconfig (future will be oidc) and re-run 
pulumi up
everything deploys fine. index.ts LINK
b

billowy-army-68599

07/29/2021, 8:51 PM
Hey Kathryn! Yes this is a common pattern 🙂 Your EKS resource outputs a 
provider
which can then be passed to your Kubernetes resources! https://github.com/pulumi/examples/blob/master/aws-ts-eks-hello-world/index.ts#L60 Your pass it to your resource via the helm chart's resource options, so in this case it'd be: 
const kongGateway = new k8s.helm.v3.Chart("gateway", {
  repo: "kong",
  chart: "kong",
  // TODO: tear down and change namespace to `kong`
  namespace: "default",
  fetchOpts:{
    repo: "<https://charts.konghq.com/>",
  },
  values: {
    postgresql: {
      enabled: true,
    }
  },
},
providers: { kubernetes: cluster.provider } }
);
regarding your comment about the namespace, you can also create your namespace and pass that to your helm chart too: https://github.com/jaxxstorm/pulumi-examples/blob/main/typescript/digitalocean/kubernetes/index.ts#L44
b

busy-journalist-6936

07/29/2021, 9:03 PM
awesome!!!!! giving this a go
b

billowy-army-68599

07/29/2021, 9:06 PM
I haven't actually tested the helm example, hopefully your IDE can help 😄
b

busy-journalist-6936

07/29/2021, 9:10 PM
ha, just in vim for now. should switch over to VSCode
Okay, updated gist. Erroring out, but it's odd to me that it is, because it definitely did create the namespace. So the kubeconfig 
provider
cant be garbage. Unless I somehow created the namespace somewhere else after deploying this fresh cluster without remembering. 
<http://kongclusterplugins.configuration.konghq.com|kongclusterplugins.configuration.konghq.com> (kubernetes:<http://helm.sh/v3:Chart$kubernetes:apiextensions.k8s.io/v1beta1:CustomResourceDefinition|helm.sh/v3:Chart$kubernetes:apiextensions.k8s.io/v1beta1:CustomResourceDefinition>)
error: configured Kubernetes cluster is unreachable: unable to load Kubernetes client configuration from kubeconfig file: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
If the cluster has been deleted, you can edit the pulumi state to remove this resource

default/gateway-kong (kubernetes:<http://helm.sh/v3:Chart$kubernetes:apps/v1:Deployment|helm.sh/v3:Chart$kubernetes:apps/v1:Deployment>)
error: configured Kubernetes cluster is unreachable: unable to load Kubernetes client configuration from kubeconfig file: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
If the cluster has been deleted, you can edit the pulumi state to remove this resource

  pulumi:pulumi:Stack (KongOnEKS-KongOnEKS):
    W0729 22:20:38.072566    2219 loader.go:223] Config not found: /root/.kube/config
 
    error: update failed
b

billowy-army-68599

07/29/2021, 10:22 PM
Ah, the provider field on the helm chart is slightly different to kubernetes resources
b

busy-journalist-6936

07/29/2021, 10:22 PM
looking back at it.
b

billowy-army-68599

07/29/2021, 10:22 PM
Notice the kubernetes map of the map here { providers: { kubernetes: provider } },
https://github.com/jaxxstorm/pulumi-examples/blob/480b0d2f9618dc3b4c91b51af6061452875bc8ad/typescript/digitalocean/kubernetes/index.ts#L60
b

busy-journalist-6936

07/29/2021, 10:23 PM
Ah, k, didnt see it as a value here: https://www.pulumi.com/docs/reference/pkg/kubernetes/helm/v3/chart/
learning how to navigate docs still I suppose
b

billowy-army-68599

07/29/2021, 10:37 PM
ah, that's because the helm chart resource is a component resource, and the provider options goes on that
https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/#ComponentResourceOptions-providers
b

busy-journalist-6936

07/29/2021, 10:39 PM
Success!!! Now on to learning how to create kubernetes secrets in pulumi before the helm chart deploys.
++ @billowy-army-68599 thank you!
b

billowy-army-68599

07/29/2021, 10:40 PM
Now on to learning how to create kubernetes secrets in pulumi before the helm chart deploys.
if you define a secret output as an input to the helm chart, this will happen automatically, similar to what you did with the namespace earlier
@busy-journalist-6936 once you have this all working, I'd be interested in helping you turn this into a component that other users can reuse, keep me updated!
b

busy-journalist-6936

07/29/2021, 10:42 PM
I'm 100% on board with getting it mature enough for wider use. *disclaimer I work for Kong
b

billowy-army-68599

07/29/2021, 10:43 PM
excellent, once you're in a good place, DM me and we can chat more!
👍 1
b

busy-journalist-6936

07/29/2021, 10:46 PM
@billowy-army-68599 do you have an example of that secret thing which would be equivalent to something like: 
kubectl create secret generic \
  kong-enterprise-license -n kong \
  --from-file=./license
I can do 
--from-literal
style instead and make the license part of pulumi config
b

billowy-army-68599

07/29/2021, 11:00 PM
Not to hand, but you should be able to use fs.readFileSync to read the file and then input it into stringData
5 Views
#kubernetesJoin Slack
Powered by