• v

    victorious-dusk-75271

    1 month ago
    whats the right way to pass nested value to helm.v3.Release? i am trying to pass
    serviceAccount.create: false
    but its not picking uphttps://github.com/aws/eks-charts/tree/master/stable/aws-load-balancer-controller i have tried both { serviceAccount: { create: false }} and 'serviceAccount.create': false
    v
    1 replies
    Copy to Clipboard
  • b

    bright-horse-50102

    1 month ago
    Does helm.v3.Release not support transformations like charts do?
    b
    w
    +1
    3 replies
    Copy to Clipboard
  • f

    few-pillow-1133

    1 month ago
    Getting some weird error
    Exception: Cannot read properties of null (reading 'data')
        error: TypeError: Cannot read properties of null (reading 'data')
            at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/cluster.ts:580:103
            at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/output.ts:383:31
            at Generator.next (<anonymous>)
            at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/pulumi/output.js:21:71
            at new Promise (<anonymous>)
            at __awaiter (/root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/pulumi/output.js:17:12)
            at applyHelperAsync (/root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/pulumi/output.js:229:12)
            at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/output.ts:302:65
            at processTicksAndRejections (node:internal/process/task_queues:96:5)
        error: an unhandled error occurred: Program exited with non-zero exit code: 1
    f
    r
    3 replies
    Copy to Clipboard
  • m

    millions-judge-24978

    1 month ago
    Hi, is there any example on how to generate a
    k8s.Provider
    for an existing EKS cluster? I would like to be able to do something like
    eks.getClusterOutput({...}).provider
    , as I would be able to if I had just created with
    new eks.Cluster({...}).provider
    . Failing that, at least how I can generate the
    kubeconfig
    file text from
    eks.getClusterOutput().something
    .
    m
    b
    4 replies
    Copy to Clipboard
  • b

    bored-spoon-83710

    1 month ago
    Hello, I’m trying to deploy the same chart in two different clusters (in the same Pulumi project), but I’m having issue with naming: I can’t use the same Pulumi logical name for my two chart resources (else Pulumi complains about duplicate resource URN) and I didn’t find a way to override the release name used when templating the chart. Is it a deliberate choice to not let the user modify the release name (maybe I just didn’t see how to do it) or is it a missing feature which could be implemented (potentially by me when I’ve time)?
    b
    b
    14 replies
    Copy to Clipboard
  • v

    victorious-church-57397

    1 month ago
    Hi there team 👋 I'm trying to pulumify some k8s config and hit a bit of a bump in the road when trying to convert the k8s yaml to pulumi using kube2pulumi.
    unable to run program: Error: unknown resource type 'kubernetes:<http://garo.tietoevry.com/v1alpha1:GithubActionRunner|garo.tietoevry.com/v1alpha1:GithubActionRunner>'
    
      on pcl-087019550.pp line 0:
       1: resource "github_actions_runner_operatorRunner_poolGithubActionRunner" "kubernetes:<http://garo.tietoevry.com/v1alpha1:GithubActionRunner|garo.tietoevry.com/v1alpha1:GithubActionRunner>" {
    
    unknown resource type 'kubernetes:<http://garo.tietoevry.com/v1alpha1:GithubActionRunner|garo.tietoevry.com/v1alpha1:GithubActionRunner>'
    Is there anything i can do locally to get the program to recognise the resource type? I'm installing the CRDs etc using helm, but need to deploy the actual deployment separately
    v
    b
    3 replies
    Copy to Clipboard
  • v

    victorious-dusk-75271

    1 month ago
    How do you provide
    scheme
    in in spec? typescript is complaining about it
    apiVersion: elbv2.k8s.aws/v1beta1
    kind: IngressClassParams
    metadata:
      name: awesome-class
    spec:
      scheme: internal
      ipAddressType: dualstack
      tags:
      - key: org
        value: my-org
  • v

    victorious-church-57397

    1 month ago
    hey peeps, im installing a helm chart to install an operator and all the CRDs i need, and then im using the pulumi k8s.
    CustomResource
    to try and deploy an instance of the resource which is configured on the cluster with the helm chart. I've got pulumi creating it, and it all looks good but no pods are actually being deployed, if i manually run
    kubectl apply -f
    on the yaml file, then it works fine but not when ive converted it to a JS object format, cant help but thinking the
    CustomResource
    might not be what im after?
    v
    b
    10 replies
    Copy to Clipboard
  • i

    incalculable-midnight-8291

    3 weeks ago
    Is there some way to tag
    k8s.helm.v3.Release
    so that pulumi skips uninstall on a stack destroy, where the cluster itself will be taken down?
    i
    b
    7 replies
    Copy to Clipboard
  • b

    bright-horse-50102

    1 month ago
    Does Pulumi currently not support StatefulSets with the OnDelete update strategy? My observations:1. When updating a StatefulSet using the OnDelete strategy, Pulumi will (erroneously?) wait on
    Waiting for StatefulSet update to roll out (0/n Pods ready)
    2. If you do update the pods yourself while Pulumi is waiting, Pulumi will continue to wait on
    Waiting for StatefulSet update to roll out (n/n Pods ready)
    , and eventually error and time out because
    .status.currentRevision
    was not updated to
    .status.updatedRevision
    :
    Diagnostics:
      kubernetes:apps/v1:StatefulSet (interactions-app):
        error: 3 errors occurred:
            * the Kubernetes API server reported that "default/interactions-app-b2ecafa3" failed to fully initialize or become live: 'interactions-app-b2ecafa3' timed out waiting to be Ready
            * 32 out of 32 replicas succeeded readiness checks
            * StatefulSet controller failed to advance from revision "interactions-app-b2ecafa3-646dcff454" to revision "interactions-app-b2ecafa3-569b7cb476"
    Relevant issue? https://github.com/pulumi/pulumi-kubernetes/issues/1066
    b
    g
    4 replies
    Copy to Clipboard