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
f90cbed4
Commit
f90cbed4
authored
Mar 01, 2019
by
Darren Shepherd
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Apply suggestions from code review
Thanks for review. I don't know how these spelling errors have slipped in. :-) Co-Authored-By:
toomyem
<
toomyem@toomyem.net
>
parent
0b8d7c86
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
README.md
README.md
+2
-2
No files found.
README.md
View file @
f90cbed4
...
...
@@ -89,10 +89,10 @@ of that file as `NODE_TOKEN` and then run the agent as follows
That's it.
Accessing cluser from outside
Accessing clus
t
er from outside
-----------------------------
Copy
file
`/etc/rancher/k3s/k3s.yaml`
your machine located outside the cluster as
`~/.kube/config`
. Then edit it and replace
Copy
the file
`/etc/rancher/k3s/k3s.yaml`
on
your machine located outside the cluster as
`~/.kube/config`
. Then edit it and replace
"localhost" with the IP or name of the k3s server. Now you can use
`kubectl`
to manage your k3s cluster.
Auto-deploying manifests
...
...
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