The project is currently pre-alpha and it is expected that breaking changes to the API will be made in the upcoming releases.
See the design docs for planned work on upcoming milestones.
This project is a component of the Operator Framework, an open source toolkit to manage Kubernetes native applications, called Operators, in an effective, automated, and scalable way. Read more in the introduction blog post.
Operators make it easy to manage complex stateful applications on top of Kubernetes. However writing an operator today can be difficult because of challenges such as using low level APIs, writing boilerplate, and a lack of modularity which leads to duplication.
The Operator SDK is a framework designed to make writing operators easier by providing:
- High level APIs and abstractions to write the operational logic more intuitively
- Tools for scaffolding and code generation to bootstrap a new project fast
- Extensions to cover common operator use cases
The SDK provides the following workflow to develop a new operator:
- Create a new operator project using the SDK Command Line Interface(CLI)
- Define new resource APIs by adding Custom Resource Definitions(CRD)
- Specify resources to watch using the SDK API
- Define the operator reconciling logic in a designated handler and use the SDK API to interact with resources
- Use the SDK CLI to build and generate the operator deployment manifests
At a high level an operator using the SDK processes events for watched resources in a user defined handler and takes actions to reconcile the state of the application.
- dep version v0.5.0+.
- git
- go version v1.10+.
- docker version 17.03+.
- kubectl version v1.9.0+.
- Access to a kubernetes v.1.9.0+ cluster.
First, checkout and install the operator-sdk CLI:
$ mkdir -p $GOPATH/src/github.com/operator-framework
$ cd $GOPATH/src/github.com/operator-framework
$ git clone https://github.com/operator-framework/operator-sdk
$ cd operator-sdk
$ git checkout master
$ make dep
$ make install
Create and deploy an app-operator using the SDK CLI:
# Create an app-operator project that defines the App CR.
$ mkdir -p $GOPATH/src/github.com/example-inc/
$ cd $GOPATH/src/github.com/example-inc/
$ operator-sdk new app-operator --api-version=app.example.com/v1alpha1 --kind=App
$ cd app-operator
# Build and push the app-operator image to a public registry such as quay.io
$ operator-sdk build quay.io/example/app-operator
$ docker push quay.io/example/app-operator
# Update the operator manifest to use the built image name
$ sed -i 's|REPLACE_IMAGE|quay.io/example/app-operator|g' deploy/operator.yaml
# Deploy the app-operator
$ kubectl create -f deploy/sa.yaml
$ kubectl create -f deploy/rbac.yaml
$ kubectl create -f deploy/crd.yaml
$ kubectl create -f deploy/operator.yaml
# By default, creating a custom resource (App) triggers the app-operator to deploy a busybox pod
$ kubectl create -f deploy/cr.yaml
# Verify that the busybox pod is created
$ kubectl get pod -l app=busy-box
NAME READY STATUS RESTARTS AGE
busy-box 1/1 Running 0 50s
# Cleanup
$ kubectl delete -f deploy/cr.yaml
$ kubectl delete -f deploy/crd.yaml
$ kubectl delete -f deploy/operator.yaml
$ kubectl delete -f deploy/rbac.yaml
$ kubectl delete -f deploy/sa.yaml
To learn more about the operator-sdk, see the user guide.
To explore any operator samples built using the operator-sdk, see the operator-sdk-samples.
See CONTRIBUTING for details on submitting patches and the contribution workflow.
See reporting bugs for details about reporting any issues.
Operator SDK is under Apache 2.0 license. See the LICENSE file for details.