This repository has been archived by the owner on Apr 3, 2023. It is now read-only.
forked from kubernetes/kubernetes
-
Notifications
You must be signed in to change notification settings - Fork 3
Merging upstream code for 1.12.9 release #23
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`elbv2.AddTags` doesn't seem to support assigning the same set of tags to multiple resources at once leading to the following error: Error adding tags after modifying load balancer targets: "ValidationError: Only one resource can be tagged at a time" This can happen when using AWS NLB with multiple listeners pointing to different node ports. When k8s creates a NLB it creates a target group per listener along with installing security group ingress rules allowing the traffic to reach the k8s nodes. Unfortunately if those target groups are not tagged, k8s will not manage them, thinking it is not the owner. This small changes assigns tags one resource at a time instead of batching them as before. Signed-off-by: Brice Figureau <brice@daysofwonder.com>
…re account operation use const for timeout value remove get azure accounts in the init process add lock for account init
add timeout for getAllStorageAccounts
If a iSCSI target is down while a volume is attached, reading from /sys/class/iscsi_host/host415/device/session383/connection383:0/iscsi_connection/connection383:0/address fails with an error. Kubelet should assume that such target is not available / logged in and try to relogin. Eventually, if such error persists, it should continue mounting the volume if the other paths are healthy instead of failing whole WaitForAttach().
add more logging info in detach disk add more logging for azure disk attach/detach
…ick-of-#74386-upstream-release-1.12 Automated cherry pick of kubernetes#74386: fix negative slice index error in keymutex
…pick-of-#74636-upstream-release-1.12 Automated cherry pick of kubernetes#74636: Remove reflector metrics as they currently cause a memory
apply fix for msi and fix test failure
Use Nginx as the DaemonSet image instead of the ServeHostname image. This was changed because the ServeHostname has a sleep after terminating which makes it incompatible with the DaemonSet Rolling Upgrade e2e test. In addition, make the DaemonSet Rolling Upgrade e2e test timeout a function of the number of nodes that make up the cluster. This is required because the more nodes there are, the longer the time it will take to complete a rolling upgrade. Signed-off-by: Alexander Brand <alexbrand09@gmail.com>
Always report 0 cpu/memory usage for exited containers to make metrics-server work as expect. Signed-off-by: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
…y-pick-of-#69895-upstream-release-1.12 Automated cherry pick of kubernetes#69895: Reduce cardinality of admission webhook metrics
while cleaning up ipvs mode. flushing iptable chains first and then remove the chains. this avoids trying to remove chains that are still referenced by rules in other chains. fixes kubernetes#70615
…er that requests any device plugin resource. If not, re-issue Allocate grpc calls. This allows us to handle the edge case that a pod got assigned to a node even before it populates its extended resource capacity.
…k-of-#74755-upstream-release-1.12 Automated cherry pick of kubernetes#74755: Revert kubelet to default to ttl cache secret/configmap
…pick-of-#74336-origin-release-1.12 Automated cherry pick of kubernetes#74336: cri_stats_provider: overload nil as 0 for exited containers
…ck-of-#72738-upstream-release-1.12 Automated cherry pick of kubernetes#72738: DaemonSet e2e: Update image and rolling upgrade test timeout
…pick-of-#74191-upstream-release-1.12 Automated cherry pick of kubernetes#74191: remove get azure accounts in the init process set timeout
…ck-of-#69631-upstream-release-1.12 Automated cherry pick of kubernetes#69631: use k8s.gcr.io/pause instead of kubernetes/pause
…k-of-#76675-upstream-release-1.12 Automated cherry pick of kubernetes#76675: Error when etcd3 watch finds delete event with nil prevKV
…ick-of-#76762-upstream-release-1.12 Automated cherry pick of kubernetes#76762: Pick up security patches for fluentd-gcp-scaler by upgrading
Make CreatePrivilegedPSPBinding reentrant so tests using it (e.g. DNS) can be executed more than once against a cluster. Without this change, such tests will fail because the PSP already exists, short circuiting test setup.
…-pick-of-#69828-upstream-release-1.12 Automated cherry pick of kubernetes#69828: Make CreatePrivilegedPSPBinding reentrant
…k-of-#76788-upstream-release-1.12 Automated cherry pick of kubernetes#76788: Test kubectl cp escape
…-pick-of-#77224-upstream-release-1.12 Automated cherry pick of kubernetes#77224: Upgrade Stackdriver Logging Agent addon image from 1.6.0 to
…-of-#77656-upstream-release-1.12 Automated cherry pick of kubernetes#77656: check if Memory is not nil for container stats
…ates world-writeable cached schema files
…ick-of-#77874-github-release-1.12 Automated cherry pick of kubernetes#77874: fix CVE-2019-11244: `kubectl --http-cache=<world-accessible
…pick-of-#77613-upstream-release-1.12 Automated cherry pick of kubernetes#77613 upstream release 1.12
…y-pick-of-#77619-upstream-release-1.12 Automated cherry pick of kubernetes#77619: In GuaranteedUpdate, retry on any error if we are working
…pick-of-#77722-upstream-release-1.12 Automated cherry pick of kubernetes#77722: fix incorrect prometheus metrics
…k-of-#78029-upstream-release-1.12 Automated cherry pick of kubernetes#78029: Terminate watchers when watch cache is destroyed
Kubernetes official release v1.12.9
jadarsie
approved these changes
May 30, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merging upstream code for 1.12.9 release
Testing in progress.