amdatu/amdatu-kubernetes-deploymentctl-backend repository overview

⁠Introduction

Amdatu Kubernetes Deploymentctl provides basically a UI for the Amdatu Kubernetes Deployer, but it has some additional features.

This repository contains the backend part, see the Amdatu Kubernetes Deploymentctl Frontend repository for the frontend.

Features are:

• Integration with an authentication and authorization backend for getting authorized namespaces
• Management of Kubernetes Secrets
• Docker Hub integration for easy selecting of Docker images and tags for deployments
• Webhooks for automated redeployments

Amdatu Kubernetes Deployer is used in several production environments, and is actively maintained.

⁠Related components

Amdatu Kubernetes Deploymentctl depends on

• Kubernetes
• Amdatu Kubernetes Deployer
• An auth backend (work in progress, this backend needs further specification)
• A Redis data store

⁠Getting started

Run the backend together with the frontend with Docker Compose. You can find a compose file in the run directory, just change the environment variables to your needs.

⁠Authentication and authorization

Authentication against the Kubernetes API is supported by the underlying Amdatu Kubernetes Java client, but not implemented in this component yet.

The earlier mentioned auth backend provides preliminary support for namespace authorization. See org.amdatu.deploymentctl.auth.LoginResource.java for current implementation details. Warning, the authorization mechanism will be changed soon to OAuth.

⁠Getting involved

Bug reports and feature requests⁠ and of course pull requests are greatly appreciated! The project is built on Bamboo⁠. The build produces a runnable jar file and pushes a Docker image.

⁠Versioning

The Docker images are tagged using a alpha/beta/prod schema. The continuous build pushes amdatu/deploymentctl-backend:alpha. When a version is stable, we promote it to beta. The image is not rebuild, but a tag is set in git specifying the version number (e.g. 1.x.x). For Docker we set multiple tags:

• beta
• 1.x.x

This way you can both reference the latest beta version, or a specific tagged version. From beta we promote images to production. The image is not rebuild, but new tags are added:

• production
• latest

This way you can reference the latest stable production version.

The list of tags can be found on Docker Hub⁠.