pulumi-community #kubernetes

kubernetes

quaint-electrician-41503

10/02/2020, 7:18 PM

Thanks @broad-dog-22463, I am looking through that repo. I'm trying to understand facets of deploying helm charts with Pulumi. I'd like to seperate the configuration of the helm chart from IE the provisioning program which seems to be a primary goal of most pulumi configuration. However due to differences in kubernetes yaml, I haven't yet found an ideal option. One thing I was considering was keeping the helm chart configurations in their natural form and trying to apply them with your api. However for some feature like

helm -f values.yaml name /path/to/chart

which is natural via helm, I cannot IE apply

ConfigFile

for the values argument of

LocalChartOpts

miniature-leather-70472

10/05/2020, 11:13 AM

I'm trying to deploy a Helm chart using Pulumi component resource, I've got a values dictionary I am passing to the resource, but one of the values it needs is the name of the container registry to use, which is something I may create in my template, so the value is an Input<string> rather than just a string. This fails because the container registry name is not passed correctly, because it is an Input<T> any way to deal with this?

limited-rainbow-51650

10/06/2020, 12:49 PM

~ kubernetes:apps/v1:Deployment: (update)
        [id=deployer-ut11s29w/deployer-activities-k8s-l0dmq9rt]
        [urn=urn:pulumi:development::deployer::kubernetes:apps/v1:Deployment::deployer-activities-k8s]
        [provider=urn:pulumi:development::deployer::pulumi:providers:kubernetes::default_2_6_1::a73e10a4-562a-40e2-9db1-61bb39736827]
      ~ spec: {
          ~ template: {
              ~ spec: {
                  ~ containers: [
                      - [0]: {
                              - args           : [
                              -     [0]: "osimis-deploy-activities"
                                ]
                              - env            : [
                              -     [0]: {
                                      - name : "TEMPORAL_FRONTEND_HOST"
                                      - value: "<redacted>"
                                    }
                                ]
                              - image          : "<redacted>"
                              - imagePullPolicy: "Always"
                              - livenessProbe  : {
                                  - exec               : {
                                      - command: [
                                      -     [0]: "/bin/sh"
                                      -     [1]: "-c"
                                      -     [2]: "ps -ef | grep osimis-deploy-activities"
                                        ]
                                    }
                                  - failureThreshold   : 2
                                  - initialDelaySeconds: 10
                                  - periodSeconds      : 10
                                  - successThreshold   : 1
                                  - timeoutSeconds     : 5
                                }
                              - name           : "activities-worker"
                              - readinessProbe : {
                                  - exec               : {
                                      - command: [
                                      -     [0]: "/bin/sh"
                                      -     [1]: "-c"
                                      -     [2]: "ps -ef | grep osimis-deploy-activities"
                                        ]
                                    }
                                  - failureThreshold   : 6
                                  - initialDelaySeconds: 5
                                  - periodSeconds      : 10
                                  - successThreshold   : 1
                                  - timeoutSeconds     : 5
                                }
                              - resources      : {
                                  - limits  : {
                                      - cpu   : "0.15"
                                      - memory: "120Mi"
                                    }
                                  - requests: {
                                      - cpu   : "0.1"
                                      - memory: "100Mi"
                                    }
                                }
                              - volumeMounts   : [
                              -     [0]: {
                                      - mountPath: "/etc/pulumi-deployer/osimisdockercreds.conf"
                                      - name     : "osimis-docker-hub-credentials"
                                      - subPath  : "osimisdockercredes.conf"
                                    }
                                ]
                            }
                    ]
                }
            }
        }
Resources:
    ~ 1 to update
    8 unchanged

I’m not confident in applying this. What is happening? Context: Pulumi v2.11.2 + Kubernetes provider 2.6.1

limited-rainbow-51650

10/06/2020, 12:49 PM

I have a local change adding an additional environment variable to the Pod

spec

of a

Deployment

. That’s the only change, and I’m also the only one working with this stack, with which I want to clarify that no other team member could have made any changes. When I do a

preview --diff

, it wants to delete the

containers

section of the Pod `spec`:

quiet-wolf-18467

10/07/2020, 11:14 AM

Is it possible to get a

k8s.yaml.ConfigFile

or Helm template as straight up YAML in the Pulumi code?

quiet-wolf-18467

10/07/2020, 11:14 AM

I'm working on Cluster API integrations and I need to store this YAML as data keys within ConfigMaps and Secrets 🙂

limited-rainbow-51650

10/07/2020, 11:54 AM

Continuing with this setup: https://pulumi-community.slack.com/archives/C019YSXN04B/p1601995800036200 I’m wondering if I bumped into a bug regarding persistence of state. The automation API is running in a docker container, so I attached a cluster role & rolebinding with a set of permissions which I deemed enough to roll out a git based project/stack. In a previous run, Pulumi complained it couldn’t watch for the pods associated with a StatefulSet. Indeed, the

