busy-soccer-65968
11/19/2020, 11:04 PMhelm.v3.Chart
and wondering if i'm missing something. i'm using latest`2.7.2` kubernetes npm package. This is typescript project.
The problem is around the values
property.
Essentially when I deploy the helm chart from scratch. All customized values
work as expected. However, when I change any of those values AFTER the initial deploy pulumi doesn't seem to notice any difference. What I've done in the past is simply comment out the helm chart, run pulumi update (to delete it), and redeploy with new values. However, I cannot do this because it is our ingress controller.
Other properties namespace, version, transformations
all seem to pick up differences. The issue seems to be strictly related to the values
property.
Is there anyway to have pulumi recognize the change in values
without having to manually delete/replace the helm chart? Let me know if I can make this any more clear 🙏 .~white-orange-65913
11/20/2020, 12:17 PMadamant-translator-31969
11/20/2020, 3:12 PMbitter-application-91815
11/23/2020, 6:52 PMbitter-application-91815
11/23/2020, 6:53 PMsparse-gold-89283
11/24/2020, 4:55 PMbreezy-cricket-40277
11/26/2020, 2:29 PMkubernetes
provider to fetch a secret
from a kubernetes cluster provider, if the secret itself is not created by pulumi?adamant-translator-31969
11/28/2020, 7:08 PMrich-library-94587
11/30/2020, 1:19 PMcolossal-australia-65039
12/01/2020, 1:27 AMup
. For example, I move an ingress
to a different namespace but get an error because it has the same host as the "existing" one. How can I handle these to ensure there is no conflict when I run up
?big-potato-91793
12/03/2020, 1:34 PMbig-potato-91793
12/03/2020, 1:34 PMbored-river-53178
12/03/2020, 11:10 PMNo matching service found for ingress rule: "freepbx.taskrouter.dev.internal/" -> ""
and can't understand why the service name is empty, the service is present and everything works fine besides this pulumi check which leads to a failed deploymentbored-river-53178
12/03/2020, 11:48 PMapiVersion: extensions/v1beta1
to apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
in the ingress definition seemed to solve the issuebored-river-53178
12/03/2020, 11:49 PMbored-river-53178
12/04/2020, 12:07 AMicy-jordan-58549
12/04/2020, 4:07 PMerror: resource kube-system/coredns-custom was not successfully created by the Kubernetes API server : configmaps "coredns-custom" already exists
icy-jordan-58549
12/07/2020, 3:01 PMkubectl apply -f
If resource exists, replace it or create. Thankscolossal-australia-65039
12/07/2020, 10:22 PMroleMappings[*].groups
property somehow. Neither the name of the clusterrole or binding work here (something like system:masters
does work though). Anyone know how i can achieve this?icy-jordan-58549
12/08/2020, 4:44 PMoperator (statefulset)
and when service
resource has been created, I am trying to get it using something like this:
const kc = new k8sClient.KubeConfig();
const watcher = config.servicesK8s.cluster.kubeconfig
.apply(kubeConfig => kc.loadFromString(kubeConfig))
.apply(() => new k8sClient.Watch(kc));
export let serviceName = watcher.apply(w => waitFor(w, 'elastic-es-http'));
export const service = pulumi
.all([namespace.metadata.name, serviceName])
.apply(([ns, name]) =>
k8s.core.v1.Service.get('elastic-svc', `${ns}/${name}`, {
parent: namespace,
dependsOn: [elasticsearch]
})
);
bitter-application-91815
12/10/2020, 7:26 PMbitter-application-91815
12/10/2020, 7:41 PMsteep-angle-29984
12/14/2020, 5:59 PMclever-byte-21551
12/15/2020, 7:21 AMpulumi-kubernetes
to a more up-to-date version. But my stack wasn’t able to refresh if I didn’t have the old plugin version existing on the machine (I’m running in container so I only have the recent plugin version)
Other pulumi provider have this behaviour and I was wondering if this is a bug
Diagnostics:
pulumi:providers:kubernetes (default_2_6_1):
error: no resource plugin 'kubernetes-v2.6.1' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource kubernetes v2.6.1`
(I was upgrading from 2.6.1 to 2.6.3)prehistoric-kite-30979
12/17/2020, 4:49 PMfunc New(ctx *pulumi.Context, options ...pulumi.ResourceOption) error {
_, err := kustomize.NewDirectory(ctx, "vault", kustomize.DirectoryArgs{
Directory: pulumi.String("./kustomize"),
})
return err
}
It appears that local directories are always relative to the main.go, not the library. I think my only option here is to do a full import into Pulumi, right?proud-pizza-80589
12/18/2020, 8:34 AMred-area-47037
12/18/2020, 6:39 PMkubernetes:<http://apiextensions.k8s.io/v1:CustomResourceDefinition|apiextensions.k8s.io/v1:CustomResourceDefinition> (<http://certificates.cert-manager.io|certificates.cert-manager.io>):
error: 1 error occurred:
* the Kubernetes API server reported that "<http://certificates.cert-manager.io|certificates.cert-manager.io>" failed to fully initialize or become live: "" is invalid: patch: Invalid value: ......." : cannot convert int64 to float64
proud-pizza-80589
12/21/2020, 9:51 AMbland-lamp-16797
12/22/2020, 10:47 AM<http://kubernetes-charts.storage.googleapis.com|kubernetes-charts.storage.googleapis.com>
check this blog post:
https://helm.sh/blog/new-location-stable-incubator-charts/rough-oxygen-8318
12/23/2020, 3:53 AMmonkey patch
kubernetes resources that were not created with Pulumi? My use case is: Adding the environment variable AWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG=true
for DaemonSet aws-node
inside an AWS EKS Cluster (Step 3 in custom-networking AWS Documentation https://docs.aws.amazon.com/eks/latest/userguide/cni-custom-network.html)rough-oxygen-8318
12/23/2020, 3:53 AMmonkey patch
kubernetes resources that were not created with Pulumi? My use case is: Adding the environment variable AWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG=true
for DaemonSet aws-node
inside an AWS EKS Cluster (Step 3 in custom-networking AWS Documentation https://docs.aws.amazon.com/eks/latest/userguide/cni-custom-network.html)prehistoric-kite-30979
12/23/2020, 10:42 AMrough-oxygen-8318
12/23/2020, 5:39 PMaws-node
installation (ClusterRole, ClusterRoleBinding, ServiceAccount, etc)
• I found an official helm repo with multiple EKS related charts. I'm going to use pulumi + helm to install the aws-vpc-cni
(a.k.a aws-node
) chart. I hope using this installation method give me more flexibility for future upgrades.