k3s/cmd/kubeadm/app/discovery
Rostislav M. Georgiev 576b8d3f4f kubeadm: Split discovery from JoinConfiguration
This change splits out discovery fields from JoinConfiguration by performing
the following changes:

- Introduce a BootstrapTokenDiscovery structure, that houses configuration
  options needed for bootstrap token based discovery.

- Introduce a FileDiscovery structure, that houses configuration options
  (currently only a single option) needed for KubeConfig based discovery.

- Introduce a Discovery structure, that houses common options (such as
  discovery timeout and TLS bootstrap token) as well as pointer to an instance
  of either BootstrapTokenDiscovery or FileDiscovery structures.

- Replace the old discovery related JoinConfiguration members with a single
  Discovery member.

This change is required in order to cleanup the code of unnecessary logic and
make the serialized JoinConfiguration more structured (and therefore, more
intuitive).

Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>
2018-10-16 15:25:32 +03:00
..
file Moved staging/src/k8s.io/client-go/tools/bootstrap to staging/src/k8s.io/cluster-bootstrap 2018-10-02 09:46:13 -07:00
https kubeadm join the cluster with pre-existing client certificate 2018-07-26 19:34:09 +08:00
token kubeadm: Split discovery from JoinConfiguration 2018-10-16 15:25:32 +03:00
BUILD Run hack/update-bazel.sh 2018-06-22 16:22:57 -07:00
discovery.go kubeadm: Split discovery from JoinConfiguration 2018-10-16 15:25:32 +03:00
discovery_test.go kubeadm: Split discovery from JoinConfiguration 2018-10-16 15:25:32 +03:00