Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
H
helm3
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
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
go
helm3
Commits
c316193a
Commit
c316193a
authored
Feb 05, 2018
by
Matthew Fisher
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
remove references to the term "master"
parent
add98dab
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
6 additions
and
6 deletions
+6
-6
charts_tips_and_tricks.md
docs/charts_tips_and_tricks.md
+1
-1
install_faq.md
docs/install_faq.md
+5
-5
No files found.
docs/charts_tips_and_tricks.md
View file @
c316193a
...
...
@@ -204,7 +204,7 @@ together in one GitHub repository.
**Deis's [Workflow](https://github.com/deis/workflow/tree/master/charts/workflow):**
This chart exposes the entire Deis PaaS system with one chart. But it's different
from the SAP chart in that this
master
chart is built from each component, and
from the SAP chart in that this
umbrella
chart is built from each component, and
each component is tracked in a different Git repository. Check out the
`requirements.yaml`
file to see how this chart is composed by their CI/CD
pipeline.
...
...
docs/install_faq.md
View file @
c316193a
...
...
@@ -106,12 +106,12 @@ Error: Error forwarding ports: error upgrading connection: dial tcp: lookup kube
A: We have seen this issue with Ubuntu and Kubeadm in multi-node clusters. The
issue is that the nodes expect certain DNS records to be obtainable via global
DNS. Until this is resolved upstream, you can work around the issue as
follows:
follows
. On each of the control plane nodes
:
1) Add entries to
`/etc/hosts`
on the master
mapping your hostnames to their public IPs
2) Install
`dnsmasq`
on the master
(e.g.
`apt install -y dnsmasq`
)
3)
Kill the k8s api server container on mast
er (kubelet will recreate it)
4) Then
`systemctl restart docker`
(or reboot the
master
) for it to pick up the /etc/resolv.conf changes
1) Add entries to
`/etc/hosts`
,
mapping your hostnames to their public IPs
2) Install
`dnsmasq`
(e.g.
`apt install -y dnsmasq`
)
3)
Remove the k8s api server contain
er (kubelet will recreate it)
4) Then
`systemctl restart docker`
(or reboot the
node
) for it to pick up the /etc/resolv.conf changes
See this issue for more information: https://github.com/kubernetes/helm/issues/1455
...
...
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