Skip to content
This repository was archived by the owner on Apr 20, 2026. It is now read-only.

Release 1.17 rebase and cherry-pick from release-1.16.15-lyft.1#30

Merged
gongx merged 12 commits intorelease-1.17.17-lyft.1from
release-1.17-xuan-rebase
Sep 23, 2021
Merged

Release 1.17 rebase and cherry-pick from release-1.16.15-lyft.1#30
gongx merged 12 commits intorelease-1.17.17-lyft.1from
release-1.17-xuan-rebase

Conversation

@gongx
Copy link
Copy Markdown

@gongx gongx commented Sep 20, 2021

Pick:
fe822af legacy-cloud-providers/aws: add gp3 pvc support (#28)
03bd351 disable klog for cadvisor.GetDirFsInfo cache miss
6c8c3b4 sidecar: glog -> klog
4c01153 sidecar: kubelet: don't bother killing pods when non-sidecars are done
3efe7de sidecar: container ordered start/shutdown support
bd36566 remove unnecessary line
1ba9ec7 handle case where cpuacct is reset to 0 in a live container
6b95d62 do not consider exited containers when calculating nanocores
069517a pkg/kubelet: fix uint64 overflow when elapsed UsageCoreNanoSeconds exceeds 18446744073
8251b5f pkg/kubelet: fix 1.14 compat for container restore error text
137a81e pkg/kubelet: try restoring the container spec if its nil
cc1cb6f Allow metrics to be retrieved from CRI with CRI-O

Drop:
5924265 Merge pull request #26 from tomwans/release-1.16-lyft-cronjobfix
717d679 cronjob: handle invalid/unschedulable dates
5d4d00a make cronjobController sync period configurable via flag
ac7b61d add Job scheduled start time annotation
05e3010 create cronjob controller metrics
32a8844 fix missed starting deadline warning never being hit
709ab5b wrap table driven tests in t.Run to allow running individual tests (#17)
428e48e Check next cron schedules in a binary-search fashion

tomwans and others added 12 commits September 20, 2021 16:20
This change turns off the ability to completely kill pods when the
non-sidecars are done. This is useful for cronjobs, where the
non-sidecars finish work and exit, this code previously would clean up
the pod and its resources.

This feature was pulled in from kubernetes#75099.

This is a feature that sounds nice in practice, but its not what we
need. It seems to be a bit buggy since the Pod sandbox can
potentially be deleted and recreated during the liftime of the
Pod. That ain't good.
CRI-O properly implements the CRI interface, and therefore it is
capable of returning the container stats if being asked for.

There is no reason to keep CRI-O as a special use case that has to
be run with the legacy mode making kubelet using cadvisor on each
container.

This patch removes the hardcoded assumptions that CRI-O has cannot
handle to return containers stats through CRI.

Fixes kubernetes#73750

Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
We're not guaranteed that the pod passed in has the ContainerSpec
we're looking for. With this, we check if the pod has the container
spec, and if it doesn't, we try to recover it one more time.
* Add gp3 pvc support along with throughput and iops options
* aws-sdk-go rev'd from v1.16.26 to v1.38.42 to support gp3 provisioning
@gongx
Copy link
Copy Markdown
Author

gongx commented Sep 21, 2021

/ptal #compute

@gongx gongx merged commit 2b98636 into release-1.17.17-lyft.1 Sep 23, 2021
@gongx gongx deleted the release-1.17-xuan-rebase branch September 23, 2021 22:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants