• p

    powerful-planet-88446

    4 months ago
    Is it possible to organise stacks in a subfolder?
  • p

    powerful-planet-88446

    4 months ago
    I have an infrastructure project for several Kubernetes clusters and I'm concerned about there being so many Pulumi stack config files at the top level
  • p

    powerful-planet-88446

    4 months ago
    Because I have a stack-per-cluster
  • a

    adorable-computer-41765

    4 months ago
    @powerful-planet-88446 absolutely, check out: https://www.pulumi.com/docs/guides/organizing-projects-stacks/. If you are worried about access control as well to those projects and stacks you should check out the following features in the pulumi service: https://www.pulumi.com/docs/intro/pulumi-service/teams/ & https://www.pulumi.com/docs/intro/pulumi-service/projects-and-stacks/#stack-permissions
    a
    p
    6 replies
    Copy to Clipboard
  • r

    red-leather-22955

    4 months ago
    Hi, We are just getting started using Pulumi in our organisation. We are using Python as we are a Python shop for our main applications. We have got Pulumi creating an eks cluser using pulumi-eks, now we are trying to get it to actually deploy something to the cluster. We are following https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/eks/ modifying the code as that is in JavaScript/TypeScript, however it I'm having problems when specifying the cluster The example has:
    {
            provider: cluster.provider,
    }
    as the third parameter(opts), I tried converting this to Python as:
    opts=pulumi.ResourceOptions(provider=cluster.provider),
    However my IDE complains about it being the wrong type (Output[Provider] instead of ProviderResource) and when running
    pulumi up
    , I get:
    ValueError: Attempted to register resource kubernetes:apps/v1:Deployment with a provider for '<pulumi.output.Output object at 0x7f695f68c5d0>'
        error: an unhandled error occurred: Program exited with non-zero exit code: 1
    Any idea of what I am doing wrong or how I can fix this?
    r
    b
    4 replies
    Copy to Clipboard
  • w

    white-chef-55657

    4 months ago
    hi folks, I’m looking to test a pulumi k8s setup as part of CI before actually deploying to production has anyone tried out https://github.com/helm/kind-action or https://github.com/marketplace/actions/setup-minikube ?
  • w

    white-chef-55657

    4 months ago
    https://docs.datadoghq.com/agent/kubernetes/control_plane/?tab=helm#EKS datadog recommends adding annotations to default/kubernetes service so API server metrics are collected with pulumi, I can’t seem to find a way to GetService, but even so I remember that all of the attributes are read only and I can’t seem to find a way to specify this customization in the
    eks.Cluster
    resource ideas?
  • f

    fast-florist-41572

    4 months ago
    I am trying to replicate what the
    pulumi-eks
    package does in golang but I appear to get an error. I'm trying to update the configmap for
    aws-auth
    . In the nodejs/eks version it does this
    const eksNodeAccess = new k8s.core.v1.ConfigMap(`${name}-nodeAccess`, {
            apiVersion: "v1",
            metadata: {
                name: `aws-auth`,
                namespace: "kube-system",
            },
            data: nodeAccessData,
        }, { parent, provider: k8sProvider });
    Which appears to work by actually altering the configmap. However in golang when I try do the same I get an error
    _, err = corev1.NewConfigMap(ctx, "aws-auth", &corev1.ConfigMapArgs{
    			Metadata: &metav1.ObjectMetaArgs{
    				Name: pulumi.String("aws-auth"),
    				Namespace: pulumi.String("kube-system"),
    			},
    			Data:       pulumi.StringMap{
    				"mapRoles": roleConfig,
    			},
    		}, pulumi.Provider(kubeProvider))
    The error is
    resource kube-system/aws-auth was not successfully created by the Kubernetes API server : configmaps "aws-auth" already exists
    f
    o
    4 replies
    Copy to Clipboard
  • f

    fast-florist-41572

    4 months ago
    How does the node version manage to do it whilst the go version can't?
  • f

    flat-laptop-90489

    4 months ago
    I'm trying to build out an EKS project in go, and I'm having some issues with credentials and providers. Wondering if anyone has tried this particular scenario yet. We have a Hashicorp Vault AWS credential backend already configured for this account. SO - I have pulumi grabbing some AWS credentials from Vault, building an AWS provider, and then using that for all of my AWS resources. This works well for most things (VPC created already, etc.) But, when I use pulumi-eks to build an EKS cluster with this provider, it fails to validate that the cluster is running. From the error messages, it appear that the pulumi operator (which is running this code), is trying to use its own credentials to access the cluster afterwards. SO, I think there's some issue with the Kubernetes provider that gets generated not using the AWS provider credentials that I used to create the cluster. At this point, I have no clue how to get around this, other than to not use the pulumi-eks library, and instead build out the cluster and node groups, etc. myself using the "standard" aws library. This would allow me to control the K8s provider that gets generated and the aws-auth configmap myself (I think) Am I missing something, or is that the correct path forward here? Also, let me know if I should post this in AWS or Go instead
    f
    o
    +1
    35 replies
    Copy to Clipboard