chore(eks): remediate management runtime blockers - #170
Open
plural-copilot[bot] wants to merge 1 commit into
Open
chore(eks): remediate management runtime blockers#170plural-copilot[bot] wants to merge 1 commit into
plural-copilot[bot] wants to merge 1 commit into
Conversation
Contributor
Author
There was a problem hiding this comment.
This PR was generated by the codex Plural Agent Runtime. Here's some useful information you might want to know to evaluate the ai's perfomance:
| Name | Details |
|---|---|
| 💬 Prompt | Create ONE minimal management-runtime EKS 1.35 blocker-remediation PR in this repository. Do not inspect or modify any pre-existing PR branches.... |
| 🔗 Run history | View run history |
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
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.
Summary
Create the minimal bootstrap management-runtime release required for the EKS 1.35 add-on blockers.
Version changes
0.1.36→0.1.37ingress-nginxdependency: chart4.14.1→4.15.0(controller app1.14.1→1.15.0)ingress-nginxalias dependency: chart4.14.1→4.15.0(controller app1.14.1→1.15.0)3.15.1→3.21.1(upstream chart metadata reports appVersionv3.21.1)charts/runtime/Chart.lockand the vendored archive were refreshed (ingress-nginx-4.14.1.tgzreplaced byingress-nginx-4.15.0.tgz). No encrypted runtime values or unrelated runtime components changed.Ownership and scope
charts/runtime/Chart.yamlpackages ingress-nginx twice: the normal subchart and theingress-nginx-privatealias. Both pins must move together to keep public and private runtime controllers aligned.Gatekeeper is not a workload-only declaration here. The definitive chart source is
resources/policy/services/gatekeeper.yaml, a fleet-wideGlobalService;setup/pr-automation/gatekeeper-setup.yamlcopies this bootstrap-owned template intobootstrap/policymanagement-app configuration. It is therefore included in this same minimal remediation.Deployment order
This PR must be merged and released first, so the bootstrap chart release
runtime-0.1.37is available. Then updateplrl-up-demosin the downstream management runtime ServiceDeployment-reference PR to reference0.1.37, and wait for that reference PR to reconcile healthy.Only after that healthy reconciliation, apply the existing management upgrade PR #2782, then #2779. This change is additive to #2782 and #2779: it supplies prerequisite controller versions and does not replace, reorder internally, or otherwise modify either upgrade PR.
Validation
Passed with containerized Helm
3.17.3:Results: dependency build succeeded; linted 1 chart with 0 failures (one non-blocking recommended-icon info message); template rendered 2,312 lines. Inspected vendored ingress metadata confirms chart
4.15.0/ appVersion1.15.0; inspected Gatekeeper upstream metadata confirms chart3.21.1/ appVersionv3.21.1.Result: passed.
Plural Stack: mgmt
Plural Service: mgmt/runtime
Plural Service: mgmt/apps