Anya Sabo

For the first three, that's definitely valid and I tried to address them in the initial issue. My main hesitation with adding it to the ES CRD is the amount...

>I was wondering how we should handle deletion. What if the user wants to delete something ? (creating objects at scale is great, being able to fix a mistake at...

One other extension point I thought of is that adding another field containing query parameters to use only on PUTs might make sense. For instance [component templates](https://www.elastic.co/guide/en/elasticsearch/reference/7.9/indices-component-template.html#put-component-template-api-query-params) have a flag...

In an out of band discussion, we decided to put this approach on pause for the time being. It is feasible, but we would need to add support for specific...

This makes sense to me. It looks like a pod spec with that field will fail admission validation pre-1.13, so I think we'd have to do one of - detect...

Is this just to enable having multiple clusters with different licenses active in the same namespace? Otherwise isn't just using the `--namespaces` flag on the operator sufficient to let people...

What if instead of using annotations, we just allow people to specify label selectors in the operator config? So that way if people wanted they could configure their enterprise ECK...

Just to address your last point, the `maxUnavailable` setting can be tuned to modify that behavior: https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-update-strategy.html