opm-operator

module
v1.0.0-alpha.22 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Sep 30, 2026 License: Apache-2.0

README

opm-operator

// TODO(user): Add simple overview of use/purpose

Description

// TODO(user): An in-depth paragraph about your project and overview of use

Getting Started

Prerequisites
  • go version v1.26.2+
  • docker version 17.03+.
  • kubectl version v1.11.3+.
  • Access to a Kubernetes v1.11.3+ cluster.
Installing

Install the latest release directly from the GitHub release asset:

kubectl apply -f https://github.com/open-platform-model/opm-operator/releases/latest/download/install.yaml

The manifest pins the controller image by digest (ghcr.io/open-platform-model/opm-operator:vX.Y.Z@sha256:...), so the exact bytes from the release are pulled regardless of future tag movement.

Verify the release image signature with cosign:

cosign verify ghcr.io/open-platform-model/opm-operator:vX.Y.Z \
  --certificate-identity-regexp='^https://github.com/open-platform-model/opm-operator/\.github/workflows/release\.yml@refs/heads/main$' \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com

For a PR preview image, swap the workflow path to image-pr.yml and adjust the ref:

cosign verify ghcr.io/open-platform-model/opm-operator:pr-123 \
  --certificate-identity-regexp='^https://github.com/open-platform-model/opm-operator/\.github/workflows/image-pr\.yml@refs/pull/.*$' \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com
Image tag semantics
Tag Stability Purpose
:v<version> Immutable Exact release version; points at a specific manifest-list digest.
:<digest> (@sha256:...) Immutable Cryptographic pin, always the same bytes.
:latest Moves Tracks the newest published release.
:pr-<N> Mutable Preview for PR N; overwrites on force-push. Not for production.
:sha-<short7> Effectively immutable Commit-pinned build; published on both PR and release runs.
To Deploy on the cluster

Build and push your image to the location specified by IMG:

task docker:build docker:push IMG=<some-registry>/opm-operator:tag

NOTE: This image ought to be published in the personal registry you specified. And it is required to have access to pull the image from the working environment. Make sure you have the proper permission to the registry if the above commands don’t work.

Install the CRDs into the cluster:

task operator:crds

Deploy the Manager to the cluster with the image specified by IMG:

task operator:controller:install IMG=<some-registry>/opm-operator:tag

NOTE: If you encounter RBAC errors, you may need to grant yourself cluster-admin privileges or be logged in as admin.

Create instances of your solution You can apply the samples (examples) from the config/sample:

kubectl apply -k config/samples/

NOTE: Ensure that the samples has default values to test it out.

To Uninstall

Delete the instances (CRs) from the cluster:

kubectl delete -k config/samples/

Delete the APIs(CRDs) from the cluster:

task operator:crds:remove

UnDeploy the controller from the cluster:

task operator:controller:uninstall

Project Distribution

Following the options to release and provide this solution to the users.

By providing a bundle with all YAML files
  1. Build the installer for the image built and published in the registry:
task operator:installer IMG=<some-registry>/opm-operator:tag

NOTE: The task above generates an 'install.yaml' file in the dist directory. This file contains all the resources built with Kustomize, which are necessary to install this project without its dependencies.

  1. Using the installer

Users can just run 'kubectl apply -f ' to install the project, i.e.:

kubectl apply -f https://raw.githubusercontent.com/<org>/opm-operator/<tag or branch>/dist/install.yaml

Contributing

// TODO(user): Add detailed information on how you would like others to contribute to this project

NOTE: Run task --list for more information on all potential task targets

More information can be found via the Kubebuilder Documentation

License

Copyright 2026.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Directories

Path Synopsis
api
v1alpha1
Package v1alpha1 contains API Schema definitions for the opmodel.dev v1alpha1 API group.
Package v1alpha1 contains API Schema definitions for the opmodel.dev v1alpha1 API group.
internal
apply
Package apply contains server-side apply and prune integration points.
Package apply contains server-side apply and prune integration points.
inventory
Package inventory contains controller-local ownership inventory helpers.
Package inventory contains controller-local ownership inventory helpers.
moduleacquire
Package moduleacquire loads a ModuleInstance's target module from the OCI registry into a library *module.Module.
Package moduleacquire loads a ModuleInstance's target module from the OCI registry into a library *module.Module.
platform
Package platform holds the process-local platform store: a single-slot, concurrency-safe holder of the platform module generated and built from the cluster-singleton Platform CR and the set of active transformer claims.
Package platform holds the process-local platform store: a single-slot, concurrency-safe holder of the platform module generated and built from the cluster-singleton Platform CR and the set of active transformer claims.
reconcile
Package reconcile contains high-level release reconciliation orchestration.
Package reconcile contains high-level release reconciliation orchestration.
render
Package render contains OPM render orchestration boundaries.
Package render contains OPM render orchestration boundaries.
shrink
Package shrink answers one question about a rendered TransformerRegistration: does applying it take a contract away from instances that still demand it (0015:D16)?
Package shrink answers one question about a rendered TransformerRegistration: does applying it take a contract away from instances that still demand it (0015:D16)?
source
Package source contains Flux source-controller integration helpers.
Package source contains Flux source-controller integration helpers.
status
Package status contains release condition, digest, and history helpers.
Package status contains release condition, digest, and history helpers.
version
Package version carries the operator's build-time version identity.
Package version carries the operator's build-time version identity.
pkg
core
Package core provides shared primitives for the OPM rendering pipeline.
Package core provides shared primitives for the OPM rendering pipeline.
test
fixtures
Catalog subscription coordinate for registry-backed specs.
Catalog subscription coordinate for registry-backed specs.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL