Drycc (pronounced DAY-iss) Workflow is an open source Platform as a Service (PaaS) that adds a developer-friendly layer to any Kubernetes cluster, making it easy to deploy and manage applications on your own servers.
For more information about the Drycc Workflow, please visit the main project page at https://github.com/drycc/workflow.
We welcome your input! If you have feedback, please submit an issue. If you'd like to participate in development, please read the "Development" section below and submit a pull request.
The Controller is the central API server for Drycc Workflow. It is installed on a Kubernetes cluster, making it easy to deploy and manage applications on your own cluster. Below is a non-exhaustive list of things it can do:
- Create a new application
- Delete an application
- Scale an application
- Configure an application
- Create a new user
The Drycc project welcomes contributions from all developers. The high-level process for development matches many other open source projects. See below for an outline.
- Fork this repository
- Make your changes
- Submit a pull request (PR) to this repository with your changes, and unit tests whenever possible.
- If your PR fixes any issues, make sure you write Fixes #1234 in your PR description (where #1234 is the number of the issue you're closing)
- Drycc project maintainers will review your code.
- After two maintainers approve it, they will merge your PR.
Unit tests and code linters for controller run in a container with your local code directory
mounted in. You need Podman to run make test.
You'll want to test your code changes interactively in a working Kubernetes cluster. Follow the installation instructions if you need Kubernetes.
After you have a working Kubernetes cluster, you're ready to install Workflow.
When you've built your new feature or fixed a bug, make sure you've added appropriate unit tests and run make test to ensure your code works properly.
Also, since this component is central to the platform, it's recommended that you manually test and verify that your feature or fix works as expected. To do so, ensure the following environment variables are set:
DRYCC_REGISTRY- A Container registry that you have push access to and your Kubernetes cluster can pull from- If this is Drycc Registry, leave this variable empty
IMAGE_PREFIX- The organization in the Container repository. This defaults todrycc, but if you don't have access to that organization, set this to one you have push access to.SHORT_NAME(optional) - The name of the image. This defaults tocontrollerVERSION(optional) - The tag of the Container image. This defaults to the current Git SHA (the output ofgit rev-parse --short HEAD)
Then, run make deploy to build and push a new Container image with your changes and replace the existing one with your new one in the Kubernetes cluster. See below for an example with appropriate environment variables.
export IMAGE_PREFIX=arschles
make deployAfter the make deploy finishes, a new pod will be launched but may not be running. You'll need to wait until the pod is listed as Running and the value in its Ready column is 1/1. Use the following command watch the pod's status:
kubectl get pod --namespace=drycc -w | grep drycc-controller