Repository navigation
Conversation
This was referenced Oct 3, 2026
kube 4 builds CRDs as typed `CustomResourceDefinition`s, which omit the empty `spec.names.categories` list, so the exported VpcEndpoint CRD changes accordingly. k8s-controller exposes kube types, so this needs a k8s-controller release on kube 4. Until then the workspace patches it to a pinned fork commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cargo-deny only allows Git sources owned by MaterializeInc. GitHub serves the pull request's commit from the upstream repository as well. The fuzz workspace does not depend on k8s-controller, so the lint-cargo patch mirror check omits it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
1 participant
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.
The workspace compiles unchanged against kube 4.2 and k8s-openapi 0.28, and it keeps the
v1_34API feature. k8s-controller also moves from 0.12 to 0.13, whose additions (reconcile observers, events, conditions) are opt-in.kube 4 builds derived CRDs as typed
CustomResourceDefinitions, which omit the emptyspec.names.categorieslist. The exported VpcEndpoint CRD changes by that field. Kubernetes treats an absent list and an empty one the same.Other kube 4 behavior changes that reach us:
mz_orchestrator_kubernetes::util::create_clientsetsread_timeoutandconnect_timeoutexplicitly, so our clients keep their timeouts.hyper-util-tracing, which this PR does not enable.smallvec < 1.16. The lock moves smallvec from 1.16.2 back to 1.15.2, which still satisfies the workspace requirement of 1.15.1.Draft until MaterializeInc/k8s-controller#55 ships as a release. k8s-controller exposes kube types, so it has to move to kube 4 first. Until then,
[patch.crates-io]pins that pull request's commit through the MaterializeInc repository, and the fuzz patch-mirror check inbin/lint-cargoomits the entry. Both go away with the release.Posted by Claude Code.
🤖 Generated with Claude Code