9cd2443e04
Cluster-autoscaler: FAQ improvement
2017-04-07 14:12:44 +02:00
08776f7e6c
Merge pull request https://github.com/kubernetes/contrib/pull/2530 from mwielgus/ubuntu-slim-bump
...
Cluster-autoscaler: ubuntu slim version bump
2017-04-07 10:10:31 +02:00
3c05e20e18
Merge pull request https://github.com/kubernetes/contrib/pull/2529 from mwielgus/faq4
...
Automatic merge from submit-queue
Cluster-autoscaler: add HPA and performance questions to FAQ
cc: @MaciekPytel @fgrzadkowski
2017-04-06 04:41:22 -07:00
f726f19cbf
Cluster-autoscaler: ubuntu slim version bump
2017-04-06 13:40:40 +02:00
9eed534a7a
Cluster-autoscaler: add HPA and performance questions to FAQ
2017-04-06 13:19:55 +02:00
0fa6a8d980
Merge pull request https://github.com/kubernetes/contrib/pull/2528 from mwielgus/faq3
...
Automatic merge from submit-queue
Cluster-autoscaler: rename FAQ
For some reason in the previous PR the name was not changed.
2017-04-06 04:03:20 -07:00
47a2727c5c
Cluster-autoscaler: rename FAQ
2017-04-06 12:05:34 +02:00
963440dfa0
Merge pull request https://github.com/kubernetes/contrib/pull/2526 from mwielgus/faq2
...
Cluster-autoscaler: readme reorg
2017-04-06 12:02:32 +02:00
ca3d6db9e2
Cluster-autoscaler: readme reorg
2017-04-06 11:42:11 +02:00
acde27f64b
Merge pull request https://github.com/kubernetes/contrib/pull/2524 from mwielgus/faq
...
Automatic merge from submit-queue
Cluster-autoscaler: Frequently Asked Questions
cc: @MaciekPytel @fgrzadkowski
2017-04-05 06:09:11 -07:00
081fcd6b84
Cluster-autoscaler: Frequently Asked Questions
2017-04-05 14:55:00 +02:00
32bfacd511
Merge pull request https://github.com/kubernetes/contrib/pull/2522 from mwielgus/readme-2
...
Automatic merge from submit-queue
Cluster-autoscaler: improve readme
cc: @fgrzadkowski @MaciekPytel
2017-04-05 01:44:07 -07:00
2ed1203e42
Cluster-autoscaler: improve readme
2017-04-04 21:53:06 +02:00
6a28643880
Merge pull request https://github.com/kubernetes/contrib/pull/2509 from mwielgus/aws_doc_fix
...
Automatic merge from submit-queue
Cluster-autoscaler: update aws doc with --stderrthreshold=info flag
cc: @andrewsykim @MaciekPytel
ref: #2500
2017-03-29 23:31:15 -07:00
760477c96c
Cluster-autoscaler: update aws doc with --stderrthreshold=info flag
2017-03-29 23:47:20 +02:00
2c2b54ee8e
Merge pull request https://github.com/kubernetes/contrib/pull/2506 from MaciekPytel/ca_status_cleanup
...
Automatic merge from submit-queue
Cluster-Autoscaler: make status less confusing
Previously min and max in status were refering to
non-obvious internal variables, which was pretty confusing.
2017-03-29 00:49:30 -07:00
bf9b6ce203
Cluster-Autoscaler: make status less confusing
...
Previously min and max in status were refering to
non-obvious internal variables, which was pretty confusing.
2017-03-28 13:31:12 +02:00
6d841cbf17
Merge pull request https://github.com/kubernetes/contrib/pull/2505 from mwielgus/v0.5.1
...
Automatic merge from submit-queue
Bump cluster autoscaler to 0.5.1
cc: @MaciekPytel @fgrzadkowski
2017-03-28 04:22:23 -07:00
8f465e588f
Bump cluster autoscaler to 0.5.1
2017-03-28 12:49:04 +02:00
d236c1d61d
Merge pull request https://github.com/kubernetes/contrib/pull/2504 from MaciekPytel/ca_scaleup_status_fix
...
Automatic merge from submit-queue
Cluster-Autoscaler: fix scaleup status reporting
This fixes https://github.com/kubernetes/contrib/issues/2503
2017-03-28 03:14:19 -07:00
28b40c45db
Cluster-Autoscaler: fix scaleup status reporting
...
Previously the cluster would move to NoActivity too quickly
(before new nodes were actually ready).
2017-03-28 11:58:56 +02:00
6c991c8465
Merge pull request https://github.com/kubernetes/contrib/pull/2502 from mwielgus/ca-starting-fix
...
Automatic merge from submit-queue
Cluster-autoscaler: Fix isNodeStarting
Fix for: https://github.com/kubernetes/kubernetes/issues/43709
cc: @MaciekPytel @fgrzadkowski
2017-03-28 01:14:45 -07:00
eb3e6173d1
Cluster-autoscaler: Fix isNodeStarting
2017-03-27 23:27:14 +02:00
f8ca11f223
Merge pull request https://github.com/kubernetes/contrib/pull/2499 from diwu1989/patch-1
...
Automatic merge from submit-queue
fix typo consumig
2017-03-27 01:20:23 -07:00
2ee2a1c598
Merge pull request https://github.com/kubernetes/contrib/pull/2496 from mwielgus/compatibility
...
Automatic merge from submit-queue
Cluster-autoscaler: add information about which version is supported in which k8s
cc: @andrewsykim @MaciekPytel @fgrzadkowski
2017-03-27 01:11:51 -07:00
971ca5049b
Cluster-autoscaler: add information about which version is supported in which k8s
2017-03-27 09:58:58 +02:00
0499a09de5
fix typo consumig
2017-03-26 13:12:00 -07:00
35ec57437d
Merge pull request https://github.com/kubernetes/contrib/pull/2488 from MaciekPytel/ca_reset_on_cluster_failure
...
Automatic merge from submit-queue
Cluster-Autoscaler: reset unneededNodes list on cluster failure
If the nodes is marked as unneeded and cluster goes to an unhealthy state shortly after the node will likely be deleted immediately on cluster recovery. This is because there is already an entry for it in unnededNodes datastructure and the cluster downtime is counted towards node being unneeded time.
It's not 100% obvious to me what should happen in this case, but I think it's better to play it safe and just wait the full 10 minutes after cluster recovery before we start to delete nodes. After a quick glance at the code I haven't spotted any other stuff that needs to be cleaned up in case of cluster failure, but maybe you have some other ideas @mwielgus?
2017-03-23 06:40:24 -07:00
72c885b800
Cluster-Autoscaler: reset scale-down on unready cluster
2017-03-22 17:17:59 +01:00
9395dbaccd
Merge pull request https://github.com/kubernetes/contrib/pull/2485 from mwielgus/0.5.0
...
Automatic merge from submit-queue
Cluster-autoscaler: bump version to 0.5.0
cc: @MaciekPytel @fgrzadkowski @jszczepkowski
2017-03-21 07:25:11 -07:00
bfde563911
Cluster-autoscaler: bump version to 0.5.0
2017-03-21 15:11:13 +01:00
314b811300
Merge pull request https://github.com/kubernetes/contrib/pull/2479 from MaciekPytel/ca_defer_statusmap
...
Automatic merge from submit-queue
Cluster-Autoscaler: update status configmap on errors
Previously it would only update after successfully completing the main
loop, meaning the status wouldn't get updated unless cluster was
healthy.
2017-03-15 08:39:35 -07:00
c71668a8d8
Cluster-Autoscaler: update status configmap on errors
...
Previously it would only update after successfully completing the main
loop, meaning the status wouldn't get updated unless cluster was
healthy.
2017-03-15 13:22:24 +01:00
41d3292456
Merge pull request https://github.com/kubernetes/contrib/pull/2478 from mwielgus/v0.5.0-beta2
...
Automatic merge from submit-queue
Cluster-autoscaler: bump version to 0.5.0-beta2
cc: @MaciekPytel @jszczepkowski @fgrzadkowski
2017-03-15 04:36:29 -07:00
ac5f7634d8
Merge pull request https://github.com/kubernetes/contrib/pull/2464 from MaciekPytel/ca_drain_evictions
...
Automatic merge from submit-queue
Cluster-Autoscaler: evict pods instead of deleting them
This should make CA respect PodDisruptionBudget.
2017-03-15 04:27:27 -07:00
d953213592
Cluster-autoscaler: bump version to 0.5.0-beta2
2017-03-15 12:21:14 +01:00
6f727fe2e0
Merge pull request https://github.com/kubernetes/contrib/pull/2475 from MaciekPytel/ca_unready_status_fix
...
Automatic merge from submit-queue
Cluster-Autoscaler: consider node with unknown readiness unready
Node with non-responsive kubelet seems to be marked as NodeReady: Unknown, which is currently considered as ready by CA.
2017-03-15 03:32:24 -07:00
1590789292
Cluster-Autoscaler: "unknown" readiness -> unready
2017-03-15 11:16:17 +01:00
624be93a55
Merge pull request https://github.com/kubernetes/contrib/pull/2472 from MaciekPytel/ca_fix_e2e
...
Automatic merge from submit-queue
Cluster-autoscaler: fix NotTriggerScaleUp event
This should fix a failing e2e test.
Also updated some scale_up unittests to check created events and fixed a typo in variable name.
2017-03-14 11:18:44 -07:00
7d5488898c
Cluster-autoscaler: fix NotTriggerScaleUp event
...
This should fix a failing e2e test
2017-03-14 14:54:36 +01:00
97370ea02c
Merge pull request https://github.com/kubernetes/contrib/pull/2471 from MaciekPytel/ca_fix_segfault
...
Automatic merge from submit-queue
Cluster-Autoscaler: handle nil node group
In a few place we assumed it's not-nil, leading to segfaults.
2017-03-13 09:14:15 -07:00
10d560dae6
Cluster-Autoscaler: handle nil node group
...
In a few place we assumed it's not-nil, leading
to segfaults.
2017-03-13 14:46:11 +01:00
39162f0860
Cluster-Autoscaler: evict pods instead of deleting them
2017-03-10 16:18:47 +01:00
cff33b2505
Merge pull request https://github.com/kubernetes/contrib/pull/2463 from MaciekPytel/ca_fix_deletaint
...
Automatic merge from submit-queue
Cluster-Autoscaler: fix delete taint failing
It was using old node version (which in general is always going to be outdated, as we've likely modified it by adding delete taint).
@mwielgus
2017-03-10 05:35:36 -08:00
0379a73828
Cluster-Autoscaler: fix delete taint failing
2017-03-10 12:02:52 +01:00
b171566401
Merge pull request https://github.com/kubernetes/contrib/pull/2461 from mwielgus/lister-fix
...
Automatic merge from submit-queue
Cluster-autoscaler: ready node lister fix
cc: @MaciekPytel @jszczepkowski
2017-03-09 08:32:45 -08:00
95bad10311
Cluster-autoscaler: ready node lister fix
2017-03-09 19:18:49 +03:00
7fcab2d18e
Merge pull request https://github.com/kubernetes/contrib/pull/2460 from mwielgus/pdb-typo
...
Automatic merge from submit-queue
Cluster-autoscaler: fix typo in pdb listener
cc: @MaciekPytel @jszczepkowski
2017-03-09 07:53:12 -08:00
eb257e5713
Merge pull request https://github.com/kubernetes/contrib/pull/2459 from MaciekPytel/ca_fix_deletetaint
...
Automatic merge from submit-queue
Cluster-Autoscaler: fix delete taint value format
Fix a bug, where non-compliant value format prevented CA deletetaint from being created (which in turn caused CA node drain to fail).
2017-03-09 07:43:10 -08:00
10f848b049
Cluster-autoscaler: fix typo in pdb listener
2017-03-09 18:38:50 +03:00
Marcin Wielgus