github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
37,784 Commits
32 Branches
881 Tags
633 MiB
Commit Graph

13 Commits (33ebe1f18b9cf5909931376f656e19e80ac9ac1c)

Author SHA1 Message Date
Kubernetes Submit Queue f79a53a734 Merge pull request #31777 from dshulyak/evict_pet 
Automatic merge from submit-queue

Delete evicted pet

If pet was evicted by kubelet - it will stuck in this state forever.
By analogy to regular pod we need to re-create pet so that it will
be re-scheduled to another node, so in order to re-create pet
and preserve consitent naming we will delete it in petset controller
and create after that.

fixes: https://github.com/kubernetes/kubernetes/issues/31098
 2016-10-04 01:32:02 -07:00
Maciej Kwiek 0bec588202 PetSet returns valid replica count in status 
If the first pod is not healthy and next pods are not yet created, do
not provide the status with incorrect replica count
 2016-09-27 10:58:26 +02:00
Dmitry Shulyak c0981963d9 Verify evicted pods managed by petset controller will be recreated 
Spawn pet set with single replica and simple pod. They will have
conflicting hostPort definitions, and spawned on the same node.

As the result pet set pod, it will be created after simple pod, will be
in Failed state. Pet set controller will try to re-create it. After
verifying that pet set pod failed and was recreated atleast once, we will
remove pod with conflicting hostPort and wait until pet set pod will be in
running state.

Change-Id: I5903f5881f8606c696bd390df58b06ece33be88a
 2016-09-21 12:03:11 +03:00
deads2k b83a317003 switch controller manager to generated clientset 2016-09-20 12:53:47 -04:00
d00369826 3de4695057 fix petset update(pet) retries bug 
Change-Id: I92e2b653ab78fca72ae41cf87945d90fbbc67f44
 2016-09-20 11:35:58 +08:00
Kubernetes Submit Queue 2462f43798 Merge pull request #32030 from m1093782566/m109-clean-get-pet-code 
Automatic merge from submit-queue

[Pet Set] Fix logical breaking of apiServerPetClient.Get(*pcb)

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**:

addresses #32031
 2016-09-11 22:49:40 -07:00
m1093782566 13ce13664d always return false if error not nil in Get(pcb) 
Change-Id: I37bd4d8948a8a5c0017966958547904595b28119
 2016-09-08 10:25:54 +08:00
m1093782566 7dd675ef32 clean up pet set code 
Change-Id: I60562bb1aa44436a23cfc5e50d6037adcce417c6
 2016-09-03 21:28:46 +08:00
Dmitry Shulyak 200f8c5c39 Delete evicted pet 
If pet was evicted by kubelet - it will stuck in this state forever.
By analogy to regular pod we need to re-create pet so that it will
be re-scheduled to another node, so in order to re-create pet
and preserve consitent naming we will delete it in petset controller
and create after that.

Change-Id: Ib98bf7f34b3f2ab1582b9de34b5f4c5f84cd5215
 2016-08-31 14:41:10 +03:00
Anirudh 467333cc40 Create event only if creation of PVC failed. 2016-07-14 11:53:42 -07:00
David McMahon ef0c9f0c5b Remove "All rights reserved" from all the headers. 2016-06-29 17:47:36 -07:00
Prashanth Balasubramanian 377957a173 PetSet doesn't scale if it finds unready pets 2016-05-10 13:03:28 -07:00
Prashanth Balasubramanian 6bc3052551 PetSet alpha controller 2016-05-04 18:39:17 -07:00