This repository provides a K3D config file. Mainly it is designed to be managed by administrators, DevOps engineers, SREs.
k3d
= version is specified in the project.yaml file
of each project of the repository in the tools
section.
This repository uses the classic GitFlow workflow, embracing all its advantages and disadvantages.
Stable branches: develop, master
Each merge in the master branch adds a new SemVer2 tag and a GitHub release is created.
This configuration of K3D manifest can only be launched from the project repository via RMK,
because the entire input set of variables is formed by RMK at the moment
the commands are launched: rmk cluster k3d
.
RMK also keeps track of which version of the release of K3D config file the project repository will use.
The version of config file artifact is described in the project.yaml file of each
project repository in the section:
inventory:
clusters:
k3d.provisioner.infra:
version: <SemVer2>
url: git::https://github.com/edenlabllc/{{.Name}}.git?ref={{.Version}}
For development, navigate to the local .PROJECT/clusters/k3d.provisioner.infra-<version>/k3d.yaml
directory of a project repository,
then perform the changes directly in the files and test them.
Finally, copy the changed files to a new feature branch of this repository and create a pull request (PR).