question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Helm reads wrong Kubeversion: >=1.22.0-0 for v1.23.0 as v1.20.0

See original GitHub issue

What happened?

Tried adding ArgoCD to Kubernetes cluster on AWS (EKS) using Pulumi Python. But the wrong KubeVersion is read from the requirement.

THE CLUSTER VERSION IS: v1.23.0 verified on AWS. And NOT 1.20.0

ArgoCD install yaml used with CRD2Pulumi: https://raw.githubusercontent.com/argoproj/argo-cd/master/manifests/core-install.yaml

Any ideas as to fixing this oddity between the version error and the actual cluster version?

Steps to reproduce

Try something like the following code (reproducibility verified):

cluster = eks.Cluster("argo-example") # version="1.23"

# Cluster provider
provider = k8s.Provider(
    "eks",
    kubeconfig=cluster.kubeconfig.apply(lambda k: json.dumps(k))
    #kubeconfig=cluster.kubeconfig
)

ns = k8s.core.v1.Namespace(
    'argocd',
    metadata={
        "name": "argocd", 
    },

    opts=pulumi.ResourceOptions( 
        provider=provider
    )
)

argo = k8s.helm.v3.Release(
    "argocd",  
    args=k8s.helm.v3.ReleaseArgs(
        chart="argo-cd",
        namespace=ns.metadata.name,
        repository_opts=k8s.helm.v3.RepositoryOptsArgs(
            repo="https://argoproj.github.io/argo-helm"
        ),
        values={
            "server": {
                "service": {
                    "type": "LoadBalancer",
                }
            }
        },
    ),
    opts=pulumi.ResourceOptions(provider=provider, parent=ns),
)

Expected Behavior

Successfully deploys ArgoCD on the cluster.

Actual Behavior

image

  kubernetes:helm.sh/v3:Release (argocd):
    error: failed to create chart from template: chart requires kubeVersion: >=1.22.0-0 which is incompatible with Kubernetes v1.20.0

Output of pulumi about

No response

Additional context

I’ve tried:

Deleting everything and starting over.
Updating to the latest ArgoCD install yaml.

Contributing

Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you’ve opened one already).

Issue Analytics

  • State:closed
  • Created 10 months ago
  • Reactions:1
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
WP-LKLcommented, Nov 9, 2022

This seems to be an issue with the chart and/or Helm. argoproj/argo-helm#1579 added a kubeVersion requirement, which is failing validation.

Can you try installing that Chart using the helm client directly and see if you get the same error?

You are correct, indeed a new addition to the Argo helm chart.

However, it appears to be working fine using the helm client directly: image

0reactions
WP-LKLcommented, Nov 22, 2022

Great stuff – indeed updating the package requirements solved it!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Helm reads wrong Kubeversion: >=1.22.0-0 for v1.23.0 as ...
So using that version successfully deploys the helm chart. E.g. import * as k8s from "@pulumi/kubernetes"; ...
Read more >
Error: chart requires kubeVersion: < 1.23.0-0 which is ...
Error : chart requires kubeVersion: < 1.23.0-0 which is incompatible with Kubernetes v1.23.0 [bug] #10819.
Read more >
Helm complains about incompatible kubernetes version
Whenever I try helm upgrade longhorn longhorn/longhorn --dry-run I end up ... Error: UPGRADE FAILED: chart requires kubeVersion: >=v1.18.0 ...
Read more >
Deprecated Kubernetes APIs
These API versions would have been announced for deprecation prior to this again. This shows that there is a good policy in place...
Read more >
Customize apiVersion in helm templates - Rene Hernandez
In my case, we ran into this issue with the Ingress resource apiVersion , which in version 1.22 stopped serving extensions/v1beta1 and ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found