Errors during deployment about jitsi-deployment HOT 9 OPEN

Still nobody found the solution? I think I have a progress, Jitsi still doesn't work though.

I've just install Metacontroller using instruction on the following page:
https://docs.primehub.io/docs/getting_started/install_metacontroller

Then I don't see the STDIN error anymore but all the pending service still doesn't change.

from jitsi-deployment.

Everything goes well.I have deployed in AKS.

@sunilkumarjena21 How did you manage to resolve the following error:

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

Any update will be appreciated

From my research the built-in service-per-pod DecoratorController has been deprecated in favor of metacontroller's package:

DEPR: https://github.com/GoogleCloudPlatform/metacontroller/tree/master/examples/service-per-pod
NEW: https://github.com/metacontroller/metacontroller/tree/master/examples/service-per-pod

from jitsi-deployment.

Got same problem during deployment.

Do you have fix guys, it would be very helpful. @simoncolincap @janrenz @mvakert @wolfm89

unable to recognize "STDIN": no matches for kind "Certificate" in version "cert-manager.io/v1alpha2"
unable to recognize "STDIN": no matches for kind "ClusterIssuer" in version "cert-manager.io/v1alpha2"
unable to recognize "STDIN": no matches for kind "Elasticsearch" in version "elasticsearch.k8s.elastic.co/v1"
unable to recognize "STDIN": no matches for kind "Kibana" in version "kibana.k8s.elastic.co/v1"
unable to recognize "STDIN": no matches for kind "DecoratorController" in version "metacontroller.k8s.io/v1alpha1"
unable to recognize "STDIN": no matches for kind "DecoratorController" in version "metacontroller.k8s.io/v1alpha1"
unable to recognize "STDIN": no matches for kind "DecoratorController" in version "metacontroller.k8s.io/v1alpha1"
unable to recognize "STDIN": no matches for kind "DecoratorController" in version "metacontroller.k8s.io/v1alpha1"
unable to recognize "STDIN": no matches for kind "Alertmanager" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "PodMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "PodMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "PodMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"

from jitsi-deployment.

Hello @simoncolincap @janrenz @mvakert @wolfm89@pgabriela

Everything goes well.I have deployed in AKS.

@pgabriela @debendraoli Did you guys figured out how to access the jitsi frontend ?

For your information, I have also replaced the placeholders for the base64 credentials in

/overlays/production/ops/bbb-basic-auth-secret.yaml
/base/jitsi/jitsi-secret.yaml

Swift response will be life saver..

Thanks in advance!

from jitsi-deployment.

@tonezzz I have a question. Are you using latest jitsi docker images? Moving this setup to use websocket is pain :( . I'm trying from last couple of weeks and still no progress.
for Metacontroller, I have created a directory metacontroller in base/ops and put all the files present here in the directory. Also added directory name to base/ops/kustomization.yaml file.

from jitsi-deployment.

@prayagsingh.

I'm just a beginner in Git, Jitsi, Docker, and Kubernetes so pls give me advice if there's anything I should check (and perhaps also provide instructions & explanations).

I think yes, all scripts & images I'm using should be the latest, coz I've just restarted from scratch before I posted the reply. And I only use the instruction from this Repository,

I also thought if I had to download and add the metacontroller files but I don't understand a thing, I've just got lucky I found an instruction to install it, and the error log disappeared so I think this might help someone to overcome the current issue and make more progress.

from jitsi-deployment.

Hello @simoncolincap @janrenz @mvakert @wolfm89@pgabriela

Everything goes well.I have deployed in AKS.

@pgabriela @debendraoli Did you guys figured out how to access the jitsi frontend ?

For your information, I have also replaced the placeholders for the base64 credentials in

/overlays/production/ops/bbb-basic-auth-secret.yaml
/base/jitsi/jitsi-secret.yaml

Swift response will be life saver..

Thanks in advance!

@sunilkumarjena21 Would it be possible to share your EKS setup and how you were able to deploy to Amazon EKS?

from jitsi-deployment.

@pgabriela @debendraoli Did you guys figured out how to access the jitsi frontend ?

The ingress haproxy ngx returns 404

Did you manage to access the fronted ? How did you do it?

from jitsi-deployment.

I'm sorry, I managed to setup using my own config on eks.

from jitsi-deployment.