Installing ES with Custom image from private repository fails

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
#1

Here is my file -

apiVersion: elasticsearch.k8s.elastic.co/v1alpha1
kind: Elasticsearch
metadata:
  name: jaeger-elasticsearch
  namespace: test
spec:
  image: phx.ocir.io/<>/elasticsearch/elasticsearch:7.3.2
  version: 7.3.2
  nodes:
    - nodeCount: 1
      config:
        node.master: true
        node.data: true
        node.ingest: true

I've verified that the image exists and does not require secrets for pull.

After installation I see this -

NAME                   HEALTH   NODES   VERSION   PHASE     AGE
jaeger-elasticsearch                    7.3.2     Invalid   6m

Can someone pls help ? How do I debug/get logs as to what's going on ?

#2

The location of the image <> was masked deliberately.

#3

Once I switched to NodeSets definition, it went through fine.

apiVersion: elasticsearch.k8s.elastic.co/v1alpha1
kind: Elasticsearch
metadata:
  name: jaeger-elasticsearch
  namespace: observability
spec:
  image: phx.ocir.io/test/elasticsearch/elasticsearch:7.3.2
  version: 7.3.2
  nodeSets:
    - name: default
      config:
        node.master: true
        node.data: true
        node.ingest: true
      podTemplate:
        metadata:
          labels:
            jaeger: jaeger-elasticsearch
        spec:
          containers:
            - name: elasticsearch
              resources:
                requests:
                  memory: 4Gi
                  cpu: 1
                limits:
                  memory: 4Gi
                  cpu: 2
      count: 3
#4

If anyone else ends up here: the specification was expressed using ECK 0.9 syntax in the first post ( nodes ), instead of using the 1.0.0 syntax ( nodeSets ). Using a private registry should work as expected.