unable to recognize "STDIN": no matches for kind "DecoratorController"

[r3k2]

Hello, I am having some problems trying to get this setup on digital ocean, I have so far fixed some issues already but another ones are giving me a hard time like this one below:

unable to recognize "STDIN": no matches for kind "DecoratorController" in version "metacontroller.k8s.io/v1alpha1"

Also, I have some questions…
Can we use a nginx-ingress, or does it have to be ha-proxy? Digital ocean already provide load balancers, I had a simple toy setup of Jitsi working fine, with a nginx-ingress but only one jvb, but we want this to be able to autoscale, so we have seen this project as a perfect for us, maybe overkill with all the Kibana/monitoring, but this is ok.
The doc in this site does not really say what we can modify on the overlays or not, also the passwords and other configs that can change are on the "base" not on the overlays, will be nice to be able to just pull base from a URL to this repo so it keeps in sync instead of having to keep updating etc.
Any ideas on what can be wrote with that error above? thanks

[cgustav]

The answer comes a little late, but I hope it still helps someone.

The documentation is a bit confusing about this issue as the metacontroller maintainers have migrated their official repositories from google dependencies to their own repos.

The problem comes from the fact that for some reason the repository does not have all the base resources (like role bindings, statefulsets, etc) for metacontroller to create properly the Kubernete's CustomResourceDefinition components (in this case they are used to define the service-per-pod-controller mechanisms to scale JVB instances.

To fix this you should run the following commands before deploy any Jitsi resources on your cluster:

# Install Metacontroller custom resources
# https://docs.primehub.io/docs/getting_started/install_metacontroller
# These custom resources supports the creation of custom controllers
# for JVB services (service-per-pod-controller).

kubectl apply -f https://raw.githubusercontent.com/metacontroller/metacontroller/master/manifests/production/metacontroller-namespace.yaml
kubectl apply -f https://raw.githubusercontent.com/metacontroller/metacontroller/master/manifests/production/metacontroller-rbac.yaml
kubectl apply -f https://raw.githubusercontent.com/metacontroller/metacontroller/master/manifests/production/metacontroller-crds-v1.yaml
kubectl apply -f https://raw.githubusercontent.com/metacontroller/metacontroller/master/manifests/production/metacontroller.yaml

Finally you can check if all metacontroller dependencies were successfully inside your cluster executing:

kubectl get crd | grep metacontroller

Then you should get something like this if everything is ok:

compositecontrollers.metacontroller.k8s.io   2023-06-16T18:33:35Z
controllerrevisions.metacontroller.k8s.io    2023-06-16T18:33:36Z
decoratorcontrollers.metacontroller.k8s.io   2023-06-16T18:33:37Z

Then deploy your Jitsi resources:

namespace/jitsi created
configmap/jvb-entrypoint created
configmap/jvb-shutdown created
configmap/prosody created
configmap/web created
secret/jitsi-config created
service/shard-0-prosody created
service/shard-1-prosody created
service/web created
deployment.apps/shard-0-jicofo created
deployment.apps/shard-0-prosody created
deployment.apps/shard-0-web created
deployment.apps/shard-1-jicofo created
deployment.apps/shard-1-prosody created
deployment.apps/shard-1-web created
horizontalpodautoscaler.autoscaling/shard-0-jvb-hpa created
horizontalpodautoscaler.autoscaling/shard-1-jvb-hpa created
decoratorcontroller.metacontroller.k8s.io/shard-0-pod-name-label created
decoratorcontroller.metacontroller.k8s.io/shard-0-service-per-pod created
decoratorcontroller.metacontroller.k8s.io/shard-1-pod-name-label created
decoratorcontroller.metacontroller.k8s.io/shard-1-service-per-pod created
(...)

Cheers!