pods

resource was not added to list of permissions. Meanwhile, the statefulset and the pods are up and running though. So I redeployed the automation app with more permissions and ran again. But now it bails out complaining that my statefulset already exists. Running

pulumi stack export

shows me indeed that my statefulset is not recorded in the state. /cc @gorgeous-egg-16927

bitter-application-91815

10/08/2020, 11:07 AM

Hey there, I have deployed all my apps to kubs via helm charts, how to get the ingress endpoints for the cluster, the examples i can find only mention how to get it via an app deployment and corresponding service instance.

bitter-application-91815

10/08/2020, 11:07 AM

Basically

bitter-application-91815

10/08/2020, 11:07 AM

kubectl get ing -n axiomdb

bitter-application-91815

10/08/2020, 11:08 AM

axiomdb of course being my particular namespace

bitter-application-91815

10/08/2020, 11:23 AM

Is there any api for this ?

clever-byte-21551

10/11/2020, 1:36 PM

Why pulumi doesn’t encrypt in the state the kubernetes secret values? (the data property)

clever-byte-21551

10/11/2020, 1:37 PM

I’m using helm and I tried to pass the values i set there with

pulumi.ToSecret

and it is still saved to the state as plaintext @gorgeous-egg-16927

rough-tomato-98795

10/12/2020, 9:05 AM

Is there a way how to tell pulumi do delete pods with some flags? An app have kinda long grafecul period. Which results into pulumi failing to delete that pod. But in that case we are sure we want to delete that pod immediately without that graceful shutdown. (--grace-period=0 --force)

worried-city-86458

10/13/2020, 3:42 AM

I'm trying to deploy cert manager using the github url:

new ConfigFile($"{prefix}-cert-manager",
    new ConfigFileArgs { File = "<https://github.com/jetstack/cert-manager/releases/download/v1.0.3/cert-manager.yaml>" },
    new ComponentResourceOptions { Provider = kubeProvider });

worried-city-86458

10/13/2020, 3:43 AM

But if fails with `Failed to deserialize response message`:

Diagnostics:
  pulumi:pulumi:Stack (aws-alpha):
    error: Running program 'D:\Devel\Mps\devops-gemini-pulumi\Aws\bin\Debug\Aws.dll' failed with an unhandled exception:
    Grpc.Core.RpcException: Status(StatusCode=Internal, Detail="Failed to deserialize response message.")
       at Pulumi.GrpcMonitor.InvokeAsync(InvokeRequest request) in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Deployment/GrpcMonitor.cs:line 23
       at Pulumi.Deployment.InvokeAsync[T](String token, InvokeArgs args, InvokeOptions options, Boolean convertResult) in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Deployment/Deployment_Invoke.cs:line 36
       at Pulumi.Output`1.ApplyHelperAsync[U](Task`1 dataTask, Func`2 func) in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Core/Output.cs:line 226
       at Pulumi.Output`1.ApplyHelperAsync[U](Task`1 dataTask, Func`2 func) in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Core/Output.cs:line 226
       at Pulumi.Output`1.ApplyHelperAsync[U](Task`1 dataTask, Func`2 func) in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Core/Output.cs:line 241
       at Pulumi.Output`1.Pulumi.IOutput.GetDataAsync() in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Core/Output.cs:line 142
       at Pulumi.Serialization.Serializer.SerializeAsync(String ctx, Object prop) in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Serialization/Serializer.cs:line 136
       at Pulumi.Deployment.SerializeFilteredPropertiesAsync(String label, IDictionary`2 args, Predicate`1 acceptKey) in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Deployment/Deployment_Serialization.cs:line 54
       at Pulumi.Deployment.SerializeAllPropertiesAsync(String label, IDictionary`2 args) in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Deployment/Deployment_Serialization.cs:line 33
       at Pulumi.Deployment.RegisterResourceOutputsAsync(Resource resource, Output`1 outputs) in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Deployment/Deployment_RegisterResourceOutputs.cs:line 32
       at Pulumi.Deployment.Runner.<>c__DisplayClass7_0.<<WhileRunningAsync>g__HandleCompletion|0>d.MoveNext() in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Deployment/Deployment.Runner.cs:line 117
    --- End of stack trace from previous location ---
       at Pulumi.Deployment.Runner.WhileRunningAsync() in /home/travis/gopath/src/github.com/pulumi/pulumi/sdk/dotnet/Pulumi/Deployment/Deployment.Runner.cs:line 157

dazzling-sundown-39670

10/14/2020, 12:16 PM

I have a project I'm using pulumi for. One of the things pulumi is doing is building a docker image for me and pushing it to my container repo. One problem I have is that installing composer dependencies is taking forever and this means every single deploy is taking forever. I was thinking I could build one image that install the composer deps and then another image that uses that image. Is that possible in pulumi? Is there some way I can tell pulumi to only rebuild if for example

compose-lock.json

