Images needed when setting up a custom registry for deploying Observability for Kubernetes Operator.

Products

• DX OpenExplore

Issue/Introduction

When deploying from a local image registery the Operator, Collector and Proxy images are downloaded from Docker Hub.

Error when deploying from local location when the Operator image is missing. 

Normal   Pulling    38s (x4 over 118s)  kubelet            Pulling image "<local image path>/kubernetes-operator:2.26.0"
Warning  Failed     38s (x4 over 118s)  kubelet            Failed to pull image "<local image path>/kubernetes-operator:2.26.0": rpc error: code = NotFound desc = failed to pull and unpack image "<local image path>/kubernetes-operator:2.26.0": failed to resolve image: <local image path>/kubernetes-operator:2.26.0: not found
Warning  Failed     38s (x4 over 118s)  kubelet            Error: ErrImagePull
Normal   BackOff    10s (x6 over 118s)  kubelet            Back-off pulling image "<local image path>/kubernetes-operator:2.26.0"
Warning  Failed     10s (x6 over 118s)  kubelet            Error: ImagePullBackOff

 

Simular errors are also seen for "kubernetes-collector:<version>" and "proxy:<version>"  if those images are missing from your local registry.

Resolution

Images for the latest Operator, Collector and Proxy versions are downloaded from Docker Hub.

caapm/kubernetes-operator
caapm/kubernetes-collector
caapm/proxy

Note: Confirm version compatablity between the Operator, Collector & Proxy images using the "Release Info" link in Additional Information below. 

Additional Information

Deploy the Observability for Kubernetes Operator with a custom registry

Docker Hub - https://hub.docker.com/u/caapm

wavefrontHQ / observability-for-kubernetes

Observability for kubernetes - Releases Info