bump to 1.31 and carry 126557: Stop requiring meta.Object for clientsets#30
Closed
atiratree wants to merge 2196 commits intoopenshift:masterfrom
Closed
bump to 1.31 and carry 126557: Stop requiring meta.Object for clientsets#30atiratree wants to merge 2196 commits intoopenshift:masterfrom
atiratree wants to merge 2196 commits intoopenshift:masterfrom
Conversation
This adds a generic implementation of a lister, and uses it to replace the template code in generated listers. The corresponding templates are no longer used and are removed. Listers are reduced to their interfaces (non-namespaced and namespaced if appropriate), their specific structs, and their constructors. All method implementations are provided by the generic implementation. The dedicated interface is preserved so that each lister can have its own set of methods (e.g. the method returning the namespaced lister if appropriate), and the dedicated struct is preserved to allow expansions to be defined where necessary. The external interface is unchanged and doesn't expose generics. Signed-off-by: Stephen Kitt <skitt@redhat.com> Kubernetes-commit: 2e9adcd14aae27394238291fa08fb603bf2f3e77
Signed-off-by: Stephen Kitt <skitt@redhat.com> Kubernetes-commit: e6f44957cdb961d1ada2ae570d331c6bc0ecc8e2
Signed-off-by: Nilekh Chaudhari <1626598+nilekhc@users.noreply.github.com> Kubernetes-commit: 9161302e7fd3a5fb055b2f2572c6e1228240bb51
Kubernetes-commit: ad3d138cda76fc0267da5131fa3ff7906e2ddf76
Kubernetes-commit: 17ab25b121d05355700f39628d5d45ab3da446f8
Signed-off-by: Davanum Srinivas <davanum@gmail.com> Kubernetes-commit: bf268f02a3567c1af29199c27a7cf61cca494b2d
NodeResourceSlice will be used by kubelet to publish resource information on behalf of DRA drivers on the node. NodeName and DriverName in NodeResourceSlice must be immutable. This simplifies tracking the different objects because what they are for cannot change after creation. The new field in ResourceClass tells scheduler and autoscaler that they are expected to handle allocation. ResourceClaimParameters and ResourceClassParameters are new types for telling in-tree components how to handle claims. Kubernetes-commit: 39bbcedbcae84bf716923b3f9464968ca70b42e7
The default queue implementation is mostly FIFO and it is not exchangeable unless we implement the whole `workqueue.Interface` which is less desirable as we have to duplicate a lot of code. There was one attempt done in [kubernetes/kubernetes#109349][1] which tried to implement a priority queue. That is really useful and [knative/pkg][2] implemented something called two-lane-queue. While two lane queue is great, but isn't perfect since a full slow queue can still slow down items in fast queue. This change proposes a swappable queue implementation while not adding extra maintenance effort in kubernetes community. We are happy to maintain our own queue implementation (similar to two-lane-queue) in downstream. [1]: kubernetes/kubernetes#109349 [2]: https://github.com/knative/pkg/blob/main/controller/two_lane_queue.go Kubernetes-commit: 87b4279e07349b3c68f16f69a349a02bddd12f25
Kubernetes-commit: b7f620c12b7f2dbd7907ccad1ca63811a5c5766b
Like the current device plugin interface, a DRA driver using this model announces a list of resource instances. In contrast to device plugins, this list is made available to the scheduler together with attributes that can be used to select suitable instances when they are not all alike. Because this is the first structured parameter model, some checks that previously were not possible, in particular "is one structured parameter field set", now gets enabled. Adding another structured parameter model will be similar. The applyconfigs code generator assumes that all types in an API are defined in a single package. If it wasn't for that, it would be possible to place the "named resources" types in separate packages, which makes their names in the Go code more natural and provides an indication of their stability level because the package name could include a version. Kubernetes-commit: d4d5ade7f5be047472f8d9572c7f01f142951a2d
Kubernetes-commit: 646fd200b8532b0df95df300a8351379315f3ac9
Kubernetes-commit: 9633e25579dfa5449450875b9a238acc7cfac3e8
Use Aggregated Discovery v2 types and promote to GA Kubernetes-commit: 3f25211d69b4412e3e926835067918f86f629f3e
Kubernetes-commit: 1d4be7527f8b2d2c4eb6dcc7ef58b4c3133f6f19
Add option to upgrade subresource from CSA to SSA Kubernetes-commit: 65d75501f7d7348db1610e755e654b67c6639897
Increase client-side websocket write deadline Kubernetes-commit: 0a31504ee114e363df9d69158c2e639858b8273b
Kubernetes-commit: 8b447d8c97e8823b4308eb91cf7d75693e867c61
…on close error Kubernetes-commit: e8bbb221d36f1adf4116752990c0c4f17a9e5deb
This adds support for semantic version comparison to the CEL support in the "named resources" structured parameter model. For example, it can be used to check that an instance supports a certain API level. To minimize the risk, the new "semver" type is only defined in the CEL environment for DRA expressions, not in the base library. See kubernetes/kubernetes#123664 for a PR which adds it to the base library. Validation of semver strings is done with the regular expression from semver.org. The actual evaluation at runtime then uses semver/v4. Kubernetes-commit: 42ee56f093133402ed860d4c5f54b049041386c9
Kubernetes-commit: 33af937b4a5f4eb5c5005bddb483317f042da515
Kubernetes-commit: b04d1177efb0cfc84b76732848eef8f0ea89b25b
PortForward: Tunnel SPDY through WebSockets Kubernetes-commit: f745503112e06d6ff199e929d536c6a29825c01a
Extend deadlines to one minute Kubernetes-commit: 0bcf6e3ddee25621428017e135ce04879b32e659
Introduce trafficDistribution field for Kubernetes Services Kubernetes-commit: a76a3e031fc950a9c2429e611fd0bb00a117b1fc
Kubernetes-commit: 855bc74023900b31095de72ae49c79d5d391aad5
* support for the managed-by label in Job * Use managedBy field instead of managed-by label * Additional review remarks * Review remarks 2 * review remarks 3 * Skip cleanup of finalizers for job with custom managedBy * Drop the performance optimization * imrpove logs Kubernetes-commit: e568a77a931a1cf4239a4a5fa43e2b05bad3abdf
Add DeletionHandlingObjectToName Kubernetes-commit: 6efef796f6f3ee4825359ec4f77d2c2ee936e363
Adds OWNERS files to client-go streaming dirs Kubernetes-commit: 262399065dab3c5aa04fff83f04c2c4d3f3e444b
[KEP-3488]Promote ValidatingAdmissionPolicy to GA Kubernetes-commit: 2b521e5f8e6b99e84d464d8fa35658aed35bd13c
….33.0 Kubernetes-commit: c6673d2346c814ddb4629c569bdc659ffa0c583f
Make ServiceBackendPort an atomic struct Kubernetes-commit: 77e12aeca92c3c0fe2c1fc6ce7f0e17ba796c6fd
Kubernetes-commit: 9d560540c5268e0e2aebf5306907494cf522c260
Kubernetes-commit: bc526472515e1a01d41e5a94db2b74462545c984
Falls back to SPDY for gorilla/websocket https proxy error Kubernetes-commit: 90a84704d6e103c0a7b5cdaa8f6626a134079147
This is in preparation for revamping the resource.k8s.io completely. Because there will be no support for transitioning from v1alpha2 to v1alpha3, the roundtrip test data for that API in 1.29 and 1.30 gets removed. Repeating the version in the import name of the API packages is not really required. It was done for a while to support simpler grepping for usage of alpha APIs, but there are better ways for that now. So during this transition, "resourceapi" gets used instead of "resourcev1alpha3" and the version gets dropped from informer and lister imports. The advantage is that the next bump to v1beta1 will affect fewer source code lines. Only source code where the version really matters (like API registration) retains the versioned import. Kubernetes-commit: b51d68bb87ba4fa47eb760f8a5e0baf9cf7f5b53
Kubernetes-commit: 3999b98c8840e41acaa19d94e88f46d1fbb0c1b3
Kubernetes-commit: c47ff1e1a9aec44f262674eb6cdbabf80512d981
DRA for 1.31 Kubernetes-commit: d21b17264e5a554724aa3ad032536630bcfd5b3f
…n possible Kubernetes-commit: f387f0b69acb34143f76275aacb955fabb555bd7
Adds extra error information from response to bad handshake error when possible Kubernetes-commit: f753a444a5e0b245d2cf8433f7d8bb915c12363e
Signed-off-by: Dr. Stefan Schimanski <stefan.schimanski@gmail.com> Kubernetes-commit: 68226b0501996fc86c9c2bddb7d61e6a64c91304
Kubernetes-commit: fac758164029e278e9bda924090ed078bb6514c8
Kubernetes-commit: e1ea24a171ca6ba2d0f184abbd019ab3cf4a93c4
Kubernetes-commit: 0c774d0b1f79b0b0a6d73102a78c84853220f036
Allow calling Stop multiple times on RetryWatcher Kubernetes-commit: fc03f3e74c3d891e62b347c518b3197b62e9532c
[KEP-3751] Promote VolumeAttributesClass to beta Kubernetes-commit: c2fdeca4ab81336daf20c91b810c9685918c3d58
Kubernetes-commit: 2253b53b585e3405c5ce2dda2921db3a0afa02c9
Implement resource health in pod status (KEP 4680) Kubernetes-commit: 5af1710d90d2396f6305c73fdf7df3a1be0c2fd0
I was workinng on updating a dependency, and noticed that running hack/update-vendor.sh resulted in a diff. Comitting the result as a PR. Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Kubernetes-commit: aeb607443dd9b8ee378ee10209e9b446256f3ee2
Fix verify-vendor script to check all go.mod and go.sum files Kubernetes-commit: 9edabd617945cd23111fd46cfc9a09fe37ed194a
Coordinated Leader Election Kubernetes-commit: 5f5c02da51cd3146f30c6ee56013c983f4999d9c
Signed-off-by: Dr. Stefan Schimanski <stefan.schimanski@gmail.com> Kubernetes-commit: c7a1fa432a87579895eac4b3873162d5f1dba7f5
Signed-off-by: Dr. Stefan Schimanski <stefan.schimanski@gmail.com> Kubernetes-commit: cd69335542fd961b69b4e83b6433d1b40d2f4439
openshift-ci
bot
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
|
Member
Author
|
closing in favor of openshift/api#1983 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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.
this carry is required to fix client generationfor non meta types in openshift/client-go#291