has changed?

icy-jordan-58549

10/14/2020, 4:55 PM

@gorgeous-egg-16927 is something changed or docs are super outdated, I am seeing new interface for transformations

export declare type ResourceTransformation = (args: ResourceTransformationArgs) => ResourceTransformationResult | undefined;

Also, is there a way to omit resources? I found this approach, https://github.com/pulumi/pulumi-kubernetes/issues/486#issuecomment-527958122 any other ways to workaround it? Thanks

bitter-application-91815

10/14/2020, 9:27 PM

Hi @gorgeous-egg-16927 any idea on that thread from the other day ?

bitter-application-91815

10/14/2020, 9:28 PM

https://pulumi-community.slack.com/archives/CRFURDVQB/p1602528180148000?thread_ts=1602156237.132200&cid=CRFURDVQB

gorgeous-animal-95046

10/19/2020, 7:04 PM

I’m seeing some “bad” behavior when I’m deploying a

deployment

whose replica count is controlled by an HPA. Basically when a

deployment

change happens, it will scale the replica set behind the deployment to

replica, destroying what the HPA has set. I originally had

replicas: 1

in the deployment spec, but I removed that and I still see this behavior. Anyone else experience this and is there a way to fix it?

limited-rain-96205

10/22/2020, 1:34 AM

What's the best way to create a Secret, and then not update the stringData field the next time?

miniature-leather-70472

10/22/2020, 8:53 AM

Is there any way to debug how Pulumi decomposes a Helm chart? I'm having an issue where a value I set in the Helm chart doesn't seem to be translated into the actual service Pulumi creates, all the other values work fine, but not this one and I can't see why

better-rainbow-14549

10/22/2020, 10:00 AM

i believe you can make it export and pulumify the chart to a folder?

loud-battery-37784

10/22/2020, 3:02 PM

Successfully installed the Datadog agent into our cluster but now am trying to figure out how to install the Istio integration. Stuck on the configuration step and how to do that via Pulumi on the Datadog agent Helm chart config https://docs.datadoghq.com/integrations/istio/#configuration Anybody successfully done this?

prehistoric-account-60014

10/23/2020, 3:45 PM

I’m having an issue in CI where I’ve updated

@pulumi/kubernetes

to the latest version (v2.6) but the state was using v2.2. In CI only the new one is installed (v2.6) and Pulumi fails because it attempts to load v2.2:

error: could not load plugin for kubernetes provider 'urn:pulumi:<snip>::pulumi:providers:kubernetes::default_2_2_2': failed to load plugin /<snip>/.pulumi/plugins/resource-kubernetes-v2.2.2/pulumi-resource-kubernetes: plugin not found

Is there a way to refresh the state so that it expects the latest version of the plugin instead of the older one?

some-doctor-15042

10/23/2020, 8:36 PM

Hello all! Im very new to pulumi and I was hoping to leverage the kubernetes provider to interact with an existing eks cluster but I keep getting the following -

error: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: Get "https://********************.<http://sk1.us-west-2.eks.amazonaws.com/openapi/v2?timeout=32s|sk1.us-west-2.eks.amazonaws.com/openapi/v2?timeout=32s>": getting credentials: exec: exit status 2

This is using typescript and the following guide - https://www.pulumi.com/docs/get-started/kubernetes/review-project/ Can pulumi not authenticate with the existing kubeconfig via an iam role?

fast-dinner-32080

10/26/2020, 7:16 PM

Hey guys, I am trying to lookup a kubernetes secret which holds the sa token and extract it. For some reason (in python) when I to a Secret.get and try to extract the token I just get a NoneType error. Its almost like it isn’t retrieving the data but if I switch the id to something that doesn’t exist it does give me an error saying it can’t find it so I know it is finding the secret. Just wanted to make sure I wasn’t doing something obviously wrong.

sa_secret = pulumi_kubernetes.core.v1.Secret.get(
    resource_name="vault-auth",
    id="kube-system/vault-auth-token-fsl4p",
    opts=ResourceOptions(
        provider=kubernetes_provider
    )
)
token = sa_secret.data.apply(lambda x: x['token'])

AttributeError: ‘NoneType’ object has no attribute ‘apply’

wet-noon-14291

10/27/2020, 3:12 PM

Hello. I'm trying to set up a k8s traefik ingress controller. I want to use the

PathType

property, but some reason it seems like the

PathType

isn't applied. I'm using pulumi .NET (F#, but that shouldn't matter). Anyone knows what might be up?

Title

wet-noon-14291

10/27/2020, 3:12 PM

Hello. I'm trying to set up a k8s traefik ingress controller. I want to use the

PathType

property, but some reason it seems like the

PathType

isn't applied. I'm using pulumi .NET (F#, but that shouldn't matter). Anyone knows what might be up?

created a issue on it: https://github.com/pulumi/pulumi-kubernetes/issues/1361

View count: 5