Mike Palmer

Looks to me that you're not getting valid responses back from elasticsearch: ValueError("No JSON object could be decoded") It very well could be because of a timeout situation if your...

I started looking at this today and noticed Helm may be adopting an enhancement `HIP 0016` that implements `export-values`. Rather than modify the `opensearch` and `opensearch-dashboards` charts to support global...

Correct, once the execution controller job is marked as terminated, completed, etc and the pod goes away the deployment / workers remain but end up in a crash loop. In...

How about adding this to Dockerfile for opencontainers image spec ``` LABEL org.opencontainers.image.version="$TERASLICE_VERSION" \ org.opencontainers.image.created="$BUILD_TIMESTAMP" \ org.opencontainers.image.documentation="https://terascope.github.io/teraslice/docs/overview" \ org.opencontainers.image.licenses="Apache-2.0" \ org.opencontainers.image.revision="$GITHUB_SHA" \ org.opencontainers.image.source="https://github.com/terascope/teraslice" \ org.opencontainers.image.title="Teraslice" \ org.opencontainers.image.url="https://terascope.github.io/teraslice" \ org.opencontainers.image.vendor="Terascope" ```

Referencing another dynamically provisioned "{release name}-certs" configmap is already being done for "{release name}-worker" configs. https://github.com/terascope/teraslice/blob/a83eca00919408c06b955beffa23a9fde97441e0/packages/teraslice/lib/cluster/services/cluster/backends/kubernetes/k8sResource.js#L59-L63

Maybe the most desireable thing to do is instead of a configmap is a secret. Something along these lines, where it could contain any number of certs https://kubernetes.io/docs/concepts/storage/volumes/#example-pod-with-multiple-secrets-with-a-non-default-permission-mode-set