Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
c46e9497
Commit
c46e9497
authored
Nov 12, 2018
by
Lubomir I. Ivanov
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
kubeadm: update the state in app/cmd.go
- BETA->GA - master->control-plane - exclude @ mentions as only members can use them
parent
8307fb2f
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
9 deletions
+8
-9
cmd.go
cmd/kubeadm/app/cmd/cmd.go
+8
-9
No files found.
cmd/kubeadm/app/cmd/cmd.go
View file @
c46e9497
...
...
@@ -37,32 +37,31 @@ func NewKubeadmCommand(in io.Reader, out, err io.Writer) *cobra.Command {
Use
:
"kubeadm"
,
Short
:
"kubeadm: easily bootstrap a secure Kubernetes cluster"
,
Long
:
dedent
.
Dedent
(
`
kubeadm: easily bootstrap a secure Kubernetes cluster.
┌──────────────────────────────────────────────────────────┐
│ KUBEADM IS CURRENTLY IN BETA │
| KUBEADM │
| Easily bootstrap a secure Kubernetes cluster |
│ │
│
But please, try it out and give us feedback at:
│
│
Please give us feedback at:
│
│ https://github.com/kubernetes/kubeadm/issues │
│ and at-mention @kubernetes/sig-cluster-lifecycle-bugs │
│ or @kubernetes/sig-cluster-lifecycle-feature-requests │
└──────────────────────────────────────────────────────────┘
Example usage:
Create a two-machine cluster with one master (which controls the cluster),
and one node (where your workloads, like Pods and Deployments run).
Create a two-machine cluster with one control-plane node
(which controls the cluster), and one worker node
(where your workloads, like Pods and Deployments run).
┌──────────────────────────────────────────────────────────┐
│ On the first machine: │
├──────────────────────────────────────────────────────────┤
│
master# kubeadm init
│
│
control-plane# kubeadm init
│
└──────────────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────────────┐
│ On the second machine: │
├──────────────────────────────────────────────────────────┤
│
node# kubeadm join <arguments-returned-from-init>
│
│
worker# kubeadm join <arguments-returned-from-init>
│
└──────────────────────────────────────────────────────────┘
You can then repeat the second step on as many other machines as you like.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment