read volatile etcd parameters from the cluster spec

[andmat900]

Applicable Issues

Description of the Change

This change adds the possibility to set volatile etcd parameters like image version, resource usage in the cluster spec.

Alternate Designs

Possible Drawbacks

Sign-off

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or

(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or

(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.

(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

Signed-off-by: Andrei Matveyeu, andrei.matveyeu@axis.com

[t-persson]

Only happened to glance at this. Probably wont read any updates to this pr.

[t-persson]

If we really need to add these, then they should use the same parameters that can be found in the statefulset spec so that the parameters look and feel the same.

[andmat900]

Updated. The resources element is now identical to statefulset spec. Example:

  database:
    deploy: true
    etcd:
      image: "quay.io/coreos/etcd:v3.5.19"
      resources:
        limits:
          memory: "512Mi"
          cpu: "200m"
        requests:
          memory: "512Mi"
          cpu: "200m"