Make an option to create PDB for cluster about etcd-operator HOT 6 CLOSED

Shouldn't it be created automatically?

from etcd-operator.

Should we focus on the alpha2 version of the specification and stop expanding alpha1? Writing and rewriting code can be uncomfortable for developers.

from etcd-operator.

@AlexGluck We need to create next API version only in case if some field get removed or renamed

from etcd-operator.

@AlexGluck Creating next api version will force us to update both old and new CRD leading to even more uncomfortable development :)

See kubebuilder docs

In Kubernetes, all versions must be safely round-tripable through each other. This means that if we convert from version 1 to version 2, and then back to version 1, we must not lose information. Thus, any change we make to our API must be compatible with whatever we supported in v1, and also need to make sure anything we add in v2 is supported in v1. In some cases, this means we need to add new fields to v1, but in our case, we won’t have to, since we’re not adding new functionality.

from etcd-operator.

While we don't accepted PR #63 we can be on time move key.

from etcd-operator.

For now we can use this specification #62 (comment) for PDB and extend it later if required

from etcd-operator.