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
746cc5d2
Commit
746cc5d2
authored
Feb 21, 2017
by
Shyam JVS
Committed by
GitHub
Feb 21, 2017
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #41800 from shyamjvs/fix-hollow-node-logging
Whitelist kubemark in node_ssh_supported_providers for log dump
parents
03837fe6
3bc6bf6b
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
log-dump.sh
cluster/log-dump.sh
+2
-2
No files found.
cluster/log-dump.sh
View file @
746cc5d2
...
...
@@ -34,7 +34,7 @@ else
fi
readonly
master_ssh_supported_providers
=
"gce aws kubemark"
readonly
node_ssh_supported_providers
=
"gce gke aws"
readonly
node_ssh_supported_providers
=
"gce gke aws
kubemark
"
readonly
master_logfiles
=
"kube-apiserver kube-scheduler rescheduler kube-controller-manager etcd etcd-events glbc cluster-autoscaler kube-addon-manager fluentd"
readonly
node_logfiles
=
"kube-proxy fluentd"
...
...
@@ -129,7 +129,7 @@ function save-logs() {
case
"
${
KUBERNETES_PROVIDER
}
"
in
gce|gke|kubemark
)
files
=
"
${
files
}
${
gce_logfiles
}
"
if
[[
"
${
KUBERNETES_PROVIDER
}
"
-eq
"kubemark"
&&
"
${
ENABLE_HOLLOW_NODE_LOGS
:-}
"
-eq
"true"
]]
;
then
if
[[
"
${
KUBERNETES_PROVIDER
}
"
==
"kubemark"
&&
"
${
ENABLE_HOLLOW_NODE_LOGS
:-}
"
==
"true"
]]
;
then
files
=
"
${
files
}
${
hollow_node_logfiles
}
"
fi
;;
...
...
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