Hi! Have you encountered errors like the one below...
# kubernetes
n
Hi! Have you encountered errors like the one below when executing
pulumi up
? They occur sporadically, approximately in 1 out of every 3 attempts. Given that I'm managing several charts in my stack, it's unlikely that I can successfully run
pulumi up
on my first try. I often need to attempt it multiple times before all resources are updated successfully.
Copy code
Diagnostics:
  kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> (ingress-nginx-helm):
    error: kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> resource 'ingress-nginx-helm': property chart value {ingress-nginx} has a problem: Get "<https://github.com/kubernetes/ingress-nginx/releases/download/helm-chart-4.9.1/ingress-nginx-4.9.1.tgz>": EOF; check the chart name and repository configuration.
Thank you in advance!
Similar error seen:
Copy code
Diagnostics:
  kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> (argocd):
    error: kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> resource 'argocd': property chart value {argo-cd} has a problem: Get "<https://github.com/argoproj/argo-helm/releases/download/argo-cd-6.2.3/argo-cd-6.2.3.tgz>": EOF; check the chart name and repository configuration.
Another error I've seen sporadically:
Copy code
FetchError: request to <https://github.com/cert-manager/cert-manager/releases/download/v1.14.3/cert-manager.crds.yaml> failed, reason: Client network socket disconnected before secure TLS connection was established
d
I'd be curious to know whether the
helm
tool sees sporadic errors in your environment.
n
Never seen one, helm CLI has been been working consistently.
I've seen issues not just with helm, e.g. my last example shows how k8s.yaml.ConfigFile failed, this is how I was using it:
Copy code
const certManagerCRDs = new k8s.yaml.ConfigFile(
    "cert-manager-crds",
    {
      file: `<https://github.com/cert-manager/cert-manager/releases/download/v${certManagerVersion}/cert-manager.crds.yaml>`,
    },
    {
      provider: provider,
    },
  );
It almost looks like it's having issues connecting to GitHub, which is something I have never experienced with my Internet connection, at least that I know - maybe clients are performing retries without my knowledge.