Closed kvaps closed 7 months ago
I’ll personally raise the question again whether we should replace:
spec.pod
--> spec.podTemplate
spec.service
--> spec.serviceTemplate
spec.podDisruptionBudget
--> spec.podDisruptionBudgetTemplate
piraeus-operator and elk-operator use it this way
PR rebased after internal discussion to use Template suffixes for configuring Kubernetes entities.
Another advantage of using the Template suffixes is that it serves as a contract to adhere to the Kubernetes specifications.
What we have in storage and options is validated and processed by our logic, and the specifications there are strictly our own. However, what is in *Template follows the Kubernetes specifications and is intuitively understandable.
following up https://github.com/aenix-io/etcd-operator/issues/109#issuecomment-2032847557
Here are examples for: