-
Notifications
You must be signed in to change notification settings - Fork 133
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
example-etcd-cluster not created #6
Comments
same for
using minikube version: the versions I use also have changes for but @joshix @jdob will you update the example for later versions of the k8s-api ? |
ok, I fixed the validation by using this schema (which has become required in
now one pod is tries to start:
but the init-container throws:
|
@joshix @jdob Thoughts above? I spent about 2 hours researching this, and it seems that:
Is there any fix? Or is the book's demo (chapter 3) largely stale now too? I am excited about the book, but this start is worrying. |
Same problem here on Kind cluster (kind v0.16.0 go1.19.1 darwin/arm64)
|
The order of applying the manifests is just wrong.
After that, you will have something like:
But it will fail, unless you have provided Docker credentials into your Kubernetes Cluster.
NOTE: I did not read the book yet, but I consider to read it and I just check that repo. |
Hi there, I tested the etcd cluster example in 2023 on k8s 1.24, and the example seems to be completely outdated. The cluster does not start; it endlessly waits for the DNS config to be created.
Here is what I did (tested on both minikube and kind, with the same results):
The result:
The reason is pointed out by @seanw2020 : the book depends on the stale etcd-operator repo and the issue is known but remains unresolved. I'm not sure if the book maintainers have plans to fix that example. For now, I would recommend skipping the 'Running operators' chapter. Despite being somewhat outdated, the book is still highly interesting. |
upon running oc create -f etcd-cluster-cr.yaml the example-etcd-cluster-* pods are not created
The text was updated successfully, but these errors were encountered: