Skip to content

RHDH: promote mapt to v0.14.3 and Kubernetes 1.36 - #82854

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
zdrapela:mapt-0.14.3-promote
Aug 4, 2026
Merged

RHDH: promote mapt to v0.14.3 and Kubernetes 1.36#82854
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
zdrapela:mapt-0.14.3-promote

Conversation

@zdrapela

@zdrapela zdrapela commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Summary

Promote RHDH AKS/EKS CI to mapt v0.14.3 and main Kubernetes 1.36, after verification on #82807.

https://redhat.atlassian.net/browse/RHIDP-16008

Changes

  • Image mirror: add ci/mapt:v0.14.3quay.io/redhat-developer/mapt:v0.14.3; remove unused ci/mapt:v0.11.1 and ci/mapt:v0.13.0
  • Step registry: AKS + EKS create/destroy/orphaned-destroy from_image tags → v0.14.3
  • AKS --force-destroy: adopt Azure destroy flag (parity with EKS); remove locked-stack early-exit
  • Main only: MAPT_KUBERNETES_VERSION: "1.36" on AKS/EKS helm + operator nightlies. Release versions remain aligned with https://access.redhat.com/support/policy/updates/developerhub

Verification (#82807)

  • AKS helm nightly: success with mapt v0.14.3 + K8s 1.36 (job)
  • EKS: MapT create/destroy succeeded on 1.36; helm e2e hit unrelated Playwright UI flakes (3 timeouts). Earlier EKS rehearse with same mapt on 1.35 fully passed.

Note

After merge, the image-mirror job must populate ci/mapt:v0.14.3 before nightlies that pull that tag are fully safe.

/cc @albarbaro @kadel

Made with Cursor

Summary by CodeRabbit

  • Promotes RHDH AKS and EKS CI jobs to MapT v0.14.3 and Kubernetes 1.36.
  • Adds forced AKS infrastructure cleanup and removes obsolete locked-stack handling.
  • Updates image mirroring to publish ci/mapt:v0.14.3 and removes unused MapT versions.
  • Verification was completed in PR #82807. The image-mirror job must populate the new image after merge.

Mirror quay.io/redhat-developer/mapt:v0.14.3 as ci/mapt:v0.14.3 and
drop unused v0.11.1/v0.13.0 mirror entries. Point AKS/EKS MapT steps
at the new tag, adopt Azure --force-destroy, and set main
MAPT_KUBERNETES_VERSION to 1.36.

Verified via openshift#82807 rehearsals.
@openshift-ci
openshift-ci Bot requested review from albarbaro and kadel August 3, 2026 23:40
@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

MAPT nightly jobs now target Kubernetes 1.36 and use image v0.14.3. AKS cleanup commands now use --force-destroy, with unified exit-code and output handling for destroy failures.

Changes

MAPT configuration and image updates

Layer / File(s) Summary
MAPT versions and job targets
ci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-main.yaml, ci-operator/step-registry/redhat-developer/rhdh/**/mapt/**/*-ref.yaml, core-services/image-mirroring/_config.yaml
Nightly AKS and EKS MAPT jobs target Kubernetes 1.36. MAPT step images and supplemental image mappings use v0.14.3.
AKS forced cleanup handling
ci-operator/step-registry/redhat-developer/rhdh/aks/mapt/**/destroy/*-commands.sh
AKS MAPT destruction uses --force-destroy. The standard destroy command captures output and the exit status, then applies shared failure checks without special locked-stack handling.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The 11 changed files are YAML and shell/config files; the diff contains no Ginkgo test source or title APIs, so no dynamic test names were introduced.
Test Structure And Quality ✅ Passed The patch changes only YAML and shell CI files; it adds no Ginkgo test code or *_test.go files, so these test-quality requirements are not applicable.
Microshift Test Compatibility ✅ Passed The pull request changes only CI YAML and shell files; it adds no Ginkgo tests or MicroShift-sensitive test references.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The diff changes only CI YAML, shell commands, and image-mirror configuration; it adds no Ginkgo e2e tests or test code, so SNO compatibility review is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed The diff changes only CI YAML, shell commands, image tags, and MAPT version variables; it adds no deployment manifests, operator/controller code, or scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The PR changes only shell scripts and YAML; no OTE binary, main/suite setup, or openshift-tests integration is added or modified.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR changes only YAML references and shell cleanup commands; the commit adds no Ginkgo e2e tests or IPv4/public-network test logic.
No-Weak-Crypto ✅ Passed The 11-file diff only changes MapT image/Kubernetes versions, mirror entries, and destroy handling; scans found no weak algorithms, custom crypto, or secret/token comparisons.
Container-Privileges ✅ Passed Changed lines add image tags, an environment value, and --force-destroy; no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation settings exist. Existing USER root is u...
No-Sensitive-Data-In-Logs ✅ Passed The diff adds no sensitive log statements or literal secrets; Azure credentials are only loaded/exported, and existing MAPT output logging is unchanged.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the two primary changes: MapT promotion to v0.14.3 and Kubernetes version update to 1.36.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@zdrapela: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-redhat-developer-rhdh-main-e2e-aks-helm-nightly redhat-developer/rhdh presubmit Ci-operator config changed
pull-ci-redhat-developer-rhdh-main-e2e-aks-operator-nightly redhat-developer/rhdh presubmit Ci-operator config changed
pull-ci-redhat-developer-rhdh-main-e2e-eks-helm-nightly redhat-developer/rhdh presubmit Ci-operator config changed
pull-ci-redhat-developer-rhdh-main-e2e-eks-operator-nightly redhat-developer/rhdh presubmit Ci-operator config changed
periodic-ci-redhat-developer-rhdh-main-e2e-eks-operator-nightly N/A periodic Ci-operator config changed
periodic-ci-redhat-developer-rhdh-release-1.9-e2e-aks-helm-nightly N/A periodic Registry content changed
periodic-ci-redhat-developer-rhdh-release-1.10-e2e-eks-operator-nightly N/A periodic Registry content changed
periodic-ci-redhat-developer-rhdh-release-1.10-e2e-aks-operator-nightly N/A periodic Registry content changed
periodic-ci-redhat-developer-rhdh-release-1.10-e2e-aks-helm-nightly N/A periodic Registry content changed
periodic-ci-redhat-developer-rhdh-main-e2e-aks-operator-nightly N/A periodic Ci-operator config changed
periodic-ci-redhat-developer-rhdh-main-e2e-eks-helm-nightly N/A periodic Ci-operator config changed
periodic-ci-redhat-developer-rhdh-release-1.9-e2e-eks-helm-nightly N/A periodic Registry content changed
periodic-ci-redhat-developer-rhdh-release-1.10-e2e-eks-helm-nightly N/A periodic Registry content changed
periodic-ci-redhat-developer-rhdh-main-e2e-aks-helm-nightly N/A periodic Ci-operator config changed
periodic-ci-redhat-developer-rhdh-release-1.9-e2e-eks-operator-nightly N/A periodic Registry content changed
periodic-ci-redhat-developer-rhdh-main-cleanup-mapt-destroy-orphaned-eks-clusters N/A periodic Registry content changed
periodic-ci-redhat-developer-rhdh-release-1.9-e2e-aks-operator-nightly N/A periodic Registry content changed
periodic-ci-redhat-developer-rhdh-main-cleanup-mapt-destroy-orphaned-aks-clusters N/A periodic Registry content changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/step-registry/redhat-developer/rhdh/aks/mapt/destroy/redhat-developer-rhdh-aks-mapt-destroy-commands.sh`:
- Around line 32-38: Update the destroy failure check that inspects output with
grep to use a here-string instead of piping echo into grep. Ensure matching
error output, including output larger than the pipe buffer, cannot be reported
as successful under pipefail and the existing exit-code handling remains
unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: b619bebc-02fb-4dc2-96ed-6c9316252919

📥 Commits

Reviewing files that changed from the base of the PR and between 88e6194 and 3b44a83.

📒 Files selected for processing (11)
  • ci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-main.yaml
  • ci-operator/step-registry/redhat-developer/rhdh/aks/mapt/create/redhat-developer-rhdh-aks-mapt-create-commands.sh
  • ci-operator/step-registry/redhat-developer/rhdh/aks/mapt/create/redhat-developer-rhdh-aks-mapt-create-ref.yaml
  • ci-operator/step-registry/redhat-developer/rhdh/aks/mapt/destroy/redhat-developer-rhdh-aks-mapt-destroy-commands.sh
  • ci-operator/step-registry/redhat-developer/rhdh/aks/mapt/destroy/redhat-developer-rhdh-aks-mapt-destroy-ref.yaml
  • ci-operator/step-registry/redhat-developer/rhdh/aks/mapt/orphaned/destroy/redhat-developer-rhdh-aks-mapt-orphaned-destroy-commands.sh
  • ci-operator/step-registry/redhat-developer/rhdh/aks/mapt/orphaned/destroy/redhat-developer-rhdh-aks-mapt-orphaned-destroy-ref.yaml
  • ci-operator/step-registry/redhat-developer/rhdh/eks/mapt/create/redhat-developer-rhdh-eks-mapt-create-ref.yaml
  • ci-operator/step-registry/redhat-developer/rhdh/eks/mapt/destroy/redhat-developer-rhdh-eks-mapt-destroy-ref.yaml
  • ci-operator/step-registry/redhat-developer/rhdh/eks/mapt/orphaned/destroy/redhat-developer-rhdh-eks-mapt-orphaned-destroy-ref.yaml
  • core-services/image-mirroring/_config.yaml

@zdrapela

zdrapela commented Aug 4, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@zdrapela: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 4, 2026
@albarbaro

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 4, 2026
@openshift-ci

openshift-ci Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: albarbaro, Prucek, zdrapela

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 4, 2026
@openshift-ci

openshift-ci Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

@zdrapela: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot
openshift-merge-bot Bot merged commit a064f38 into openshift:main Aug 4, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants