autoapply 0.3.1

Automatically apply changes from a remote URL to the Kubernetes cluster

Automatically apply changes from a remote URL to the Kubernetes cluster

Usage

To start the service locally, run

$ pip3 install --user autoapply
$ autoapply server https://user:[e-mail]/repository/my-service.yaml

For a docker version, use

$ docker run -d -e URL=https://example.com/my-service.yaml pascalgn/autoapply

The following URLs are supported:

• Direct access via HTTPS, for example https://example.com/my-config/config.yaml

• Access via SSH, [e-mail]:path/to/repository.git:path/to/config.yaml or ssh://[e-mail]:123/path/to/repository.git:path/to/config.yaml

For Git URLs you can append #my-branch to specify the branch to be used. If no branch is given, master will be used.

Providing SSH keys

To use SSH keys, be sure to specify 600 as default mode when mounting them. For Kubernetes, this would look like this:

containers:
  - name: autoapply-container
    image: pascalgn/autoapply
    env:
      - name: URL
        value: '[e-mail]:pascalgn/hostinfo.git:examples/kubernetes.yaml'
    volumeMounts:
      - name: autoapply-ssh-secret-volume
        mountPath: /home/autoapply/.ssh
volumes:
  - name: autoapply-ssh-secret-volume
    secret:
      secretName: autoapply-ssh-secret-volume
      defaultMode: 256

Encrypted files

You can encrypt the values of Yaml files to protect Kubernetes secrets like SQL database or Docker registry credentials:

$ autoapply crypt -f application-secrets.yaml
Password: my-secret-passphrase

This will delete the original file and create a file application-secrets.yaml.crypt, which can later be decrypted by autoapply when providing the password for the server:

$ mkdir ~/.autoapply
$ echo -n my-secret-passphrase > ~/.autoapply/crypt.key
$ autoapply server https://example.com/repository/application-secrets.yaml

License

Autoapply is licensed under the ISC License