Skip to content
This repository was archived by the owner on Apr 9, 2025. It is now read-only.

Errors during deployment #23

Description

@pgabriela

I tried to deploy the code (overlays/production) to both Azure AKS and AWS EKS with Fargate. Both resulted in similar errors during deployment like below

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 "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 "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"

Below is the error returned from the server specific to Azure AKS (not sure if this is useful)

{"metadata":{"annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{"apiVersion":"rbac.authorization.k8s.io/v1","kind":"ClusterRoleBinding","metadata":{"annotations":{},"name":"kubernetes-dashboard"},"roleRef":{"apiGroup":"rbac.authorization.k8s.io","kind":"ClusterRole","name":"kubernetes-dashboard"},"subjects":[{"kind":"ServiceAccount","name":"kubernetes-dashboard","namespace":"kubernetes-dashboard"}]}\n"},"labels":null},"roleRef":{"name":"kubernetes-dashboard"},"subjects":[{"kind":"ServiceAccount","name":"kubernetes-dashboard","namespace":"kubernetes-dashboard"}]}
to:
Resource: "rbac.authorization.k8s.io/v1, Resource=clusterrolebindings", GroupVersionKind: "rbac.authorization.k8s.io/v1, Kind=ClusterRoleBinding"
Name: "kubernetes-dashboard", Namespace: ""
for: "STDIN": ClusterRoleBinding.rbac.authorization.k8s.io "kubernetes-dashboard" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"ClusterRole", Name:"kubernetes-dashboard"}: cannot change roleRef

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

Below is the screenshot when I run kubectl get all -n jitsi
ss2

Also, when everything works perfectly, which service is the interface to users that is exposed to the Internet? Is it the web service?
Thank you

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions