getting single node to work. #12
Closed
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
Update to golang 1.10.4
Manifest kubernetes infra images
Revert "#67504: Decrease CPU requests of master components in two times."
- Update Alpine base image to 3.8.1. - Build multi-arch images correctly.
closes kubernetes/kubeadm#1132 Signed-off-by: Chuck Ha <ha.chuck@gmail.com>
Signed-off-by: Timothy St. Clair <timothysc@gmail.com>
Remove etcd 3.2.18 from the etcd image
A previous commit updated 17.xx -> 18.xx without considering that some systems still use 17.xx. Add handling for 17.0[3,6,9] as validated versions. Also re-format the error message because the version is not validated per maximum basis, but rather based on existing validation.
Remove feature tag from ScheudulerPreemption e2e tests
Signed-off-by: Da K. Ma <klaus1982.cn@gmail.com>
Update kubeadm v1alpha3 example configuration
Refactor grpc dial with dialcontext
Bump kube-dns to 1.14.13
Fix nodes power state on Azure
Fix node label assignment for GCE k8s clusters.
Autoscaler e2e tests use allocatable to calculate resources
Use the v1.12 branch by default
Coerce componentconfig/v1alpha1 KubeSchedulerConfiguration to kubescheduler.config.k8s.io/v1alpha1
Removed taint check as DaemonSet tolerates default taints.
kubeadm: fix broken Docker 17.xx validation
Bootstrap initializes the necessary vSphere objects before the tests are run. A call to Bootstrap was missing in persistent_volumes-vsphere.go's BeforeEach. This results in Panic while running e2e tests for 'vsphere' provider with a stack trace like this: /usr/local/go/src/runtime/panic.go:502 +0x229 github.com/docker/kube-e2e-image/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere.glob..func1.1() /go/src/github.com/docker/kube-e2e-image/vendor/k8s.io/kubernetes/test/e2e/storage/vsphere/persistent_volumes-vsphere.go:77 +0xa21 github.com/docker/kube-e2e-image/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc4217c9b60, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /go/src/github.com/docker/kube-e2e-image/e2e_test.go:88 +0x2c8 testing.tRunner(0xc4206e01e0, 0x4212900) /usr/local/go/src/testing/testing.go:777 +0xd0 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:824 +0x2e0 This change fixes the Panic by calling Bootstrap. Testing: After this change, tests with FOCUS set to "PersistentVolumes:vsphere" dont Panic. They pass as expected. Signed-off-by: Anusha Ragunathan <anusha.ragunathan@docker.com>
cluster/gce and test/: update etcd:3.2.24-0 image to etcd:3.2.24-1
Both SharedIndexInformer and threadSafeMap were changed to allow AddIndexers to be called after a start or items are in the cache. While a new Indexer is being added handling deltas is blocked in the informer. When a new Indexer is added to a cache with existing items all indices are recalculated. One point to note is that adding a new indexer on a started informer will case all indexes to be rebuilt, but it will not trigger an updateNotification. This is done because it is impractical to assume any existing ResourceEventHandler would have knowledge of a yet to be added index. Any ResourceEventHandler that would need to consume this new index should be added after the new Indexer is added.
If a 101 response is not seen the connection has not been fully upgraded. In this situation do not start the copy loop and only write the HTTP response and exit.
ibuildthecloud
force-pushed
the
master
branch
from
854b0c7
to
17a44a3
Compare
1 task
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.
trying to get a single node to work and here is what I had to change.