David J. M. Karlsen

@jonnydawg do you need more info? What can be the cause of this?

@jonnydawg ``` k get mutatingwebhookconfigurations,validatingwebhookconfigurations NAME WEBHOOKS AGE mutatingwebhookconfiguration.admissionregistration.k8s.io/cert-manager-webhook 1 341d mutatingwebhookconfiguration.admissionregistration.k8s.io/inmemorychannel.eventing.knative.dev 1 61d mutatingwebhookconfiguration.admissionregistration.k8s.io/machine-api 2 348d mutatingwebhookconfiguration.admissionregistration.k8s.io/mutating-knative-openshift 2 313d mutatingwebhookconfiguration.admissionregistration.k8s.io/mutating.knativeeventings.operator.serverless.openshift.iozgvc6 1 27d mutatingwebhookconfiguration.admissionregistration.k8s.io/mutating.knativekafkas.operator.serverless.openshift.io-xq4wf 1 27d mutatingwebhookconfiguration.admissionregistration.k8s.io/mutating.knativeservings.operator.serverless.openshift.io-7sj5b 1 27d mutatingwebhookconfiguration.admissionregistration.k8s.io/sinkbindings.webhook.sources.knative.dev...

Cross-linking: https://github.com/helm/charts/issues/19807

@ltkn thanks - I tried building it with `mvn clean install -Pdev9 ` in the root but it fails with: ``` [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project...

Related: https://github.com/jOOQ/jOOQ/issues/10150 and https://groups.google.com/g/jooq-user/c/Bfikrob2tnk

```[INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] sfm-test-sandbox [jar] [INFO] sfm-test-sandbox-csv [jar] [INFO] sfm-test-proto [jar] [INFO] sfm-test-osgi [jar] [INFO] SFM JMH benchmark [jar] [INFO] sfm-parent [pom] [INFO] [INFO] ---------------<...

+1 to all that's said. This project is truly awesome! I could help out terraform a setup (a tf module) to run on AWS, but need to understand the architecture...

``` --- a/manifests/governance/namespace-configurator/rolebindings.yaml +++ /dev/null @@ -1,44 +0,0 @@ -apiVersion: redhatcop.redhat.io/v1alpha1 -kind: NamespaceConfig -metadata: - name: fss-apps -spec: - labelSelector: - matchLabels: - app.kubernetes.io/managed-by: clout - fss.tietoevry.com/legacy-logging: "true" - templates:...

sorry, that's gone by now. I'll reopen a case if I can reproduce.

@raffaelespazzoli found the cause, the finalizers seems to have changed name at some point, leading to having two: ```yaml finalizers: - namespace-config-operator - namespaceconfig-controller ```