Ralph Ursprung
Ralph Ursprung
i'd strongly suggest to move to using [Semantic Versioning](https://semver.org/spec/v2.0.0.html) for this repository to make it easier for consumers to use it. e.g. somewhere between 0.5.1 and 0.5.5 (presumably with 0.5.5...
it seems that currently optional features (`chrono` & `aq_unstable` at this time) are not being tested by the CI workflow. i'd suggest adding a [build matrix](https://docs.github.com/en/actions/using-workflows/about-workflows#using-a-matrix) which covers also these...
with this consumers get a guarantee for which rustc versions will work. previously (up to at least version 0.5.1) it was possible to build this library with rustc 1.42.0, now...
do you have a roadmap to releasing a v1.0.0? it would be cool if you could create the tickets for what you think is missing for v1.0.0 and assign them...
i admittedly haven't tried the operator yet, but based on the code it seems that it does everything with an admin user from the internal user realm (using basic auth...
coming from this comment thread: https://github.com/Opster/opensearch-k8s-operator/pull/157#discussion_r884127121 instead of documenting how RAM settings for the JVM can be manually set they should instead be set by default - and as percentage...
it'd be great if there'd be the option for the OpenSearch operator to use [cert-manager](https://cert-manager.io/) to get the TLS certificates. that way, neither manual management of the certificates for OpenSearch...
currently neither the README nor the release notes (on GitHub) list the versions of OpenSearch and OpenSearch Dashboards which are supported by this version of the operator. it'd be great...
there are various security plugins available for elasticsearch (x-pack, SearchGuard and OpenDistro being the most well known). is there any documentation on how to use elasticsearch-prometheus-exporter in combination with them?...
**Describe the bug** stumbled across this by chance, the comment claims that this should've been removed with ES 7.0 (which obviously didn't happen if it was still present in 7.10.2...