[codex] operator: port executable CRD lifecycle - #11
Merged
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
wolfiesch
marked this pull request as ready for review
July 22, 2026 10:28
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
2 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.
What changed
Ports Roy's executable OP-02 CRD lifecycle from LycaonLLC/t4-code#136 onto the Omperator Electron baseline. It adds structural compatibility fixtures, local OpenAPI/CEL/pruning validation, live-object preflight, served-schema convergence, exact stored-version gates, and fail-closed upgrade orchestration.
The original commit history and authorship are preserved through the merge.
Why
Omperator retains the managed Kubernetes control-plane path after the Electron client pivot. This keeps CRD upgrades from stranding persisted resources or advancing workloads after an incompatible schema change.
Validation
Original work: LycaonLLC/t4-code#136