This repository has been archived by the owner on Apr 3, 2023. It is now read-only.
feat: Add K8s 1.13.8 payload for Azure Stack. #27
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>
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().
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>
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.
…pick-of-#74636-upstream-release-1.13 Automated cherry pick of kubernetes#74636: Remove reflector metrics as they currently cause a memory
…k-of-#73968-upstream-release-1.13 Automated cherry pick of kubernetes#73968: record event on endpoint update failure
…y-pick-of-#74371-upstream-release-1.13 Automated cherry pick of kubernetes#74371: add health plugin in the DNS tests
Rebase docker image on debian-base:0.4.1
…ata from metadata.
This is a cherrypick of the following commit https://github.com/kubernetes/kubernetes/pull/74290/commits
This is to deal with the flaky session affinity test.
Bump ip-masq-agent version to v2.3.0
1.13: Fix incorrect procMount defaulting
…pick-of-#75234-upstream-release-1.13 Automated cherry pick of kubernetes#75234: fix flexvol stuck issue due to corrupted mnt point
…pick-of-#78700-upstream-release-1.13 Automated cherry pick of kubernetes#78700: fix: update vm if detach a non-existing disk
…-pick-of-#78999-origin-release-1.13 Automated cherry pick of kubernetes#78999: ipvs: fix string check for IPVS protocol during graceful
If kubelet never gets past sandbox creation (i.e., never attempted to create containers for a pod), it should retry the sandbox creation on failure, regardless of the restart policy of the pod.
…oad-balancer-resource-group is empty string
This commit has the following changes: - Replace `bitbucket.org/ww/goautoneg` with `github.com/munnerz/goautoneg`. - Replace `bitbucket.org/bertimus9/systemstat` with `github.com/nikhita/systemstat`. - Bump kube-openapi to remove so that it's dependency on `bitbucket.org/ww/goautoneg` moves to `github.com/munnerz/goautoneg`. - Generate `swagger.json` generated from the above change. - Update `BUILD` files. Bitbucket is replaced with GitHub because: Atlassian finally pulled the plug on their 1.0 api and forces everyone to use 2.0 now: https://developer.atlassian.com/cloud/bitbucket/deprecation-notice-v1-apis/ This leads to an error like: ``` godep: error downloading dep (bitbucket.org/ww/goautoneg): https://api.bitbucket.org/1.0/repositories/ww/goautoneg: 410 Gone ``` This was fixed in upstream go in golang/tools@13ba8ad. To fix this in k/k: 1) We'll need to either bump our vendored version https://github.com/kubernetes/kubernetes/blob/release-1.13/vendor/golang.org/x/tools/go/vcs/vcs.go#L676. However, this bump brings in _lots_ of changes. 2) We can entirely remove our dependency on bitbucket. The second point is better because: 1) godep itself vendors in an older version: https://github.com/tools/godep/blob/master/vendor/golang.org/x/tools/go/vcs/vcs.go#L667. This means that anyone who installs godep directly, without forking it, will not be able to use it with Kubernetes if we stick to bitbucket. 2) Bumping `golang/x/tools` requires running `godep restore`, which doesn't work because that uses the 1.0 api...leading to a catch-22 like situation.
[1.13] Replace bitbucket with github to fix godep error
…ick-of-#78313-upstream-release-1.13 Automated cherry pick of kubernetes#78313: Avoid the default server mux
…ck-of-#79451-upstream-release-1.13 Automated cherry pick of kubernetes#79451: kubelet: retry pod sandbox creation when containers were
…ck-of-#79514-upstream-release-1.13 Automated cherry pick of kubernetes#79514: Default resourceGroup should be used when value of annotation
…root directory symbolically links to another device's directory
…ostname addresses on Node
This fixes the issue where "childFD" from syscall.Openat is assigned to a local variable inside the for loop, instead of the correct one in the function scope. This results in that when trying to close the "childFD" in the function scope, it will be equal to "-1", instead of the correct value.
current scale. Two important ones are when missing metrics might change the direction of scaling, and when the recommended scale is within tolerance of the current scale. The way that ReplicaCalculator signals it's desire to not change the current scale is by returning the current scale. However the current scale is from scale.Status.Replicas and can be larger than scale.Spec.Replicas (e.g. during Deployment rollout with configured surge). This causes a positive feedback loop because scale.Status.Replicas is written back into scale.Spec.Replicas, further increasing the current scale. This PR fixes the feedback loop by plumbing the replica count from spec through horizontal.go and replica_calculator.go so the calculator can punt with the right value.
Cherry pick kubernetes#79035 to 1.13 (Fix HPA feedback from writing status.replicas to spec.replicas)
…k-of-#79094-up-release-1.13 Automated cherry pick of kubernetes#79094: fix kubelet can not delete orphaned pod directory when "/var/lib/kubelet/pods" directory symbolically links to another device's directory
…k-of-#79446-upstream-release-1.13 Automated cherry pick of kubernetes#79446: Fix AWS DHCP option set domain names causing garbled
…k-of-#79534-upstream-release-1.13 Automated cherry pick of kubernetes#79534: Fix closing of dirs in doSafeMakeDir
…-pick-of-#79731-upstream-release-1.13 Automated cherry pick of kubernetes#79731: edit google dns hostname
Kubernetes official release v1.13.8
jadarsie
approved these changes
Jul 11, 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.
feat: Add K8s 1.13.8 payload for Azure Stack.