{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":120642119,"defaultBranch":"master","name":"kubernetes","ownerLogin":"pohly","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2018-02-07T16:39:26.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/22076?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1714496053.0","currentOid":""},"activityList":{"items":[{"before":"e0ede9437768e99408e2f1965421157bdc3f17ef","after":"e8323872c5cf72530777b9551f8c7f0f2881f243","ref":"refs/heads/dra-kubelet-api-version-independent","pushedAt":"2024-05-03T15:10:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"DRA: move ResourceSlice publishing into DRA drivers\n\nThis is a first step towards making kubelet independent of the resource.k8s.io\nAPI versioning because it now doesn't need to copy structs defined by that API\nfrom the driver to the API server. The next step is removing the other\ndirection (reading ResourceClaim status and passing the resource handle to\ndrivers).\n\nThe drivers are still using the kubelet to access ResourceSlices, so the node\nauthorizer still applies and limits access to those objects that kubelet has\naccess to. Drivers don't need separate credentials. This works with the help of\na REST proxy that is provided to drivers by kubelet. That proxy checks that\ndrivers really only use it to access ResourceSlices.\n\nAs before, the kubelet removes all ResourceSlices for its node at startup, then\nDRA drivers recreate them if (and only if) they start up again. This ensures\nthat there are no orphaned ResourceSlices when a driver gets removed while the\nkubelet was down.\n\nWhile at it, logging gets cleaned up and updated to use structured, contextual\nlogging as much as possible. gRPC requests and streams now use a shared,\nper-process request ID and streams also get logged.","shortMessageHtmlLink":"DRA: move ResourceSlice publishing into DRA drivers"}},{"before":"762aa39bac3eff7b04fa2827a33e8a3f2b9659b8","after":"e0ede9437768e99408e2f1965421157bdc3f17ef","ref":"refs/heads/dra-kubelet-api-version-independent","pushedAt":"2024-05-02T17:37:30.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"DRA: move ResourceSlice publishing into DRA drivers\n\nThis is a first step towards making kubelet independent of the resource.k8s.io\nAPI versioning because it now doesn't need to copy structs defined by that API\nfrom the driver to the API server. The next step is removing the other\ndirection (reading ResourceClaim status and passing the resource handle to\ndrivers).\n\nThe drivers are still using the kubelet to access ResourceSlices, so the node\nauthorizer still applies and limits access to those objects that kubelet has\naccess to. Drivers don't need separate credentials. This works with the help of\na REST proxy that is provided to drivers by kubelet. That proxy checks that\ndrivers really only use it to access ResourceSlices.\n\nAs before, the kubelet removes all ResourceSlices for its node at startup, then\nDRA drivers recreate them if (and only if) they start up again. This ensures\nthat there are no orphaned ResourceSlices when a driver gets removed while the\nkubelet was down.\n\nWhile at it, logging gets cleaned up and updated to use structured, contextual\nlogging as much as possible.","shortMessageHtmlLink":"DRA: move ResourceSlice publishing into DRA drivers"}},{"before":null,"after":"77a7680db3ce73fdcd00c08ae01c9e49cbd9209a","ref":"refs/heads/PR144-e2e_node-DRA-test-plugin-failures","pushedAt":"2024-04-30T16:54:13.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"DRA: implement error injection and blocking inside test-specific interceptor\n\nPreviously, blocking and error injection where implemented inside the kubelet\nplugin code of the driver. This was a bit hacky and not thread-safe (no\nlocking).\n\nFor upcoming tests we need more flexibility. Now a test can inject its own gRPC\ninterceptor into the kubelet plugin code. A pre-built one supports blocking and\nerror injection, but completely different interceptors are also possible if\nneeded.","shortMessageHtmlLink":"DRA: implement error injection and blocking inside test-specific inte…"}},{"before":null,"after":"ff779f1cb56cf896405e52f7923188b99b88bb00","ref":"refs/heads/event-broadcaster-shutdown-fix","pushedAt":"2024-04-30T10:22:51.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"client-go/tools/record: fix and test Broadcaster shutdown + logging\n\nConstructing a Broadcaster already starts a watch which runs in the\nbackground. Shutdown must be called to avoid leaking the goroutine.  Providing\na context was supposed to remove the need to call Shutdown, but that did not\nactually work because the logic for \"must check for cancellation\" was\naccidentally inverted.\n\nWhile at it, structured log output also gets tested together with checking for\ngoroutine leaks.","shortMessageHtmlLink":"client-go/tools/record: fix and test Broadcaster shutdown + logging"}},{"before":"7d7ffeebdc71ee4f15ddfa08e4c21438e6b2b62e","after":"8d6a5be8854d12d2ae37756f03324f70141171e0","ref":"refs/heads/log-client-go-tools-cache","pushedAt":"2024-04-30T10:21:30.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"convert more event broadcasters to structured logging","shortMessageHtmlLink":"convert more event broadcasters to structured logging"}},{"before":"78581784f168c2064d521d2ce337e27f3e6467d0","after":"b92273a760503cc57aba37c4d3a28554f7fec7f8","ref":"refs/heads/controllers-context-support","pushedAt":"2024-04-29T19:01:46.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"apiserver + controllers: enhance context support\n\n27a68aee3a4834 introduced context support for events. Creating an event\nbroadcaster with context makes tests more resilient against leaking goroutines\nwhen that context gets canceled at the end of a test and enables per-test\noutput via ktesting.\n\nThe context could get passed to the constructor. A cleaner solution is to\nenhance context support for the apiserver and then pass the context into the\ncontroller's run method. This ripples up the call stack to all places which\nstart an apiserver.","shortMessageHtmlLink":"apiserver + controllers: enhance context support"}},{"before":"cd457e1861fd393a65b568c78d051f7d0ee71cb7","after":"78581784f168c2064d521d2ce337e27f3e6467d0","ref":"refs/heads/controllers-context-support","pushedAt":"2024-04-29T14:01:31.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"apiserver + controllers: enhance context support\n\n27a68aee3a4834 introduced context support for events. Creating an event\nbroadcaster with context makes tests more resilient against leaking goroutines\nwhen that context gets canceled at the end of a test and enables per-test\noutput via ktesting.\n\nThe context could get passed to the constructor. A cleaner solution is to\nenhance context support for the apiserver and then pass the context into the\ncontroller's run method. This ripples up the call stack to all places which\nstart an apiserver.","shortMessageHtmlLink":"apiserver + controllers: enhance context support"}},{"before":"2d66ba2f85a71d65291ec78c6d8e8ee6f9742683","after":"0b0e8e3882933e2c4642febac0442716060e107b","ref":"refs/heads/dra-scheduler-assume-cache-eventhandlers","pushedAt":"2024-04-29T12:43:39.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"scheduler: central ResourceClaim assume cache\n\nThis enables connecting the event handler for ResourceClaim to the assume\ncache, which addresses a theoretic race condition.\n\nIt may also be useful for implementing the autoscaler support, because now\nthe autoscaler can modify the content of the cache.","shortMessageHtmlLink":"scheduler: central ResourceClaim assume cache"}},{"before":"7d9abd57c6ca3c979e289c96f000ddfbaefbcc56","after":"2d66ba2f85a71d65291ec78c6d8e8ee6f9742683","ref":"refs/heads/dra-scheduler-assume-cache-eventhandlers","pushedAt":"2024-04-29T08:59:43.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"scheduler: central ResourceClaim assume cache\n\nThis enables connecting the event handler for ResourceClaim to the assume\ncache, which addresses a theoretic race condition.\n\nIt may also be useful for implementing the autoscaler support, because now\nthe autoscaler can modify the content of the cache.","shortMessageHtmlLink":"scheduler: central ResourceClaim assume cache"}},{"before":"3cc6fe20590f590934ab8ef00720768480c35e7d","after":"7d9abd57c6ca3c979e289c96f000ddfbaefbcc56","ref":"refs/heads/dra-scheduler-assume-cache-eventhandlers","pushedAt":"2024-04-29T06:35:27.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"fixup! scheduler: AddEventHandler for assume cache","shortMessageHtmlLink":"fixup! scheduler: AddEventHandler for assume cache"}},{"before":"24557fd928c3f20e518b1c07079968a9c5437b43","after":"3cc6fe20590f590934ab8ef00720768480c35e7d","ref":"refs/heads/dra-scheduler-assume-cache-eventhandlers","pushedAt":"2024-04-28T12:40:21.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"fixup! scheduler: AddEventHandler for assume cache","shortMessageHtmlLink":"fixup! scheduler: AddEventHandler for assume cache"}},{"before":"414b9f639eff2595854d774712432de91e5644df","after":"6eba52e79541796a96941a95710726c16eaf4fea","ref":"refs/heads/apidiff","pushedAt":"2024-04-26T09:00:08.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"hack/apidiff.sh: compare between two revisions, usability enhancements\n\nIn a Prow job, the current work tree is the result of merging a PR into the\ntarget. We want apidiff.sh from there, but then need to invoke it for two\nspecific revisions and compare.\n\nWhile at it, output and usability get enhanced. The directory parameter(s) may\nbe absolute paths or lack the leading . that is required by apidiff.","shortMessageHtmlLink":"hack/apidiff.sh: compare between two revisions, usability enhancements"}},{"before":"b120eca5662435ee222a940956d783ae8382bd17","after":"414b9f639eff2595854d774712432de91e5644df","ref":"refs/heads/apidiff","pushedAt":"2024-04-26T08:55:21.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"hack/apidiff.sh: compare between two revisions, usability enhancements\n\nIn a Prow job, the current work tree is the result of merging a PR into the\ntarget. We want apidiff.sh from there, but then need to invoke it for two\nspecific revisions and compare.\n\nWhile at it, output and usability get enhanced. The directory parameter(s) may\nbe absolute paths or lack the leading . that is required by apidiff.","shortMessageHtmlLink":"hack/apidiff.sh: compare between two revisions, usability enhancements"}},{"before":"679195d8cc56e7f6ed4f75cde13ce484f452c996","after":"b120eca5662435ee222a940956d783ae8382bd17","ref":"refs/heads/apidiff","pushedAt":"2024-04-26T08:48:19.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"hack/apidiff.sh: compare between two revisions, usability enhancements\n\nIn a Prow job, the current work tree is the result of merging a PR into the\ntarget. We want apidiff.sh from there, but then need to invoke it for two\nspecific revisions and compare.\n\nWhile at it, output and usability get enhanced. The directory parameter(s) may\nbe absolute paths or lack the leading . that is required by apidiff.","shortMessageHtmlLink":"hack/apidiff.sh: compare between two revisions, usability enhancements"}},{"before":"97040efd0b2b82d881329dd3f4abc6192629b183","after":"4306a8b1927ed734f82ae81cb149270c93e56a4c","ref":"refs/heads/dra-scheduler-perf-structured-parameters","pushedAt":"2024-04-26T06:39:35.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"scheduler_perf: add DRA structured parameters test with shared claims\n\nSeveral pods sharing the same claim is not common, but can be useful and thus\nshould get tested.\n\nBefore, createPods and createAny operations were not able to do this because\neach generated object was the same. What we need are different, predictable\nnames of the claims (from createAny) and different references to those in the\npods (from createPods). Now text/template processing with the index number of\nthe pod respectively claim as input is used to inject these varying fields. A\n\"div\" function is needed to use the same claim in several different pods.\n\nWhile at it, some existing test cases get cleaned up a bit (removal of\nincorrect comments, adding comments for testing with queuing hints).","shortMessageHtmlLink":"scheduler_perf: add DRA structured parameters test with shared claims"}},{"before":null,"after":"97040efd0b2b82d881329dd3f4abc6192629b183","ref":"refs/heads/dra-scheduler-perf-structured-parameters","pushedAt":"2024-04-26T06:37:07.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"scheduler_perf: add DRA structured parameters test with shared claims\n\nSeveral pods sharing the same claim is not common, but can be useful and thus\nshould get tested.\n\nBefore, createPods and createAny operations were not able to do this because\neach generated object was the same. What we need are different, predictable\nnames of the claims (from createAny) and different references to those in the\npods (from createPods). Now text/template processing with the index number of\nthe pod respectively claim as input is used to inject these varying fields.\n\nWhile at it, some existing test cases get cleaned up a bit (removal of\nincorrect comments, adding comments for testing with queuing hints).","shortMessageHtmlLink":"scheduler_perf: add DRA structured parameters test with shared claims"}},{"before":"06281bb8fb9f243cdeb48801cc5784f03911f9a1","after":"50c12437604b0cd5a73514389409fc2fde8b91bd","ref":"refs/heads/cloud-providers-context-support","pushedAt":"2024-04-25T09:57:25.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"cloud providers: enhance context support\n\n27a68aee3a4834 introduced context support for events. Creating an event\nbroadcaster with context makes tests more resilient against leaking goroutines\nwhen that context gets canceled at the end of a test and enables per-test\noutput via ktesting.\n\nWhile at it, all context.TODO calls get removed in files that were touched.","shortMessageHtmlLink":"cloud providers: enhance context support"}},{"before":"44df029ebdb6738bc724ba0d4d3e540c1c819405","after":"7f54c5dfec3e95a2751156a3a1ae4407be68297a","ref":"refs/heads/dra-scheduler-assume-cache","pushedAt":"2024-04-25T09:47:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"scheduler: remove AssumeCache interface\n\nThere's no reason for having the interface because there is only one\nimplementation. Makes the implementation of the test functions a bit\nsimpler (no casting). They are still stand-alone functions instead of methods\nbecause they should not be considered part of the \"normal\" API.","shortMessageHtmlLink":"scheduler: remove AssumeCache interface"}},{"before":"73eb79512f2524bf5c9b981b8c2f16ea8f9e61fc","after":"679195d8cc56e7f6ed4f75cde13ce484f452c996","ref":"refs/heads/apidiff","pushedAt":"2024-04-25T08:39:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"hack/apidiff.sh: handle lack of origin\n\nThe script failed in the Prow job with:\n\n   fatal: Not a valid object name origin/master\n\nThat came from \"git merge-base origin/master HEAD\", which isn't needed because\nthe Prow job intentionally sets -r explicitly.\n\nNow the fallback is only tried if needed. While at it, the informational\nmessages get enhanced.","shortMessageHtmlLink":"hack/apidiff.sh: handle lack of origin"}},{"before":"36aa8b1d528eb928accf39c6e2f244051848dd58","after":"06281bb8fb9f243cdeb48801cc5784f03911f9a1","ref":"refs/heads/cloud-providers-context-support","pushedAt":"2024-04-25T08:28:05.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"cloud providers: enhance context support\n\n27a68aee3a4834 introduced context support for events. Creating an event\nbroadcaster with context makes tests more resilient against leaking goroutines\nwhen that context gets canceled at the end of a test and enables per-test\noutput via ktesting.\n\nWhile at it, all context.TODO calls get removed in files that were touched.","shortMessageHtmlLink":"cloud providers: enhance context support"}},{"before":"4bb5fe68cc396999fed018be202dd2cc0f8fe6ff","after":"73eb79512f2524bf5c9b981b8c2f16ea8f9e61fc","ref":"refs/heads/apidiff","pushedAt":"2024-04-25T07:06:44.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"hack/apidiff.sh: handle lack of origin\n\nThe script failed in the Prow job with:\n\n   fatal: Not a valid object name origin/master\n\nThat came from \"git merge-base origin/master HEAD\", which isn't needed because\nthe Prow job intentionally sets -r explicitly.\n\nNow the fallback is only tried if needed. While at it, the informational\nmessages get enhanced.","shortMessageHtmlLink":"hack/apidiff.sh: handle lack of origin"}},{"before":"a3c714f482563802bd442cecabe3224073aafb19","after":"cd457e1861fd393a65b568c78d051f7d0ee71cb7","ref":"refs/heads/controllers-context-support","pushedAt":"2024-04-24T16:11:41.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"apiserver + controllers: enhance context support\n\n27a68aee3a4834 introduced context support for events. Creating an event\nbroadcaster with context makes tests more resilient against leaking goroutines\nwhen that context gets canceled at the end of a test and enables per-test\noutput via ktesting.\n\nThe context could get passed to the constructor. A cleaner solution is to\nenhance context support for the apiserver and then pass the context into the\ncontroller's run method. This ripples up the call stack to all places which\nstart an apiserver.","shortMessageHtmlLink":"apiserver + controllers: enhance context support"}},{"before":"0a89572aed51477ef9baf4963fc29aa2f1a42d51","after":"a3c714f482563802bd442cecabe3224073aafb19","ref":"refs/heads/controllers-context-support","pushedAt":"2024-04-24T16:01:58.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"apiserver + controllers: enhance context support\n\n27a68aee3a4834 introduced context support for events. Creating an event\nbroadcaster with context makes tests more resilient against leaking goroutines\nwhen that context gets canceled at the end of a test and enables per-test\noutput via ktesting.\n\nThe context could get passed to the constructor. A cleaner solution is to\nenhance context support for the apiserver and then pass the context into the\ncontroller's run method. This ripples up the call stack to all places which\nstart an apiserver.","shortMessageHtmlLink":"apiserver + controllers: enhance context support"}},{"before":"00ceebef57961cae513eb79aeee0208490e8d171","after":"4bb5fe68cc396999fed018be202dd2cc0f8fe6ff","ref":"refs/heads/apidiff","pushedAt":"2024-04-23T13:04:10.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"hack: use \"latest\" apidiff\n\nPinning apidiff to a specific version shouldn't be necessary because, if past\nexperience in klog holds true, the latest version just works. This way we don't\nhave to remember to bump up the revision.\n\nThe downside of using \"latest\" is that a compromise of that version would give\nan attacker the ability to run code in the CI and on developer machines.","shortMessageHtmlLink":"hack: use \"latest\" apidiff"}},{"before":"1db9d01185fe2dfd06c6b0cb092ab0aac71957bd","after":"0a89572aed51477ef9baf4963fc29aa2f1a42d51","ref":"refs/heads/controllers-context-support","pushedAt":"2024-04-22T19:20:13.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"apiserver + controllers: enhance context support\n\n27a68aee3a4834 introduced context support for events. Creating an event\nbroadcaster with context makes tests more resilient against leaking goroutines\nwhen that context gets canceled at the end of a test and enables per-test\noutput via ktesting.\n\nThe context could get passed to the constructor. A cleaner solution is to\nenhance context support for the apiserver and then pass the context into the\ncontroller's run method. This ripples up the call stack to all places which\nstart an apiserver.","shortMessageHtmlLink":"apiserver + controllers: enhance context support"}},{"before":"54fc99db2013198804ba1a614ba8ab83aeae70fb","after":"7d7ffeebdc71ee4f15ddfa08e4c21438e6b2b62e","ref":"refs/heads/log-client-go-tools-cache","pushedAt":"2024-04-22T16:34:21.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"DRA helper: enhance context support\n\n27a68aee3a4834 introduced context support for events. Creating an event\nbroadcaster with context makes tests more resilient against leaking goroutines\nwhen that context gets canceled at the end of a test and enables per-test\noutput via ktesting.","shortMessageHtmlLink":"DRA helper: enhance context support"}},{"before":"20988de8cca8f7608987907a13c97767e1421ccb","after":"acfaf8c27590c78fe9900f8c7c1e99927392c20e","ref":"refs/heads/dra-api-comments","pushedAt":"2024-04-22T12:19:56.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"DRA: sync internal API doc comments\n\nThis had been done before for types.go, but namedresources.go still had one\nsmall diff.\n\nWhile at it, fix some typos.","shortMessageHtmlLink":"DRA: sync internal API doc comments"}},{"before":"049eb4f641d4a08ebf62e1baebb250c010f0e062","after":"0bb3047f469ceca4aac5dc53949125b4bd963465","ref":"refs/heads/test-apiserver-context","pushedAt":"2024-04-22T11:14:06.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"WIP: move TContext setup into StartTestServer","shortMessageHtmlLink":"WIP: move TContext setup into StartTestServer"}},{"before":"5495eadd5549e989226321ee8f5302d2189e2e24","after":"00ceebef57961cae513eb79aeee0208490e8d171","ref":"refs/heads/apidiff","pushedAt":"2024-04-20T20:02:32.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"hack: add apidiff.sh\n\napidiff can be invoked for a single internal package or iterate over\neverything, including staging. The base to compare against can be specified via\n-r (similar to verify-golangci-lint.sh), with the default the base revision on\nmaster (similar to -a in verify-golangci-lint.sh).","shortMessageHtmlLink":"hack: add apidiff.sh"}},{"before":"3246e3d93d4d9f36fd0ee8c0e81de652e79aa395","after":"5495eadd5549e989226321ee8f5302d2189e2e24","ref":"refs/heads/apidiff","pushedAt":"2024-04-20T19:42:07.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"pohly","name":"Patrick Ohly","path":"/pohly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22076?s=80&v=4"},"commit":{"message":"hack: add apidiff.sh\n\napidiff can be invoked for a single internal package or iterate over\neverything, including staging. The base to compare against can be specified via\n-r (similar to verify-golangci-lint.sh), with the default the base revision on\nmaster (similar to -a in verify-golangci-lint.sh).","shortMessageHtmlLink":"hack: add apidiff.sh"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEQOBcCQA","startCursor":null,"endCursor":null}},"title":"Activity · pohly/kubernetes"}