ECK using Docker for Operator Container Registry docker.instead of elastic.co

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

I'm using the ECK Stack as described in this tutorial - Deploy an Elasticsearch cluster | Elastic Cloud on Kubernetes [1.8] for a basic ECK setup.

I want to change the container registry for operator to use the docker hub container registry. The Operator Config has a container-registry option to set it to a custom registry like docker.io instead of docker.elastic.co

My example ConfigMap.yaml for the custom container-registry

---

# Source: eck-operator/templates/configmap.yaml

apiVersion: v1

kind: ConfigMap

metadata:

  name: elastic-operator

  namespace: elastic-system

  labels:

    control-plane: elastic-operator

    app.kubernetes.io/version: "1.8.0"

data:

  eck.yaml: |-

    log-verbosity: 0

    metrics-port: 0

    container-registry: docker.io

    max-concurrent-reconciles: 3

    ca-cert-validity: 8760h

    ca-cert-rotate-before: 24h

    cert-validity: 8760h

    cert-rotate-before: 24h

    set-default-security-context: true

    kube-client-timeout: 60s

    elasticsearch-client-timeout: 180s

    disable-telemetry: false

    validate-storage-class: true

    enable-webhook: true

    webhook-name: elastic-webhook.k8s.elastic.co

---

But when pulling the docker image from docker.io, it cannot

Failed to pull image "docker.io/elasticsearch/elasticsearch:7.14.2": rpc error: code = Unknown desc = Error response from daemon

The issue is with using the dockerhub registery is that the elasticsearch image is an official image and doesn't need to be namespaced like this elasticsearch/elasticsearch

Has anyone encountered this?

2

U can change the image for the ECK resources. So for the kind: Elasticsearch, just set image: elasticsearch:<version>. See Create custom images | Elastic Cloud on Kubernetes [1.8] | Elastic

3

Thanks! That worked!

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.