-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
manifests/0prometheus-operator-0alertmanagerCustomResourceDefinition.yaml cannot be validated #2034
Comments
Can you please elaborate on this?
Thanks. |
Running The validation-thing is the one most concerning for me though. |
Sorry for taking so long, but I realized you apply the bundle and then the entire stack again. The bundle is just for a quickstart. The kube-prometheus stack is the entire stack, the bundle is a subset of kube-prometheus, as you seem to want the whole stack, just apply the latter 🙂 . (fwiw I just tried and successfully deployed the whole stack on a new cluster without any issues) |
@brancz i am also getting this with the latest version of kube prometheus
Please suggest why do we get this? |
I am unable to reproduce this with a minikube cluster. Do you have any steps for reproducing your cluster that yields this? |
brancz, Now it is me who has to apologize for being late. -.- echo 1 > /proc/sys/net/ipv4/ip_forward It is for a single node "cluster" but since the configuration-file is not understood by Kubernetes I think the fact that there are no minions does not matter. |
@asodastreamer I was able to reproduce this on minikube when I explicitely install Please install the same version of kubectl as your server has to have the strongest conversion guarantee. |
@alok87 do you mind to also verify if bumping your |
I got the same issue with Client Version 1.9.3 and Server Version 1.11.5. As @s-urbaniak suggested, it is solved by installing the same version of kubectl as my server. |
I'm closing this as we have multiple reports of @s-urbaniak's answer being correct. Should this not be the case for you and the problem continues to exist, please comment here or open a new issue. Thanks! |
What did you do?
I got the project via "go get" and also via "git clone".
Executing
kubectl create -f bundle.yaml
and thenkubectl create -f contrib/kubernetes-prometheus/manifests
What did you expect to see?
A flawless deploy.
What did you see instead? Under which circumstances?
In both cases I saw errors being raised.
The yml-files appear to be recreating state already present elsewhere and not all of them can be validated.
Operator-Version
git rev-parse HEAD
-> d0cf2eeas well as
git rev-parse HEAD
-> 4a7fea5(which is tag v0.24.0)
Clusterinfo
Client Version: version.Info{Major:"", Minor:"", GitVersion:"v1.9.3,", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"archive", BuildDate:"2018-06-02T04:44:09Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:08:19Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Kubernetes cluster kind:
kubeadm init
Manifests:
no relevant logs for this issue
The text was updated successfully, but these errors were encountered: