Operator Utility Library
This library layers on top of the Operator SDK and with the objective of helping writing better and more consistent operators.
Scope of this library
This library covers three main areas:
- Idempotent methods to manipulate resources and array of resources
- Basic operator lifecycle needs (validation, initialization, status and error management, finalization)
- Enforcing resources operator support. For those operators which calculate a set of resources that need to exist and then enforce them, generalized support for the enforcing phase is provided.
Idempotent Methods to Manipulate Resources
The following idempotent methods are provided (and their corresponding array version):
- createIfNotExists
- createOrUpdate
- deleteIfExits
Also there are utility methods to manage finalizers, test ownership and process templates of resources.
Basic Operator Lifecycle Management
To get started with this library do the following:
Change your reconciler initialization as exemplified below to add a set of utility methods to it
import "github.com/redhat-cop/operator-utils/pkg/util"
...
type MyReconciler struct {
util.ReconcilerBase
... other optional fields ...
}
...
func newReconciler(mgr manager.Manager) reconcile.Reconciler {
return &ReconcileMyCRD{
ReconcilerBase: util.NewReconcilerBase(mgr.GetClient(), mgr.GetScheme(), mgr.GetConfig(), mgr.GetRecorder(controllerName)),
}
}
If you want status management, add this to your CRD:
import "github.com/operator-framework/operator-sdk/pkg/status"
...
// +k8s:openapi-gen=true
type MyCRDStatus struct {
Conditions status.Conditions `json:"conditions"`
}
...
func (m *MyCRD) GetReconcileStatus() status.Conditions {
return m.Status.Conditions
}
func (m *MyCRD) SetReconcileStatus(reconcileStatus status.Conditions) {
m.Status.Conditions = reconcileStatus
}
At this point your controller is able to reuse leverage the utility methods of this library:
- managing CR validation
- managing CR initialization
- managing status and error conditions
- managing CR finalization
- high-level object manipulation functions such as:
- createOrUpdate, createIfNotExists, DeleteIfExists
- same functions on an array of objects
- go template processing of objects
A full example is provided here
Managing CR validation
To enable CR validation add this to your controller:
if ok, err := r.IsValid(instance); !ok {
return r.ManageError(instance, err)
}
The implement the following function:
func (r *ReconcileMyCRD) IsValid(obj metav1.Object) (bool, error) {
mycrd, ok := obj.(*examplev1alpha1.MyCRD)
...
}
Managing CR Initialization
To enable CR initialization, add this to your controller:
if ok := r.IsInitialized(instance); !ok {
err := r.GetClient().Update(context.TODO(), instance)
if err != nil {
log.Error(err, "unable to update instance", "instance", instance)
return r.ManageError(instance, err)
}
return reconcile.Result{}, nil
}
Then implement the following function:
func (r *ReconcileMyCRD) IsInitialized(obj metav1.Object) bool {
mycrd, ok := obj.(*examplev1alpha1.MyCRD)
}
Managing Status and Error Conditions
To update the status with success and return from the reconciliation cycle, code the following:
return r.ManageSuccess(instance)
To update the status with failure, record and event and return from the reconciliation cycle, code the following:
return r.ManageError(instance, err)
notice that this function will reschedule a reconciliation cycle with increasingly longer wait time up to six hours.
Managing CR Finalization
to enable CR finalization add this to your controller:
if util.IsBeingDeleted(instance) {
if !util.HasFinalizer(instance, controllerName) {
return reconcile.Result{}, nil
}
err := r.manageCleanUpLogic(instance)
if err != nil {
log.Error(err, "unable to delete instance", "instance", instance)
return r.ManageError(instance, err)
}
util.RemoveFinalizer(instance, controllerName)
err = r.GetClient().Update(context.TODO(), instance)
if err != nil {
log.Error(err, "unable to update instance", "instance", instance)
return r.ManageError(instance, err)
}
return reconcile.Result{}, nil
}
Then implement this method:
func (r *ReconcileMyCRD) manageCleanUpLogic(mycrd *examplev1alpha1.MyCRD) error {
...
}
Support for operators that need to enforce a set of resources to a defined state
Many operators have the following logic:
- Phase 1: based on the CR and potentially additional status as set of resources that need to exist is calculated.
- Phase 2: These resources are then created or updated against the master API.
- Phase 3: A well written also ensures that these resources stay in place and are not accidentally or maliciously changed by third parties.
These phases are of increasing difficulty to implement. It's also true that phase 2 and 3 can be generalized.
Operator-utils offers some scaffolding to writing these kinds of operators.
Similarly to the BaseReconciler
class, we have a base type to extend called: EnforcingReconciler
. This class extends from BaseReconciler
, so you have all the same facilities as above.
The body of the reconciler function will look something like this:
validation...
initialization...
(optional) finalization...
Phase1 ... calculate a set of resources to be enforced -> LockedResources
err = r.UpdateLockedResources(instance, lockedResources)
if err != nil {
log.Error(err, "unable to update locked resources")
return r.ManageError(instance, err)
}
return r.ManageSuccess(instance)
this is all you have to do for basic functionality. For mode details see the example
the EnforcingReconciler will do the following:
-
restore the resources to the desired stated if the are changed. Notice that you can exclude paths from being considered when deciding whether to restore a resource. As set oj JSON Path can be passed together with the LockedResource. It is recommended to set these paths:
.metadata
.status
-
restore resources when they are deleted.
The finalization method will look like this:
func (r *ReconcileEnforcingCRD) manageCleanUpLogic(instance *examplev1alpha1.EnforcingCRD) error {
err := r.Terminate(instance, true)
if err != nil {
log.Error(err, "unable to terminate enforcing reconciler for", "instance", instance)
return err
}
... additional finalization logic ...
return nil
}
Convenience methods are also available for when resources are templated. See the templatedenforcingcrd controller as an example.
Local Development
Execute the following steps to develop the functionality locally. It is recommended that development be done using a cluster with cluster-admin
permissions.
go mod download
optionally:
go mod vendor
Using the operator-sdk, run the operator locally:
oc apply -f deploy/crds
OPERATOR_NAME='example-operator' operator-sdk --verbose run --local --watch-namespace "" --operator-flags="--zap-level=debug"
Testing
EnforcingCRD controller testing
oc new-project test-enforcingcrd
oc apply -f test/enforcing_cr.yaml -n test-enforcingcrd
oc apply -f test/failing-enforcing_cr.yaml -n test-enforcingcrd
TemplatedEnforcingCRD controller testing
oc new-project test-templatedenforcingcrd
oc apply -f test/templatedenforcing_cr.yaml -n test-templatedenforcingcrd
License
This project is licensed under the Apache License, Version 2.0.
Release Process
To release execute the following:
git tag -a "<version>" -m "release <version>"
git push upstream <version>
use this version format: vM.m.z