Skip to content

Latest commit

 

History

History
51 lines (33 loc) · 1.55 KB

DEVELOPING.md

File metadata and controls

51 lines (33 loc) · 1.55 KB

Developing Onload Operator and Onload Device Plugin

Environment

  • Go version 1.21+
  • Access to your cluster via kubectl or oc
  • Docker or equivalent (e.g. podman)

The Onload Operator is built with the Operator SDK and Kubebuilder.

Prerequisites

The Onload Operator and Onload Device Plugin consume Onload container images (onload-user and either onload-source or onload-module). You may wish to pre-populate your cluster's container image registry, either with the official images provided or your own builds.

Build and deploy from source

Configure a development registry and configure cluster for insecure registries if required. Specify the following image locations:

export REGISTRY_BASE=image-registry.openshift-image-registry.svc:5000/onload-clusterlocal
export IMG=$REGISTRY_BASE/onload-operator:latest
export DEVICE_IMG=$REGISTRY_BASE/onload-device-plugin:latest

Create and push the Onload Operator controller image:

make docker-build docker-push

Create and push the Onload Device Plugin image:

make device-plugin-docker-build device-plugin-docker-push

Deploy the Onload Operator:

make deploy

Ensure that $DEVICE_IMG is exported when deploying the operator, or append DEVICE_IMG=... to the make invocation.

Continue with deploying the Onload CR.

Footnotes

Copyright (c) 2023 Advanced Micro Devices, Inc.