You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to reproduce it (as minimally and precisely as possible):
❯ kubectl apply -n open-match -f https://open-match.dev/install/v1.4.0-rc.1/yaml/03-prometheus-chart.yaml
serviceaccount/open-match-prometheus-alertmanager created
serviceaccount/open-match-prometheus-kube-state-metrics created
serviceaccount/open-match-prometheus-node-exporter created
serviceaccount/open-match-prometheus-pushgateway created
serviceaccount/open-match-prometheus-server created
configmap/open-match-prometheus-alertmanager created
configmap/open-match-prometheus-server created
persistentvolumeclaim/open-match-prometheus-alertmanager created
persistentvolumeclaim/open-match-prometheus-server created
Warning: rbac.authorization.k8s.io/v1beta1 ClusterRole is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRole
clusterrole.rbac.authorization.k8s.io/open-match-prometheus-kube-state-metrics created
clusterrole.rbac.authorization.k8s.io/open-match-prometheus-server created
Warning: rbac.authorization.k8s.io/v1beta1 ClusterRoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRoleBinding
clusterrolebinding.rbac.authorization.k8s.io/open-match-prometheus-kube-state-metrics created
clusterrolebinding.rbac.authorization.k8s.io/open-match-prometheus-server created
service/open-match-prometheus-alertmanager created
service/open-match-prometheus-kube-state-metrics created
service/open-match-prometheus-node-exporter created
service/open-match-prometheus-pushgateway created
service/open-match-prometheus-server created
service/open-match-swaggerui created
deployment.apps/open-match-swaggerui created
unable to recognize "https://open-match.dev/install/v1.4.0-rc.1/yaml/03-prometheus-chart.yaml": no matches forkind "DaemonSet"in version "extensions/v1beta1"
unable to recognize "https://open-match.dev/install/v1.4.0-rc.1/yaml/03-prometheus-chart.yaml": no matches forkind "Deployment"in version "extensions/v1beta1"
unable to recognize "https://open-match.dev/install/v1.4.0-rc.1/yaml/03-prometheus-chart.yaml": no matches forkind "Deployment"in version "extensions/v1beta1"
unable to recognize "https://open-match.dev/install/v1.4.0-rc.1/yaml/03-prometheus-chart.yaml": no matches forkind "Deployment"in version "extensions/v1beta1"
unable to recognize "https://open-match.dev/install/v1.4.0-rc.1/yaml/03-prometheus-chart.yaml": no matches forkind "Deployment"in version "extensions/v1beta1"
Anything else we need to know?:
downloading 03-prometheus-chart.yaml and replacing externsions/v1beta1 with apps/v1 for the DaemonSet and Deployments makes it apply successfully.
Output of kubectl version:
❯ kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.5", GitCommit:"c285e781331a3785a7f436042c65c5641ce8a9e9", GitTreeState:"clean", BuildDate:"2022-03-16T15:51:05Z", GoVersion:"go1.17.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.11-eks-f17b81", GitCommit:"f17b810c9e5a82200d28b6210b458497ddfcf31b", GitTreeState:"clean", BuildDate:"2021-10-15T21:46:21Z", GoVersion:"go1.15.15", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.23) and server (1.20) exceeds the supported minor version skew of +/-1
What happened:
tried to install prometheus with kubectl
What you expected to happen:
it should succeed
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
downloading 03-prometheus-chart.yaml and replacing externsions/v1beta1 with apps/v1 for the DaemonSet and Deployments makes it apply successfully.
Output of
kubectl version
:Cloud Provider/Platform (AKS, GKE, Minikube etc.): AWS
Open Match Release Version:
v1.4.0-rc.1
Install Method(yaml/helm):: yaml, but helm fails with a similar error as noted in #1393
The text was updated successfully, but these errors were encountered: