Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

Publish taints for specialised hosts

Latest
Compare
Choose a tag to compare
@amrc-benmorrow amrc-benmorrow released this 05 Feb 14:12
· 1 commit to main since this release
c2ca45a

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.