k3s/pkg/controller/node
Justin Santa Barbara 54195d590f Use strongly-typed types.NodeName for a node name
We had another bug where we confused the hostname with the NodeName.

To avoid this happening again, and to make the code more
self-documenting, we use types.NodeName (a typedef alias for string)
whenever we are referring to the Node.Name.

A tedious but mechanical commit therefore, to change all uses of the
node name to use types.NodeName

Also clean up some of the (many) places where the NodeName is referred
to as a hostname (not true on AWS), or an instanceID (not true on GCE),
etc.
2016-09-27 10:47:31 -04:00
..
cidr_allocator.go Retry assigning CIDRs 2016-07-18 17:06:04 +02:00
cidr_allocator_test.go List all nodes and occupy cidr map before starting allocations 2016-07-16 13:54:01 -07:00
cidr_set.go Retry assigning CIDRs 2016-07-18 17:06:04 +02:00
cidr_set_test.go Run goimports 2016-08-02 15:12:39 +03:00
controller_utils.go Use strongly-typed types.NodeName for a node name 2016-09-27 10:47:31 -04:00
doc.go Use Go canonical import paths 2016-07-16 13:48:21 -04:00
metrics.go Change the eviction metric type and fix rate-limited-timed-queue 2016-09-08 12:20:51 +02:00
nodecontroller.go Use strongly-typed types.NodeName for a node name 2016-09-27 10:47:31 -04:00
nodecontroller_test.go Use strongly-typed types.NodeName for a node name 2016-09-27 10:47:31 -04:00
rate_limited_queue.go Change the eviction metric type and fix rate-limited-timed-queue 2016-09-08 12:20:51 +02:00
rate_limited_queue_test.go Change the eviction metric type and fix rate-limited-timed-queue 2016-09-08 12:20:51 +02:00
test_utils.go Fix FakeNodeHandler Update behaviour 2016-09-14 12:34:37 +03:00