Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Cluster Autoscaler entrypoint #42988

Merged
merged 1 commit into from Mar 14, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Expand Up @@ -27,9 +27,18 @@
"name": "cluster-autoscaler",
"image": "gcr.io/google_containers/cluster-autoscaler:v0.5.0-beta1",
"command": [
"/bin/sh",
"-c",
"./cluster-autoscaler --kubernetes=http://127.0.0.1:8080?inClusterConfig=f --v=4 {{params}} 1>>/var/log/cluster-autoscaler.log 2>&1"
"./run.sh",
"--kubernetes=http://127.0.0.1:8080?inClusterConfig=f",
"--v=4",
"--stderrthreshold=info",
"--write-status-configmap=true",
"{{params}}"
],
"env": [
{
"name": "LOG_OUTPUT",
"value": "/var/log/cluster-autoscaler.log"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious, can't this fill the container disk? What happens if this fills the disk?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is mounted from the machine disk. I guess that there is some log rotation policy for /var/logs on the master (but can doublecheck).

}
],
# TODO: Make resource requirements depend on the size of the cluster
"resources": {
Expand Down