forked from kubernetes/kubernetes
-
Notifications
You must be signed in to change notification settings - Fork 0
Sync the main kubernetes master [FUTURE PURPOSE] #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
cymtrick
wants to merge
10,000
commits into
cymtrick:master
Choose a base branch
from
kubernetes:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or 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 CNI plugins to v1.8.0
add events.events.k8s.io to clusterrole view/edit default
…-options client-go/dynamic/fake: Stop ignoring options
kubelet: poll after reloading logind conf
Listing all keys from etcd turned out to be too expensive, negativly impacting events POST latency. Events resource is the only resource that by default has watch cache disabled and which includes very large number of small objects making it very costly to list keys. Expected impact: * No apiserver_resource_size_estimate_bytes metric for events. * APF overestimating LIST request cost to events. Fallback assumes object size of 1.5MB, meaning LIST events will always get maxSeats
kubelet: Migrate pkg/kubelet/pluginmanager to contextual logging
…mate Disable estimating resource size for resources with watch cache disabled
PSI test: add a CPU limit of 500m to cpu-stress-pod
apply integration test: fix ordering test flake
…AttachmentLimitExceeded` (#133357) * Add stress test for pod cleanup when rejected due to VolumeAttachmentLimitExceeded Signed-off-by: Eddie Torres <[email protected]> * Move newTestPodsWithResources below TestVolumeAttachLimitExceededCleanup Signed-off-by: Eddie Torres <[email protected]> --------- Signed-off-by: Eddie Torres <[email protected]>
Omit value type from validation rule failures
Enforce that all resources set resourcePrefix
Signed-off-by: Omer Aplatony <[email protected]>
DRA also calls Register at pkg/kubelet/cm/container_manager_linux.go NewContainerManager(), causing volume stats collector being ignored. Fix this by moving it out of `sync.Once()`, allowing multiple calls to `Register()` func.
…tionGracePeriodSeconds Lock down AllowOverwriteTerminationGracePeriodSeconds
modify test "the error includes the reason when the condition.Status is False"
fix: Only warn for unrecognized formats on type=string
[BUG] [Selectors]: Return an error in case nil selectors are passed to the matcher functions
Self nominate HirazawaUi as sig-node reviewer
feat: Add discovery check to SVM to ensure migration doesn't get stuck
node_e2e: fix kubelet configuration setup
Replace deprecated sets.String with sets.Set in client-go/tools/*
…ror_of_kubectl_scale Standardize not found error message of kubectl scale
…alidation-error [client-go] [cli-runtime] [133916]: fix config override logic when override provides ClientKey, ClientCertificate
…r-watcher-replace Replace NewIndexerInformerWatcher with NewIndexerInformerWatcherWithLogger
scheduler_perf: run garbage collection before measurement
Fix flaking RunTestDelayedWatchDelivery
deflake unit test: TestIsConnectionReset
Fix cacher resource prefix not having a "/" at the end in tests
Drop PodIndexLabel after the feature GA-ed in 1.32
dd9917d fixed one test which did not wait for pods to be deleted and then, depending on the timing, left ResourceClaims prepared because the driver stopped before kubelet could call NodeUnprepareResources. But this is a more systematic issue also with other tests, so now the any test which starts a DRA plugin automatically uses the same common cleanup code: - delete pods in the test names - wait for the driver to not have any active ResourceClaims - stop the driver
Explicitly set TerminationGracePeriodSeconds for mirror pod
Remove container name from container event messages
deflake e2e tests: Pod Level Resources Downward API
…image-fedora42 Update volume/iscsi base image from fedora:38 to fedora:42
Set the deprecated version=1.34.0 for apiserver_storage_objects metric
Signed-off-by: Osama Nabih <[email protected]>
DRA E2E node: fix test cleanup
…rsion-to-2_56 Update Nautilus test BASEIMAGES agnhost from 2.33 to 2.57
fix CI failure: update pod image using the same one
kcm/app: Add proper goroutine management
Co-authored-by: Bing Hongtao <[email protected]>
kubeadm: fix KUBEADM_UPGRADE_DRYRUN_DIR not honored in upgrade phase when writing kubelet config files
Clean up pkg/kubelet/config
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.
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: