Fission tries to change ValidatingWebhookConfiguration on microk8s

[henrysachs]

Fission/Kubernetes version

$ fission version
$ kubectl version

Kubernetes Version: v1.26.6

Kubernetes platform (e.g. Google Kubernetes Engine)

Microk8s (self hosted)

Describe the bug

when trying to install fission on microk8s via helm i get the following error:

  ********************
        Release was not present in Helm.  Diff will show entire contents as new.
  ********************
  Error: Failed to render chart: exit status 1: Error: rendered manifests contain a resource that already exists. Unable to continue with install: ValidatingWebhookConfiguration "validating-webhook-configuration" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "fission"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "fission"

I'm using the default values and haven't changed anything until now.

To Reproduce

Install microk8s with metallb on a linux VM

Expected result

fission creates its own ValidatingWebhookConfiguration (probably)

Actual result

helm can't install until the corresponding annotations and labels are set

Screenshots/Dump file

$ fission support dump

Additional context

[henrysachs]

after adding the annotations i receive:

error creating resource: Internal error occurred: failed calling webhook "venvironment.fission.io": failed to call webhook: Post "https://webhook-service.fission.svc:443/validate-fission-io-v1-environment?timeout=10s": x509: certificate signed by unknown authority

and everytime i invoke helm the certs change is this intended?

[henrysachs]

fission-dump_1690197718.zip
here is a dump that i was able to create after setting the annotations

[henrysachs]

so I had cert manager installed anyway and switch to it, after that and setting the annotations the environment creation works :)

[henrysachs]

okay so I was wrong on this. With this config its only possible to issue the same command about 3 times and one of the times it works the other times fail with the above error

[robert-cronin]

Any update on this one? I am encountering the same issue with MetalLB