busy-umbrella-36067
10/01/2018, 6:13 PMlibc6-compat
package fixed it, it provides the libpthread
depsparse-insurance-40223
10/01/2018, 6:16 PMsparse-insurance-40223
10/01/2018, 6:17 PMsparse-insurance-40223
10/01/2018, 6:22 PMwhite-balloon-205
busy-umbrella-36067
10/01/2018, 6:40 PMsparse-insurance-40223
10/01/2018, 7:09 PMsparse-insurance-40223
10/01/2018, 7:09 PMbusy-umbrella-36067
10/01/2018, 7:20 PMvolumeMounts
and resources
scoped wrong
spec: {
containers: [{
name: coin.name,
image: "<http://978526999579.dkr.ecr.eu-west-1.amazonaws.com/|978526999579.dkr.ecr.eu-west-1.amazonaws.com/>"+xyz.name }],
resources: {
requests: {
memory: "2Gi",
cpu: "500m"
},
limits: {
memory: "4Gi",
cpu: "1"
}
},
volumeMounts: {
name: "data",
mountPath: "/data"
}
}
spec: {
containers: [{
name: coin.name,
image: "<http://978526999579.dkr.ecr.eu-west-1.amazonaws.com/|978526999579.dkr.ecr.eu-west-1.amazonaws.com/>"+xyz.name,
resources: {
requests: {
memory: "2Gi",
cpu: "500m"
},
limits: {
memory: "4Gi",
cpu: "1"
}
},
volumeMounts: [{
name: "data",
mountPath: "/data"
}]
}]
}
adorable-sundown-11370
10/01/2018, 7:49 PMsparse-insurance-40223
10/01/2018, 8:14 PMlittle-tailor-59400
10/01/2018, 8:36 PMlittle-tailor-59400
10/01/2018, 8:37 PMfresh-flag-12765
10/01/2018, 8:58 PMawesome-pulumi
github repo would be great 😛 Otherwise, I guess the pulumi/examples repo is the best place to get inspiration?adamant-restaurant-73893
10/01/2018, 10:07 PMfresh-flag-12765
10/01/2018, 10:11 PMglamorous-printer-66548
10/02/2018, 6:03 AMconst getK8sProviderByClusterName: (clusterName: string) => k8s.Provider
. It basically creates a k8s provider simply by passing a clustername (of an existing cluster - it will not magically create a new one) to it (and project id and zone are taken from the gcp config). The cluster is typically not defined itself in the stacks which use that utility function, so in order to get the cluster I’m using Cluster.get(...)
. The idea was to avoid having my team members to “correctly” configure their kubeconfig, set the right context etc. etc. but instead make the deployment target explicitly configured in code by using only the clusterName
. The problem I’m suddenly facing is that when anything non-substantial in the cluster changes, pulumi also wants to recreate (replace) the k8s provider and ALL the resources that have been previously created by that provider. Non-substantial changes in my case for example is that one of the node-pools scaled down by 1 instance. Even though I don’t use the node pool count at all to generate the k8s provider, pulumi wants to recreate it from scratch. Any advise on how to avoid this kind of problem? From my understanding Pulumi tracks here the dependency between the cluster and the k8s provider and because the k8s provider depends on the cluster any cluster changes will recreate the k8s provider. Is there any way to disable this auto-magic dependency tracking in this instance?cool-helicopter-70130
10/02/2018, 7:45 AMsparse-insurance-40223
10/02/2018, 9:30 AMsparse-insurance-40223
10/02/2018, 10:41 AMmillions-teacher-48727
10/02/2018, 10:41 AMsparse-insurance-40223
10/02/2018, 10:41 AMsparse-insurance-40223
10/02/2018, 11:00 AMsparse-insurance-40223
10/02/2018, 11:00 AMsparse-insurance-40223
10/02/2018, 11:14 AMsparse-insurance-40223
10/02/2018, 11:14 AMsparse-insurance-40223
10/02/2018, 11:14 AMadamant-restaurant-73893
10/02/2018, 4:11 PMalert-flower-49787
10/02/2018, 4:14 PMbusy-umbrella-36067
10/02/2018, 5:01 PM