armada-operator

armada-operator is a small go project to automate the installation (and eventually management) of a fully-functional Armada deployment to a Kubernetes cluster using the Kubernetes operator pattern.

Description

Armada is a multi-Kubernetes batch job scheduler. This operator aims to make Armada easy to deploy and, well, operate in a Kubernetes cluster.

Quickstart

Want to start hacking right away?

You’ll need a Kubernetes cluster to run the operator. You can use KIND to run a local cluster for testing, or you can run against a remote cluster.

Note: Your controller will automatically use the current context in your kubeconfig file (i.e. whatever cluster kubectl cluster-info shows).

Start a Development Cluster

This section assumes you have KIND installed.

make dev-setup

This will:

• boot a kind cluster specifically for armada-operator development work
• start postgres, pulsar, and redis pods in the cluster

Then:

make dev-install-controller

Which will:

• install each CRD supported by the armada-operator on the cluster
• create a pod inside the kind cluster running the armada-operator controllers

Note: You may need to wait for some services (like Pulsar) to finish coming up to proceed to the next step. Check the status of the cluster with $ kubectl get -n armada pods.

Finally:

kubectl apply -n armada -f $(REPO_ROOT)/config/samples/deploy_armada.yaml

Which will deploy samples of each CRD. Once every Armada service is deployed, you should have a fully functional install of Aramda running.

To stop the development cluster:

make dev-teardown

This will totally destroy your development Kind cluster.

Getting Started

Running on a Cluster

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

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

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

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

1. Install Instances of Custom Resources:

kubectl apply -f config/samples/

Uninstall CRDs

To delete the CRDs from the cluster:

make uninstall

Undeploy controller

UnDeploy the controller to the cluster:

make undeploy

Using Helm Charts

This repo includes Helm charts for Armada Operator and Armada Application installation, in the deployment directory. The first chart, armada-operator, will install the Operator (CRDs and controller-manager, mainly). The other two, armada-server and armada-executor, will install the Armada application itself in your cluster(s).

The armada-operator chart should be installed first on all clusters to be used. Then, one or both of the application charts.

Why two charts for the application? Armada supports two cluster types: server and executor. The server install includes the API server and scheduler. The executor install includes the worker process (executor) which manages Armada jobs for a particular cluster. They can be installed in the same cluster, but typically we’d expect to see one server install and one or more executor installations.

cd deployment
helm install armada-operator ./armada-operator/ -n armada
helm install armada-server ./armada-server -n armada
helm install armada-executor ./armada-executor -n armada

Contributing

Please feel free to contribute bug-reports or ideas for enhancements via GitHub’s issue system.

Code contributions are also welcome. When submitting a pull-request please ensure it references a relevant issue as well as making sure all CI checks pass.

Test All Changes

Please test contributions thoroughly before requesting reviews. At a minimum:

make test
make test-integration
make lint

should all succeed without error.

Add and change appropriate unit and integration tests to ensure your changes are covered by automated tests and appear to be correct.

How it works

This project aims to follow the Kubernetes Operator pattern

It uses Controllers which provides a reconcile function responsible for synchronizing resources untile the desired state is reached on the cluster

Test It Out

1. Install the CRDs into the cluster:

make install

1. Run your controller (this will run in the foreground, so switch to a new terminal if you want to leave it running):

make run

NOTE: You can also run this in one step by running: make install run

Modifying the API definitions

If you are editing the API definitions, generate the manifests such as CRs or CRDs using:

make manifests

NOTE: Run make --help for more information on all potential make targets

More information can be found via the Kubebuilder Documentation

License

Copyright 2023.

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.

This site is open source. Improve this page.