do-operator is a Kubernetes operator for managing and consuming DigitalOcean resources from a Kubernetes cluster.

Currently it supports DigitalOcean Databases.

This project is in BETA.

• This operator should not be depended upon for production use at this time.
• The CRDs in this project are currently v1alpha1 and may change in the future.
• DigitalOcean supports this project on a best-effort basis via GitHub issues.

To install the operator on a Kubernetes cluster, you can follow these steps:

1. Generate a DigitalOcean API token and base64 encode it.
2. Edit the manifest for the most recent version in the releases/ directory. Find the do-operator-do-api-token Secret and replace the access-token value with your base64-encoded token:

apiVersion: v1
data:
  access-token: <your base64-encoded token goes here>
kind: Secret
metadata:
  name: do-operator-do-api-token
  namespace: do-operator-system
type: Opaque

3. Deploy the manifest:

kubectl apply -f releases/do-operator-<version>.yaml

See the full documentation in the docs directory.

The do-operator is built using kubebuilder. The Kubebuilder Book is a useful reference for understanding how the pieces fit together.

To test your changes you will need a Kubernetes cluster to run against. We suggest using DigitalOcean Kubernetes, but you may use KIND or any other cluster for testing. The following will automatically use the current context in your kubeconfig file (i.e. whatever cluster kubectl cluster-info shows).

Note that you will be billed for any DigitalOcean resources you create via the operator while testing. Make sure you are aware of DigitalOcean's pricing and clean up resources when you're finished testing.

1. Install the Custom Resource Definitions:

make install

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

make docker-build docker-push IMG=<some-registry>/do-operator:tag

3. Deploy cert-manager, which is necessary to manage certificates for the webhooks.

4. Generate a DigitalOcean API token to use for testing.

5. Create a local environment file containing your API token. Note that this file is in the .gitignore so it will remain local to your machine:

cat <<EOF > config/manager/do-api-token.env
access-token=<your api token here>
EOF

The contents of this file will be used to create a secret in the cluster, which is used by the operator deployment to manage resources in your DigitalOcean account.

6. Deploy the controller to the cluster with the image specified by IMG:

make deploy IMG=<some-registry>/do-operator:tag

To undeploy the controller from the cluster:

make undeploy

To delete the CRDs from the cluster:

make uninstall

At DigitalOcean we value and love our community! If you have any issues or would like to contribute, see CONTRIBUTING.md.

Copyright 2022 DigitalOcean.

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.