https://pulumi.com logo
Join the conversationJoin Slack
Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-cdk
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumi-service
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Powered by Linen
kubernetes
  • f

    famous-bear-66383

    03/30/2020, 8:29 AM
    Hello community ! Quick question: I’d like to add labels to
    default namespace
    eg. istio injection label. How can I do that ?
    g
    • 2
    • 14
  • f

    fast-dinner-32080

    03/30/2020, 6:26 PM
    Is it expected that I have to ignore a bunch of properties so pulumi kubernetes doesn't always think it needs updated. A bunch of metadata like last-applied-configuration, creationTimestamp, labels.app.kubernetes.io/managed-by, resourceVersion, etc. and default properties are set when objects are created and now pulumi thinks they need replaces/updated each time i run up. I enabled "enableDryRun" on the kubernetes provider and refreshed but that doesn't seem to change anything.
    • 1
    • 1
  • h

    hundreds-portugal-17080

    03/30/2020, 8:55 PM
    Hi, question on spinning up eks with some helm charts. When I perform pulumi up, does pulumi up implementation waits for all pods to be running or failed or certain pod state before it exits? In other words, How does pulumi up command knows when to say it has completed its command execution.
    g
    • 2
    • 5
  • f

    fast-dinner-32080

    03/31/2020, 4:29 AM
    I am running pulumi with the kubernetes provider manually set but I also manually updated my KUBECONFIG to a bad value. Now when I run it I get this warning "warning: configured Kubernetes cluster is unreachable: unable to load Kubernetes client configuration from kubeconfig file: invalid configuration: no configuration has been provided" Why does it care about my env variable and/or file if I am manually setting the provider and setting the kubeconfig. I have found a few times it tries to load the env var or file when I do not want it too so I am manually setting it too a bogus value to make sure it doesn't mess with my current local context.
    g
    b
    • 3
    • 11
  • a

    ancient-megabyte-79588

    03/31/2020, 2:27 PM
    message has been deleted
    g
    • 2
    • 2
  • a

    ancient-megabyte-79588

    03/31/2020, 2:27 PM
    message has been deleted
  • a

    ancient-megabyte-79588

    03/31/2020, 2:27 PM
    message has been deleted
  • f

    fast-dinner-32080

    03/31/2020, 4:20 PM
    Rancher just released the new version 2.4.0 but I am unable to upgrade to it due to the helm fecth extracting two directories. Seems like the logic to get the templates/values expects the untar to only have a single directory extracted and not two. I logged an issue earlier here https://github.com/pulumi/pulumi-kubernetes/issues/1046 but now I cannot upgrade rancher which is something we need to start testing. I am using dotnet but I am guessing the other sdks also have the same issue.
    g
    • 2
    • 15
  • a

    ancient-megabyte-79588

    03/31/2020, 4:59 PM
    @gorgeous-egg-16927 Now that you have self-identified as a kubernetes expert! 😄 I'm getting this error when trying to update a
    configMap
    The
    configMap
    above generates this error and there isn't a lot in the details to suggest what is wrong.
  • a

    ancient-megabyte-79588

    03/31/2020, 5:00 PM
    Is there guidance in how to interpret the data in the
    details
    that are output?
  • a

    ancient-megabyte-79588

    03/31/2020, 5:02 PM
    In the
    details
    color console, are the red lines existing and green the intended replacement and that is what the task is suggesting won't work?
    g
    • 2
    • 18
  • c

    calm-greece-42329

    04/01/2020, 7:04 PM
    got a problem and not sure of the best solution.. im trying to run kafka in kubernetes and i need to provide an environment variable to the pods with the service name they provide. this is for them to advertise. so essentially i need a deployment with a service, but i need to know the service name inside of the deployment
  • c

    calm-greece-42329

    04/01/2020, 7:04 PM
    should i just generate my own auto-name?
  • a

    ancient-megabyte-79588

    04/01/2020, 7:10 PM
    export consts serviceName = "<something you generate>-svc";
    at the top of your pulumi app?
  • c

    calm-greece-42329

    04/01/2020, 7:11 PM
    yeah, i was thinking along those lines
  • a

    ancient-megabyte-79588

    04/01/2020, 7:12 PM
    I haven't looked to see if you can export a
    label
    value into a env var .. labels are the native grouping mechanism in k8s
  • c

    calm-greece-42329

    04/01/2020, 7:12 PM
    well, the issue is that the deployment depends on the service, and the service depends on the deployment, but really only for the auto-name
    g
    • 2
    • 1
  • c

    calm-greece-42329

    04/01/2020, 7:13 PM
    i can do something like `
    const nameSuffix = `-${pulumi.getProject()}-${pulumi.getStack()}
    and mash it into all of my metadata
  • c

    calm-greece-42329

    04/01/2020, 7:16 PM
    kubernetesx makes everything so much easier until you need to do something just outside of its narrow confines
    g
    • 2
    • 1
  • a

    ancient-megabyte-79588

    04/01/2020, 9:08 PM
    message has been deleted
  • a

    ancient-megabyte-79588

    04/01/2020, 9:09 PM
    message has been deleted
    b
    • 2
    • 5
  • a

    ancient-megabyte-79588

    04/01/2020, 9:10 PM
    Mostly, I don't seem to be able to figure out how to configure the chart correctly.
  • h

    hundreds-portugal-17080

    04/04/2020, 5:18 PM
    Hi, Trying to better understand customTimeouts on the resource. I have set 2 min on the timeout on creating helm charts. I am observing that a k8 is not able to find resources to assign in k8 and thats fine but main issue is that its taking around 8 min instead of exiting after 2 min. Am I doing something wrong with the timeout? new k8s.helm.v2.Chart("XYZ", { PATH goes here. },{ providers: { "kubernetes": this.cluster.provider },customTimeouts: { create: "2m", delete: "2m", update: "2m", } }
    w
    • 2
    • 2
  • b

    boundless-morning-59924

    04/07/2020, 9:32 AM
    I've done some investigation on how to create a CD-setup, and I think that I've found a good solution using multiple stacks for identity/infrastructure/app-deployments for a monorepo-setup. We are however now trying to split up some of our code into smaller repositories, and that is when I think it will become somewhat tricky to handle. My idea is to have a separate repo for the pulumi infrastructure configuration, where I can create database instances, k8s-cluster (with external IP, ingress, ssl-cert) and more. In the repo for each service (k8s-deployment) I would like to get hold of the Ingress-definition from the shared infra-stack, and modify the ingress-rule-spec according to each service's needs. Would this be possible, or should I try to modify the structure in any other way? (I'm using GCP/GKE and Typescript)
    g
    b
    • 3
    • 12
  • b

    breezy-hamburger-69619

    04/07/2020, 4:29 PM
    A new set of changes has been merged for
    pulumi/eks
    [1] and is available in NPM [2] under version
    0.18.25-alpha.1586233126
    In this set of changes, we’ve added: • Support for proxied environments • Role-based kubeconfigs • And swapped out
    aws-iam-authenticator
    with
    aws eks get token
    used in kubeconfig auth We would love to hear back from
    pulumi/eks
    users on their experience using this version to better understand how these changes work with you and your clusters. Please let us know any feedback or open up a new issue [3]. Thank you! 1 - https://github.com/pulumi/pulumi-eks/blob/master/CHANGELOG.md#unreleased 2 - https://www.npmjs.com/package/@pulumi/eks 3 - https://github.com/pulumi/pulumi-eks/issues/new
  • b

    breezy-gold-44713

    04/07/2020, 11:59 PM
    How can I emulate this via pulumi from pulumi config secrets?
    kubectl create secret tls myservice-tls --cert=myservice.cert.pem --key=myservice.key.pem --dry-run -o yaml
    . I’ve tried manually constructing a TLS secret with the exact contents of the yaml file, but it doesn’t work for some reason. I feel like I must be missing something obvious, any insights?
    b
    g
    • 3
    • 8
  • b

    better-rainbow-14549

    04/08/2020, 12:49 PM
    i'm trying to go through and tag all the sensitive values we have in our stacks with
    additionalSecretOutputs
    - keyvault secrets, service principal passwords etc but when i get to
    kubernetes.Provider
    it doesn't accept that property in ResourceOptions
    • 1
    • 2
  • a

    ancient-megabyte-79588

    04/08/2020, 8:31 PM
    I'm having trouble converting this ConfigMap into a pulumi .ts representation.
    kind: ConfigMap
    apiVersion: v1
    metadata:
      name: nginx-nginx-ingress-controller
      namespace: kube-system
      labels:
        k8s-app: nginx-ingress-controller
    data:
      proxy-buffer-size: "128k"
      proxy-buffers: "8 128k"
    I've already got k8s resource in the cluster via manifest and I'm trying to import it so I can change it in pulumi, but I can't get the
    data
    sections to match up and so pulumi won't let it work.
  • a

    ancient-megabyte-79588

    04/08/2020, 8:32 PM
    This does not work
    export const nginxIngressControllerConfigMap = new k8s.core.v1.ConfigMap("nginx-nginx-ingress-controller", {
        metadata:{
            name: "nginx-nginx-ingress-controller",
            labels: {"k8s-app": "nginx-ingress-controller"},
            namespace:"kube-system"
        },
        data: {
            "proxy-buffer-size": "128k",
            "proxy-buffers": "8 128k"
        }
    },{provider: k8sProvider, import: "kube-system/nginx-nginx-ingress-controller"});
    g
    • 2
    • 15
  • a

    ancient-megabyte-79588

    04/08/2020, 8:32 PM
    kubernetes:core:ConfigMap (nginx-nginx-ingress-controller):
        error: inputs to import do not match the existing resource
Powered by Linen
Title
a

ancient-megabyte-79588

04/08/2020, 8:32 PM
kubernetes:core:ConfigMap (nginx-nginx-ingress-controller):
    error: inputs to import do not match the existing resource
View count: 4