vexxhost
/
node-labeler
Code Issues Proposed changes
Node Labeler for Kubernetes
7 Commits 1 Branch 0 Tags 105 KiB
Go 92.8%
Dockerfile 7.2%
Go to file
Zuul bd20aaa75b Merge "Build multi-arch images" 2020-07-24 20:34:09 +00:00
.gitreview Added .gitreview 2020-07-02 16:29:12 +00:00
.zuul.yaml Build multi-arch images 2020-07-24 16:06:13 -04:00
Dockerfile Build multi-arch images 2020-07-24 16:06:13 -04:00
README.md Add retry mechanism against api connection fail 2020-07-04 00:35:24 +03:00
bindep.txt Add retry mechanism against api connection fail 2020-07-04 00:35:24 +03:00
go.mod Fix the logic to check compute node 2020-07-23 17:51:01 +03:00
go.sum Fix the logic to check compute node 2020-07-23 17:51:01 +03:00
main.go Fix getting node name 2020-07-23 20:01:31 +03:00
manifest.yaml Add retry mechanism against api connection fail 2020-07-04 00:35:24 +03:00
units_test.go Fix getting node name 2020-07-23 20:01:31 +03:00

README.md

Node labeler

Zuul

This is a very small tool that can run as a DaemonSet inside your Kubernetes cluster which will automatically label your nodes based on the product and vendor. This can help with things like running specific monitoring tools on specific hardware.

This is an example of labeled Dell PowerEdge machine:

Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=<snip>
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/master=
                    node.vexxhost.com/product=poweredge-r640
                    node.vexxhost.com/vendor=dell-inc

In addition, we provide a very simple manifest attached inside this repository which helps you setup a service account that is locked down to only GET and PATCH nodes in the Kubernetes API with the code for a DaemonSet. It shouldn't require any changes to get going on your cluster.