Open gbanasiak opened 1 year ago
Good point, however the fact, that ECK components charts are Enterprise feature, I suppose, that a 3rd party/community charts will be born soon to allow full functionality and be free. In my opinion, licensing the charts this way is a mindless move...
As Elastic maintenance of non-ECK Helm charts is drawing to an end (see https://github.com/elastic/helm-charts/issues/1731) there's a group of customers who will migrate from non-ECK to ECK Helm charts. Today there's no full feature parity between non-ECK and ECK Helm charts and one of the missing components is Ingress support.
Non-ECK Helm charts include Ingress templates for APM server, Elasticsearch, Kibana and Logstash. Leaving Logstash aside (see https://github.com/elastic/cloud-on-k8s/issues/1453) a reasonable starting point for Ingress support in ECK Helm charts would be feature parity with what was offered in [1], [2], and [3].
Let's use Ingress case to decide whether ECK Helm charts are intended solely as Helm "wrappers" for ECK CRDs (which is the current state). If yes, then Helm users would need to rely on custom charts or charts provided by 3rd parties to manage resources such as Ingress.