Git Product home page Git Product logo

Comments (4)

r3k2 avatar r3k2 commented on August 9, 2024 1

same here. how do we install this add-on? do we need to run this before we run your kustomize yaml files?

kubectl apply -k https://github.com/metacontroller/metacontroller/manifests/production

from jitsi-deployment.

cgustav avatar cgustav commented on August 9, 2024 1

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

You should also get rid of any metacontroller namespace definitions within the repo to avoid breaking the metacontroller resources you have previously installed and manage this whole process in a specific script to prepare your cluster to deploy Jitsi's resources.

Expected output after deploying Jitsi:

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
(...)

NOTE: As @kachar said you should use this installation guide (do not consider GoogleCloudPlatform/metacontroller documentation in this regard) : https://metacontroller.github.io/metacontroller/guide/install.html

NOTE2: Command shared by @r3k2 work in a more efficient way:

kubectl apply -k https://github.com/metacontroller/metacontroller/manifests/production

Cheers!

from jitsi-deployment.

kachar avatar kachar commented on August 9, 2024

@uvwild metacontroller actually is being included here https://github.com/hpi-schul-cloud/jitsi-deployment/tree/master/base/ops/metacontroller

The ops/ folder is included only in the development-monitoring and production-monitoring overlays.

Keep in mind that the GoogleCloudPlatform/metacontroller repo has been deprecated in favor of the dedicated https://github.com/metacontroller/metacontroller repo where you can find the latest version.

from jitsi-deployment.

tibby-stanescu avatar tibby-stanescu commented on August 9, 2024

Hello - I am running into the same issue. Do we need to deploy the monitoring components first and then jitsi?

from jitsi-deployment.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.