jetstack-experimental / pilot-elasticsearch Goto Github PK

At the moment, upon node pool deletion we will not detect a scale down event and trigger shards to be relocated.

In future, this will likely be determined by the navigator-apiserver (ref jetstack/navigator#8) but in the meantime we should handle this gracefully.

Currently, the elasticsearch.yml configuration file is built into the base image. This is completely non-customisable without a rebuild of the base image.

We should allow users to specify their configuration within the ThirdPartyResource, or in future helm definition.

Right now, in order to determine what actions to take or events have been fired (see hooks and events packages), we directly query the Kubernetes API.

In order to support alternative environments, we need to identify where we query this API, why we query it, and then provide an abstraction for that functionality via the TBC 'navigator-apiserver'.

Once we've refactored out all queries to the Kubernetes API, we should be able to run Pilots in any environment supported by the navigator-apiserver.