Rebase 1.19.0 beta.0 #145
Merged
Rebase 1.19.0 beta.0 #145
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
improve error logging on e2e pod create function
Improving EndpointSlice tests
…l-lowercase Ensure the server FQIN is stored and searched in lowercase (vsphere)
Improves unittest codecoverage for azure_securitygroupclient
proxy: followup to last-queued-change metric
Ingress validation
We should read and verify the data before actually closing the connection to avoid connection based-races within the test. Signed-off-by: Sascha Grunert <sgrunert@suse.com>
…ests Add tests for KubeletConfig
…rage Fix date race in storage tests
fix some fixture path calculations
base-images: Update to kube-cross:v1.13.9-5
…er-fixup service controller: clean up unit tests
…eview Indicate node authorizer does not support rule resolution
…d-member-add kubeadm: fix flakes when performing etcd MemberAdd on slower setups
ginkgo has a weird bug that - AfterEach does not get called when testsuite exits with certain kind of interrupt (Ctrl-C for example). More info - onsi/ginkgo#222 We workaround this issue in Kubernetes by adding a special hook into AfterSuite call, but AfterSuite can not be used to peforms certain kind of cleanup because it can race with AfterEach hook and framework.AfterEach hook will set framework.ClientSet to nil. This presents a problem in cleaning up CSI driver and testpods. This PR removes cleanup of driver manifest via CleanupAction because that is not safe and racy (such as f.ClientSet may disappear!) and makes AfterSuite hooks run in a ordered fashion
Signed-off-by: Aldo Culquicondor <acondor@google.com>
In case two or more controllers share the informers created through InitTestScheduler, it's not safe to start the informers until all controllers set their informer indexers. Otherwise, some controller might fail to register their indexers in time. Thus, it's responsibility of each consumer to make sure all informers are started after all controllers had time to get initiliazed.
Promote GlobalAccess for GCE Internal Loadbalancers to GA
…affic ensure that when a pod servicing UDP traffic is deleted the conntrack entries are cleaned up and another backend can pick up the traffic with minimal interruption When using NodePort services and long running connections that on pod deletion stale conntrack entries can halt the flow of traffic. Add a test case to check that conntrack entries are cleaned up.
Switch to use AzureFile management SDK
Deprecating Kubelet not used testing flags
Origin-commit: 131dbb4770bb3bed0c07d2a6ca0cbe4cba2556bb
This line makes the upgrade log output unreadable and provides
no value during the set of tests it's used in:
```
Jan 12 20:49:25.628: INFO: cluster upgrade is Progressing: Working towards registry.svc.ci.openshift.org/ci-op-jbtg7jjb/release@sha256:144e73d125cce620bdf099be9a85225ade489a95622a70075d264ea3ff79219c: downloading update
Jan 12 20:49:26.692: INFO: Poke("http://a74e3476115ce4d2d817a1e5ea608dad-802917831.us-east-1.elb.amazonaws.com:80/echo?msg=hello"): success
Jan 12 20:49:28.727: INFO: Poke("http://a74e3476115ce4d2d817a1e5ea608dad-802917831.us-east-1.elb.amazonaws.com:80/echo?msg=hello"): success
```
Origin-commit: 1cdf04c0e15b79fad3e3a6ba896ed2bb3df42b78
…o function Origin-commit: 0d7fb2d769d631054ec9ac0721aee623c96c1001
Origin-commit: cb0b340d0e68c9524fa7fd6277f571b6aa68bf86
The following packages have tests that exceed the default 120s timeout: k8s.io/kubernetes/pkg/kubelet/volumemanager/reconciler - The tests in this package collectively take longer than 120s. k8s.io/kubernetes/pkg/volume/csi - One of the unit tests has to wait 2 minutes for a timeout to validate its failure condition.
… secret This patch brings back the downstream changes that were introduced to allow reading openstack cloud provider config from a secret. They are available in release-4.4, but were reverted in master with openshift/origin#24719 This change includes: - Ability to read metadata values for kubelet. Since the service does not have access to the secret to read the configuration, but it needs data to download (e.g. hostname or flavor), we are trying to get it from the metadata server. - Deprecation of kubeConfig parameter. Now we read the file that was provided with --kubeconfig option. Origin-commit: f95edc26155a29769b3c5b80c03755a01a87b5fc
Also fix the install path to be relative.
…nodes In 16443 a set of changes were made to enable service load balancers for Kube 1.1 and GCP to exclude unschedulable nodes from load balancer pools. However, Unschedulable has nothing to do with whether nodes should host service load balancer pods - the act of preventing new pods from landing on a node has no impact on existing workloads. In general nodes are not special, and a user who wants to exclude otherwise healthy nodes can use the beta service load balancer label to exclude the node from the LB pool. This commit removes the check for unschedulable nodes from the LB pool. Origin-commit: 0d1e1e134816f678234d884d0457e7ef1da510d2
…oken secrets Previously the serving service CA was added to token secrets by default. This commit changes the addition to be disabled by default and optionally enabled by setting ADD_SERVICE_SERVING_CA_TO_TOKEN_SECRETS=true in the environment. Origin-commit: f24fbff3f692fe13ed7f229ddfa47dca6828e79d
…anage Origin-commit: 59d4df02ece2eeeb7701c3b09c8e0a3f59198b56
…ndler chain Origin-commit: 5772e7285acbe901762d8cd8cb1fc33d8b459d04
Origin-commit: ea5a6809e96cef1c6a9fe99caeda9db6e31f6962
openshift-ci-robot
added
area/dependency
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: marun The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
do-not-merge/invalid-owners-file
|
The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the openshift org. You can then trigger verification by writing
|
|
@marun: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.