8000 Chartify renders objects with incorrect apiVersion · Issue #1864 · roboll/helmfile · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content < 8000 /span>
Chartify renders objects with incorrect apiVersion #1864
Closed
@alexgaganov

Description

@alexgaganov

Hey guys,

Just another issue I've noticed with Chartify and Helmfile: while trying to install prometheus-community/kube-prometheus-stack chart with Helmfile and setting forceNamespace key in my helmfile.yaml, the Ingress object is generated with apiVersion: networking.k8s.io/v1 which is not supported by our current K8s version. So it seems that the logic in kube-prometheus-stack.ingress.apiVersion helper function is just ignored.

And then, when I'm trying to do, for example, helmfile diff I get the following error:

error: unable to recognize "/var/folders/km/x2g0dhc17mn7sb5czxsmz3gw0000gp/T/chartify134751137/arn:aws:eks:eu-west-1:XXX:cluster/XXX/monitoring/prometheus-operator-ec2/kube-prometheus-stack/files/templates/prometheus/ingress.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1"

However, once I remove the forceNamespace, everything is working just fine.

Could you please assist?

How to reproduce: basically the configurations are the same as I described in #1857, but the cluster version should be the one that doesn't support the networking.k8s.io/v1 API version yet(in our case it's 1.18, which only supports networking.k8s.io/v1beta1).

K8s version: 1.18
Helm version: 3.5.4
Helmfile version: 0.139.7

Thanks a lot,

Alex.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0