• c

    curved-morning-41391

    4 months ago
    Anyone have good patterns around getting AWS credentials into a K8s cluster?
  • c

    curved-morning-41391

    4 months ago
    I could obviously set them as secrets in the configfile, but was wondering if there was a way to grab them out of my local credentials file?
    c
    s
    3 replies
    Copy to Clipboard
  • f

    flat-laptop-90489

    4 months ago
    Is it for the aws account that your cluster is in? You could use IRSA or kube2iam to assume roles instead
  • f

    flat-laptop-90489

    4 months ago
    More fun with pulumi-eks and the pulumi-kubernetes-operator -
    Unable to connect to the server: getting credentials: exec plugin is configured to use API version <http://client.authentication.k8s.io/v1beta1|client.authentication.k8s.io/v1beta1>, plugin returned version <http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>
    I was able to fix this error locally by updating to a newer version of the awscli. I can't seem to find where this is defined for the pulumi containers. Any thoughts on a workaround, and/or should I file an issue somewhere for this?
    f
    b
    +3
    30 replies
    Copy to Clipboard
  • b

    breezy-bear-50708

    4 months ago
    Hi all, I'm trying to use the v3.Chart resource. However I'm running into an issue that I can't seem to replicate
    --set-file
    , used for a template that that replaces a value with the file's contents. If I 1) use a json object as the value, it blows up with
    wrong type for value; expected string; got []interface {}
    . If I try to pass a yaml string literal, pulumi helpfully escapes all the newlines so that doesn't work either. So wondering if anyone knows of a way to duplicate whatever helm template --set-file does.
    b
    1 replies
    Copy to Clipboard
  • b

    busy-island-31180

    4 months ago
    Does anyone know why “health” checking is implicitly part of the “create” lifecycle for k8s objects? If health fails, it thinks that create fails, and the object doesn’t get stored in state. Subsequent runs fail with “already exists” error from kubernetes. I filed an issue:https://github.com/pulumi/pulumi-kubernetes/issues/1994 I think this is a fairly high priority / common use case.
    b
    1 replies
    Copy to Clipboard
  • a

    acceptable-mechanic-48231

    3 months ago
    Hey there! Posting my questions here because I think they are most relevant here, but if I should move this to another channel that's better suited, then let me know. I am building a component resource provider, in Go, for easily deploying my company’s platform, which is a cloud environment, such as a VPC and EKS cluster, with a suite of open-source tools that gets deployed to Kubernetes. I’ve ran into a dilemma and I’m not sure how to proceed. I’m trying to make use of the Kubernetes provider’s “CustomResource” resource in order to configure an ArgoCD application custom resource. I’ve hit a snag with that "CustomResource" resource type because one of its arguments doesn't implement Pulumi types, specifically the
    OtherFields
    field, ref. Because of that, I can’t pass it a Pulumi type for a value. This is an issue for me because my custom resource needs to support resource dependencies for a
    dependsOn
    to work, but as far as I know Pulumi’s provider type checking requires that fields implement Pulumi types if a resource is to have dependencies. Implementing plain types when my provider’s resource has a
    dependsOn
    results in an error like the following:
    error: program failed: waiting for RPCs: rpc error: code = Unknown desc = setting args: copying input "spec": application.ArgocdAppArgs.Spec is typed as map[string]interface {} but must be a type that implements pulumi.Input or pulumi.Output for input with dependencies
    Which seems to originate from here: https://github.com/pulumi/pulumi/blob/master/sdk/go/pulumi/provider.go#L564. Which seems odd that this is even a problem, because my dependency is simply a
    dependsOn
    , not an actual field dependency. So with all of that backstory laid out, my main questions are: How do I pass a pulumi type to a resource that implements a plain type? If that’s not possible, is it possible to get around the pulumi provider type checking that is requiring all fields to implement pulumi types when there are dependencies?
    a
    b
    5 replies
    Copy to Clipboard
  • c

    curved-morning-41391

    3 months ago
    Hey is it possible to deploy a local cluster using minikube/kind/k3s using pulumi?
    c
    b
    +1
    4 replies
    Copy to Clipboard
  • l

    little-vegetable-79574

    3 months ago
    Pulumi keeps overwriting
    .kube/config
    on
    pulumi up
    . How do you make it not touch the file?
    l
    s
    2 replies
    Copy to Clipboard
  • f

    famous-salesclerk-74711

    3 months ago
    👋 quick q for yall - we’re using the helm.v3 construct, but the chart we’re consuming wraps an entire resource template with:
    if (.Capabilities.APIVersions.Has <some-api-resource-version>)
    which always fails, bc apparently this check returns false. is there a known way for pulumi-k8s operators to work around this, specifically around hydrating
    .Capabilities
    ? https://github.com/pulumi/pulumi-kubernetes/issues/196
    f
    f
    3 replies
    Copy to Clipboard