https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
b
that error seems to indicate that your deployment hasn't come up because it wasn't able to attach a PVC. Where is your cluster deployed? Do you have a storage class deployed, did your persistent volumes get created?
ah, I notice it's in EKS. Can you show my the output of 
kubectl get storageclasses
g
Copy code
$ kubectl get storageclasses 

NAME                                PROVISIONER             AGE
gp2 (default)                       <http://kubernetes.io/aws-ebs|kubernetes.io/aws-ebs>   125m
helloworld-gp2-dqzz6skn (default)   <http://kubernetes.io/aws-ebs|kubernetes.io/aws-ebs>   123m
https://www.pulumi.com/docs/tutorials/kubernetes/eks/ I’ve followed this tutorial, and reused working eks cluster as provider for jenkins (i’ve copied jenkins.ts )
Copy code
export const instance = new jenkins.Instance({
    name: 'jenkins',
    credentials: {
        username: config.require("username"),
        password: config.require("password"),
    },
    resources: {
        memory: "512Mi",
        cpu: "100m",
    },
}, { provider: cluster.provider });
originally there was no provider, and that failed either with similiar error
I wondered how that jenkins class can be deployed into existing eks cluster without specifying the cluster
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by