Setting up a custom registry for deploying Observability for Kubernetes Operator.
search cancel

Setting up a custom registry for deploying Observability for Kubernetes Operator.

book

Article ID: 413757

calendar_today

Updated On:

Products

DX OpenExplore

Issue/Introduction

Use another image repository, such as your own Harbor repository, to deploy the Operator with all the necessary components, ie Cluster Collector, Node Collectors and Proxy. 

Resolution

Below link explains the process in detail.

Deploy the Observability for Kubernetes Operator with a custom registry

  1. Create a local directory called observability.
  2. Download wavefront-operator.yaml into the observability directory.
  3. Create a kustomization.yaml file in the observability directory.
  4. Modify the kustomization.yaml to identify images source & destination 

    images:
    - name: caapm/kubernetes-operator
      newName: YOUR_IMAGE_REGISTRY/kubernetes-operator


  5. Deploy the Observability for Kubernetes Operator using the local directory name.

    kubectl apply -k observability

A few items of Note:

Repository name and tags must be created as shown and are case sensitive. 

kubernetes-operator
kubernetes-collector
proxy



Example:



During deployment the Operator deployment expects the folder naming convention of "proxy" within the new Harbor repository.  If an alternate folder name is used the system will return an error that the folder was not found.  

 

Error: ImagePullBackOff
Pulling image "harbor.<project>/public/proxy:13.7": rpc error: code = NotFound desc = failed to pull and unpack image "harbor.<project>/public/proxy:13.7": failed to resolve reference "harbor.<project>/public/proxy: 13.7": harbor.<project>/public/proxy:13.7: not found

 

Deploy calling the folder rather than each YAML individually.

Deployment folder contains both;  kustomization.yaml and wavefront-operator yaml and you will reference that folder name during deployment.

$ kubectl apply -k observability

Example: 

You must name your customization yaml file 'kustomization.yaml'

Error seen when using another file name 

"unable to find one of 'kustomization.yaml', 'kustomization.yml' or 'Kustomization' in directory '/home/<file-path>/505"

 

In the kustomization yaml only the source image location includes the Operator build number.  

If both the source and destination images locations include the Operator build number, it will be appended twice during deployment causing error.

Failed to apply default image tag "Harbor<project>.com/public/kubernetes-operator: <buildVersion>:<buildVersion>: couldn't parse image name Harbor<project>.com/public/kubernetes-operator: <buildVersion>:<buildVersion>: invalid reference format

 

 

For example, this is correctly configured kustomization.yaml file 

Additional Information

Powered by Wolken Software