helm inflator kustomize not same result as helm install

[wibed]

kustomize's helm chart inflator does not correctly infer values set from the values.yaml

the following:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: cert-manager

helmGlobals:
  chartHome: ../../../base/cert-manager

helmCharts:
- name: cert-manager
  includeCRDs: true
  releaseName: cluster0
  valuesInline:
    namespace: cert-manager
  repo: https://charts.jetstack.io/

does not have the same effect as:

helm install \                                                                             
  cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --create-namespace \
  --version v1.8.2 \
  --includeCRDs=true

the second works, the first does result in the following error:

E0709 15:02:18.865017       1 leaderelection.go:330] error retrieving resource lock kube-system/cert-manager-cainjector-leader-election: leases.coordination.k8s.io "cert-manager-cainjector-leader-election" is forbidden: User "system:serviceaccount:cert-manager:cluster0-cert-manager-cainjector" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "kube-system"

/kind bug

[Alegrowin]

I came across the exact same thing, this issue is caused by kustomize.

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: cert-manager

will replace all resource namespace to cert-manager.

in ./base/charts/cert-manager/templates/rbac.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: {{ include "cert-manager.fullname" . }}:leaderelection
  namespace: {{ .Values.global.leaderElection.namespace }}

This should be deployed to kube-system namespace instead of cert-manager.

Try comment/remove the namespace from kustomization.yaml

[wibed]

youre right.
it works fine, but i cannot determine the namespace the resources are created.

even though is set the values as follows:

  valuesInline:
    namespace: cert-manager
    clusterResourceNamespace: cert-manager

they are created in the namespace default
a related issue:
kubernetes-sigs/kustomize#3815

have you find a way to work around this problem?

[wibed]

Duplicate of kubernetes-sigs/kustomize#4593

/close