Implement ".spec.image" about etcd-operator HOT 3 CLOSED

I suggest before accept PR #63 move key image under podSpec.

from etcd-operator.

Agree with @AlexGluck that two keys would be too much. From the other point of view - podSpec is redundant for us. And we can just use the subset of keys from there like affinity, tolerations etc., which are important and should be customisable by the end user. But it will lead to massive work for preparing our own version of spec. Or otherwise we can just use podSpec and fill the proper spec fields by admission controller. So effectively taking spec.image and putting it into proper place of podSpec.

Why do I so insist on using spec.image? Because it is obviuos that it is much more important and more frequent to be changed than other fields from podSpec. So logically it should as close to the root key spec as possible.

from etcd-operator.

For now we have 2 options about field placement:

• spec.image
• spec.podSpec.image

We will decide it with community vote in https://t.me/etcd_operator/4054 and comment decision here

from etcd-operator.