Hey @justinsb
We've slightly touched that topic on kubecon in Barcelona.
First of all I much appreciate all your (authors and collaborators) hard work in these exceptional projects.
My current k8s@aws v1.12 was build by kops 1.11 using normal official etcd image of v3.2.26
Now kops 1.12 is released and has all the etcd versions hardcoded.
Curious if there is way we can have our official images and versions chosen during kops/etcdmanager setup?
IMHO such hard-coding adds excess maintenance.
Whole community will depend on contributors will and free-time.
It's GO code and not end-user-friendly YAML.
Also this commit:
justinsb committed 12 days ago Support etcd 3.3.10 (May 16, 2019)
Any specific reason why not 3.3.13, or anything else after 3.3.10 ?
lawrencedudley
commented
5 years ago
Hey @justinsb We've slightly touched that topic on kubecon in Barcelona. First of all I much appreciate all your (authors and collaborators) hard work in these exceptional projects.
My current k8s@aws v1.12 was build by kops 1.11 using normal official etcd image of v3.2.26 Now kops 1.12 is released and has all the etcd versions hardcoded.
Curious if there is way we can have our official images and versions chosen during kops/etcdmanager setup?
IMHO such hard-coding adds excess maintenance. Whole community will depend on contributors will and free-time. It's GO code and not end-user-friendly YAML.
Also this commit:
Any specific reason why not 3.3.13, or anything else after 3.3.10 ?
Related issue from kops repo https://github.com/kubernetes/kops/issues/6756