colossal-car-2729
11/09/2021, 3:37 PMk8s.helm.v3.chart
when switching from LocalChartOpts
to ChartOpts
(so instead of using a chart in a local repository using some upstream repo).
In my values.yaml is a line like this:
{{ .Files.Get “files/fluentd-prometheus.conf” | indent 4 }}
The file is read with LocalChartOpts
but is just empty with ChartOpts
. I assume the working directory with ChartOpts
is neither where pulumi up
is executed nor where the values.yaml file is located. Any idea one this?modern-city-46733
11/09/2021, 5:06 PMError: rendered manifests contain a resource that already exists. Unable to continue with install: MutatingWebhookConfiguration "aws-load-balancer-webhook" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "<http://meta.helm.sh/release-name|meta.helm.sh/release-name>" must equal "aws-load-balancer-controller": current value is "release-xxxxx"
witty-belgium-75866
11/11/2021, 10:50 AMaws-load-balancer-controller
chart on my EKS cluster, by using pulumi ( Python ).
The installation goes well, but every time I'm executing pulumi up
or pulumi preview
, some of its resources are being changed:
it's very unnecessary and time consuming.
anybody encountered that? thx!big-potato-91793
11/11/2021, 9:00 PMDiagnostics:
kubernetes:<http://networking.k8s.io/v1:Ingress|networking.k8s.io/v1:Ingress> (ingress-name):
error: 1 error occurred:
* the Kubernetes API server reported that "namespace/ingress-name" failed to fully initialize or become live: Ingress.extensions "ingress-name" is invalid: spec.rules[0].http.paths[0].backend: Invalid value: "": resource or service backend is required
If, i rerun back my pipeline everything pass without any problem.
Any idea?nutritious-petabyte-61303
11/12/2021, 2:25 AMnutritious-petabyte-61303
11/12/2021, 2:25 AMnutritious-petabyte-61303
11/12/2021, 2:26 AMnutritious-petabyte-61303
11/12/2021, 2:26 AMnutritious-petabyte-61303
11/12/2021, 2:26 AMnutritious-petabyte-61303
11/12/2021, 2:26 AMnutritious-petabyte-61303
11/12/2021, 2:26 AMnutritious-petabyte-61303
11/12/2021, 2:27 AMnutritious-petabyte-61303
11/12/2021, 2:28 AMmammoth-honey-6147
11/12/2021, 2:23 PMCertificate, err := apiextensions.NewCustomResource(ctx, "cert", &apiextensions.CustomResourceArgs{
// Various fields, etc
}
Which works perfectly fine - However, I need to effectively "wait" until the cert is in ready
state - I'm using a DNS challenge method so it can take ~60-90 seconds. I have another app that references the cert that's generated via the corresponding secret, which, I believe, isn't in a fully formed state as the app reads the secret before the entire chain is fully complete. Therefore, how can I facilitate this wait in my code?
I could do this by inspecting the status
field of the API object but it looks like I can't do that with the current SDKquick-television-97606
11/12/2021, 11:25 PMnutritious-petabyte-61303
11/15/2021, 3:49 PMnutritious-petabyte-61303
11/15/2021, 3:49 PMglamorous-australia-21342
11/16/2021, 12:45 AMconfigured Kubernetes cluster is unreachable: unable to load schema information from the API server: the server has asked for the client to provide credentials
. We have a role that is defined in pulumi rolemappings
for the cluster and I can confirm the IAM role is in aws-auth configmap. Anyone can auth to the cluster with k9s or kubectl using this role, but if anyone tries to do pulumi commands we get this auth error above. I can do anything beause I created the cluster I guess. I even tried using a different test account and have no issues, but my colleagues and my CI is broken. I am not using a providercredentialopts so pulumi is using whatever profile is in the default profile.glamorous-australia-21342
11/16/2021, 12:47 AMpurple-plumber-90981
11/16/2021, 11:01 PM<https://github.com/kubernetes-csi/external-snapshotter/tree/release-4.0/client/config/crd>
square-coat-62279
11/17/2021, 11:59 AMconst container: k8stypes.core.v1.Container = {
readinessProbe: props.deployment.readinessProbe || null,
while some of my deployments may not have readinessProbe defined, would the code above work?wonderful-twilight-70958
11/19/2021, 5:52 PMminiature-leather-70472
11/23/2021, 10:06 AMwonderful-twilight-70958
11/23/2021, 4:20 PMpost-step event returned an error: failed to verify snapshot: urn:pulumi:dev::pi-vpc-eks::eks:index:Cluster$kubernetes:<http://storage.k8s.io/v1:StorageClass::gateway-cluster-gp2|storage.k8s.io/v1:StorageClass::gateway-cluster-gp2> refers to unknown provider urn:pulumi:dev::pi-vpc-eks::eks:index:Cluster$pulumi:providers:kubernetes::gateway-cluster-eks-k8s::408665c4-5bbf-4595-a470-4b204f053b35
a lot recently when destroying an eks cluster that has a storage class specified. It's like there's some dependency not working correctly and it tries to destroy the storageclass after the cluster / provider is already gone?numerous-printer-41511
11/23/2021, 8:22 PMpulumi import
work with k8s objects?big-potato-91793
11/24/2021, 2:40 PMv1
version of the ingress. I look at my ingress in my cluster and it seems that I’m still at the v1beta
? Something I didn’t do correclty?brainy-appointment-20633
11/24/2021, 5:09 PMminiature-leather-70472
11/26/2021, 3:08 PMmost-lighter-95902
11/27/2021, 3:17 AMpulumi up
is run twice in a row with `k8s.yaml.ConfigFile`:most-lighter-95902
11/27/2021, 3:17 AMconst knativeOperator = new k8s.yaml.ConfigFile(name, {
file: `<https://github.com/knative/operator/releases/download/knative-v${version}/operator.yaml>`,
}, { parent: this })