Publish taints for specialised hosts

Some hosts on edge clusters have specialised hardware, or are otherwise unsuitable for running general-purpose 'floating' workloads. Define a taint factoryplus.app.amrc.co.uk/specialised to handle these situations.

Hosts which should not accept floating workloads can be tainted with this taint, using any suitable value indicating the reason for the taint being applied. Using a dedicated taint will avoid interference with other uses of taints, e.g. for cordoning. The Edge Agent helm chart will need to be updated to tolerate this taint, with any value, for deployments targetted to a specific host.

This release of the Edge Sync operator will push the value associated with this taint, where it exists, up to the ConfigDB under the Cluster Status entry. This will allow the Manager to display the information to the user when deploying a Node.

v0.0.3-dev.1: Publish 'fieldbus' host taints to the ConfigDB (#15)

Publish taints on hosts

Initial release

This operator runs on an edge cluster watching the ConfigDB for Edge Deployment entries. When an entry belonging to this cluster is changed, it arranges to deploy Helm charts as specified by the config entries.

It also keeps the Edge Cluster Status entries up to date with the current state of this cluster: the hosts available, and the current sealed-secrets certificate.

v0.0.2-dev.3: Tidy up for release (#12)

Test release from main.

v0.0.2-dev.2

Update utilities.

v0.0.2-dev.1

Try a release