kyverno [BUG] Deploying via helm with custom release name fails webhook config Go

@hans-d - thanks for filing the issue. We'll investigate it and keep you posted.

1

Answered Jun 11 '21 at 19:46

realshuting

Hi @hans-d this is usually because you have a different deployment name than kyverno , we don’t allow custom deployment name. currently, We set webhookconfig’s owner to Kyverno deployment:

  ownerReferences:
  - apiVersion: extensions/v1beta1
    kind: Deployment
    name: kyverno
    uid: uid

1

Answered Jun 15 '21 at 09:18

vyankyGH

With helmfiles it's quite common do have some release name. In this case, by setting the KYVERNO_DEPLOYMENT in the dpeloyment it should work. Otherwise the helm templates should be adjusted to use a fixed name instead of the release name.

1

Answered Jun 15 '21 at 14:53

hans-d

With helmfiles it's quite common do have some release name. In this case, by setting the KYVERNO_DEPLOYMENT in the dpeloyment it should work. Otherwise the helm templates should be adjusted to use a fixed name instead of the release name.

I agree with that. Since we don't allow custom name of the Deployment, we should change the Helm templates using the fixed name. Would you be interested in contributing a PR?

And can you please log a separate issue to make this name configurable? I recall there were users asking for this feature as well. We'll have to check what needs to be changed in order to get this work.

1

Answered Jun 15 '21 at 21:50

realshuting

Can we get this issue re-opened please? It's not yet fixed.

(cc @NoSkillGirl)

1

Answered Jun 28 '21 at 07:07

MarcusNoble