// BootstrapTokens is respected at `kubeadm init` time and describes a set of Bootstrap Tokens to create.
BootstrapTokens[]BootstrapToken
// NodeRegistration holds fields that relate to registering the new master node to the cluster
// NodeRegistration holds fields that relate to registering the new control-plane node to the cluster
NodeRegistrationNodeRegistrationOptions
// LocalAPIEndpoint represents the endpoint of the API server instance that's deployed on this control plane node
...
...
@@ -208,7 +208,7 @@ type APIEndpoint struct {
BindPortint32
}
// NodeRegistrationOptions holds fields that relate to registering a new master or node to the cluster, either via "kubeadm init" or "kubeadm join"
// NodeRegistrationOptions holds fields that relate to registering a new control-plane or node to the cluster, either via "kubeadm init" or "kubeadm join"
typeNodeRegistrationOptionsstruct{
// Name is the `.Metadata.Name` field of the Node API object that will be created in this `kubeadm init` or `kubeadm joiń` operation.
...
...
@@ -220,7 +220,7 @@ type NodeRegistrationOptions struct {
CRISocketstring
// Taints specifies the taints the Node API object should be registered with. If this field is unset, i.e. nil, in the `kubeadm init` process
// it will be defaulted to []v1.Taint{'node-role.kubernetes.io/master=""'}. If you don't want to taint your master node, set this field to an
// it will be defaulted to []v1.Taint{'node-role.kubernetes.io/master=""'}. If you don't want to taint your control-plane node, set this field to an
// empty slice, i.e. `taints: {}` in the YAML file. This field is solely used for Node registration.
Taints[]v1.Taint
...
...
@@ -244,7 +244,7 @@ type Networking struct {
// TODO: The BootstrapToken object should move out to either k8s.io/client-go or k8s.io/api in the future
// (probably as part of Bootstrap Tokens going GA). It should not be staged under the kubeadm API as it is now.
typeBootstrapTokenstruct{
// Token is used for establishing bidirectional trust between nodes and masters.
// Token is used for establishing bidirectional trust between nodes and control-planes.
// Used for joining nodes in the cluster.
Token*BootstrapTokenString
// Description sets a human-friendly message why this token exists and what it's used
...
...
@@ -315,11 +315,11 @@ type ExternalEtcd struct {
typeJoinConfigurationstruct{
metav1.TypeMeta
// NodeRegistration holds fields that relate to registering the new master node to the cluster
// NodeRegistration holds fields that relate to registering the new control-plane node to the cluster
NodeRegistrationNodeRegistrationOptions
// CACertPath is the path to the SSL certificate authority used to
// secure comunications between node and master.
// secure comunications between node and control-plane.
// Defaults to "/etc/kubernetes/pki/ca.crt".
CACertPathstring
...
...
@@ -359,7 +359,7 @@ type Discovery struct {
// BootstrapTokenDiscovery is used to set the options for bootstrap token based discovery
typeBootstrapTokenDiscoverystruct{
// Token is a token used to validate cluster information
// fetched from the master.
// fetched from the control-plane.
Tokenstring
// APIServerEndpoint is an IP or domain name to the API server from which info will be fetched.
...
...
@@ -377,7 +377,7 @@ type BootstrapTokenDiscovery struct {
// APIEndpoint represents the endpoint of the instance of the API server to be deployed on this node.
...
...
@@ -144,7 +144,7 @@ type APIEndpoint struct {
BindPortint32`json:"bindPort"`
}
// NodeRegistrationOptions holds fields that relate to registering a new master or node to the cluster, either via "kubeadm init" or "kubeadm join"
// NodeRegistrationOptions holds fields that relate to registering a new control-plane or node to the cluster, either via "kubeadm init" or "kubeadm join"
typeNodeRegistrationOptionsstruct{
// Name is the `.Metadata.Name` field of the Node API object that will be created in this `kubeadm init` or `kubeadm joiń` operation.
...
...
@@ -156,7 +156,7 @@ type NodeRegistrationOptions struct {
CRISocketstring`json:"criSocket,omitempty"`
// Taints specifies the taints the Node API object should be registered with. If this field is unset, i.e. nil, in the `kubeadm init` process
// it will be defaulted to []v1.Taint{'node-role.kubernetes.io/master=""'}. If you don't want to taint your master node, set this field to an
// it will be defaulted to []v1.Taint{'node-role.kubernetes.io/master=""'}. If you don't want to taint your control-plane node, set this field to an
// empty slice, i.e. `taints: {}` in the YAML file. This field is solely used for Node registration.
Taints[]v1.Taint`json:"taints,omitempty"`
...
...
@@ -178,7 +178,7 @@ type Networking struct {
// BootstrapToken describes one bootstrap token, stored as a Secret in the cluster
typeBootstrapTokenstruct{
// Token is used for establishing bidirectional trust between nodes and masters.
// Token is used for establishing bidirectional trust between nodes and control-planes.
// Used for joining nodes in the cluster.
Token*BootstrapTokenString`json:"token"`
// Description sets a human-friendly message why this token exists and what it's used
...
...
@@ -251,18 +251,18 @@ type ExternalEtcd struct {
typeJoinConfigurationstruct{
metav1.TypeMeta`json:",inline"`
// NodeRegistration holds fields that relate to registering the new master node to the cluster
// NodeRegistration holds fields that relate to registering the new control-plane node to the cluster
// LocalAPIEndpoint represents the endpoint of the API server instance that's deployed on this control plane node
...
...
@@ -191,7 +191,7 @@ type APIEndpoint struct {
BindPortint32`json:"bindPort"`
}
// NodeRegistrationOptions holds fields that relate to registering a new master or node to the cluster, either via "kubeadm init" or "kubeadm join"
// NodeRegistrationOptions holds fields that relate to registering a new control-plane or node to the cluster, either via "kubeadm init" or "kubeadm join"
typeNodeRegistrationOptionsstruct{
// Name is the `.Metadata.Name` field of the Node API object that will be created in this `kubeadm init` or `kubeadm joiń` operation.
...
...
@@ -203,7 +203,7 @@ type NodeRegistrationOptions struct {
CRISocketstring`json:"criSocket,omitempty"`
// Taints specifies the taints the Node API object should be registered with. If this field is unset, i.e. nil, in the `kubeadm init` process
// it will be defaulted to []v1.Taint{'node-role.kubernetes.io/master=""'}. If you don't want to taint your master node, set this field to an
// it will be defaulted to []v1.Taint{'node-role.kubernetes.io/master=""'}. If you don't want to taint your control-plane node, set this field to an
// empty slice, i.e. `taints: {}` in the YAML file. This field is solely used for Node registration.
Taints[]v1.Taint`json:"taints,omitempty"`
...
...
@@ -225,7 +225,7 @@ type Networking struct {
// BootstrapToken describes one bootstrap token, stored as a Secret in the cluster
typeBootstrapTokenstruct{
// Token is used for establishing bidirectional trust between nodes and masters.
// Token is used for establishing bidirectional trust between nodes and control-planes.
// Used for joining nodes in the cluster.
Token*BootstrapTokenString`json:"token"`
// Description sets a human-friendly message why this token exists and what it's used
...
...
@@ -301,11 +301,11 @@ type ExternalEtcd struct {
typeJoinConfigurationstruct{
metav1.TypeMeta`json:",inline"`
// NodeRegistration holds fields that relate to registering the new master node to the cluster
// NodeRegistration holds fields that relate to registering the new control-plane node to the cluster
// TokenDescription flag sets the description of the token
TokenDescription="description"
// TLSBootstrapToken flag sets the token used to temporarily authenticate with the Kubernetes Master to submit a certificate signing request (CSR) for a locally created key pair
// TLSBootstrapToken flag sets the token used to temporarily authenticate with the Kubernetes Control Plane to submit a certificate signing request (CSR) for a locally created key pair
TLSBootstrapToken="tls-bootstrap-token"
// TokenDiscovery flag sets the token used to validate cluster information fetched from the API server (for token-based discovery)