Upgrade Ascender to 25.5.0 and pin EE - #209
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Upgrades the Ascender install/migration configuration to use Ascender 25.5.0 and ensures the default execution environment (EE) image tag follows ASCENDER_VERSION instead of hardcoding latest, keeping runtime components aligned with the selected Ascender release.
Changes:
- Bumps documented/default
ASCENDER_VERSIONvalues to 25.5.0 across example configs and upgrade docs. - Updates the Ascender deployment spec template to default
image_versionto 25.5.0 and to tag the control plane EE/init container withASCENDER_VERSION. - Updates bundle creation and role defaults so the Ascender EE image tag tracks
ASCENDER_VERSION(rather thanlatest).
Reviewed changes
Copilot reviewed 14 out of 14 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| playbooks/roles/awx_migrate_ascender/README.md | Updates migration guidance examples for Ascender/EE versions and EE naming. |
| playbooks/roles/ascender_install/templates/ascender-deployment/additional-spec.yml | Sets Ascender default image version to 25.5.0 and pins control plane EE/init container to ASCENDER_VERSION. |
| playbooks/roles/ascender_install/defaults/main.yml | Makes default EE name/tag derive from ASCENDER_VERSION instead of always latest. |
| playbooks/group_vars/all.yml | Updates the shared default ASCENDER_VERSION to 25.5.0. |
| playbooks/create_bundle.yml | Bundles ascender-ee using the ASCENDER_VERSION tag instead of latest. |
| docs/installation/rke2/rke2.default.config.yml | Updates example config to Ascender 25.5.0. |
| docs/installation/k3s/k3s.offline.default.config.yml | Updates example config to Ascender 25.5.0. |
| docs/installation/k3s/k3s.default.config.yml | Updates example config to Ascender 25.5.0. |
| docs/installation/gke/gke.custom.config.yml | Updates example config to Ascender 25.5.0. |
| docs/installation/eks/eks.custom.config.yml | Updates example config to Ascender 25.5.0. |
| docs/installation/dkp/dkp.default.config.yml | Updates example config to Ascender 25.5.0. |
| docs/installation/aks/aks.custom.config.yml | Updates example config to Ascender 25.5.0. |
| docs/configuration/upgrading.md | Updates upgrade documentation examples to 25.5.0. |
| default.config.yml | Updates the default config example to Ascender 25.5.0. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
TheWitness
previously approved these changes
Aug 5, 2026
TheWitness
approved these changes
Aug 5, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 14 out of 14 changed files in this pull request and generated no new comments.
Suppressed comments (2)
playbooks/roles/ascender_install/defaults/main.yml:3
ee_imagesdefault hard-codesghcr.io/ctrliq/ascender-ee, so whenk8s_container_registryis set for offline/internal-registry installs the default EE still points to GHCR and jobs will fail to pull the execution environment. This is inconsistent with the rest of the role/templates which derive image locations fromk8s_container_registry.
image: ghcr.io/ctrliq/ascender-ee:{{ ASCENDER_VERSION }}
playbooks/roles/awx_migrate_ascender/README.md:748
- The table says the default EE name is
Ascender-EE (Latest Ascender Version), but the installer defaults define the EE name asAscender-EE ({{ ASCENDER_VERSION }})(e.g.,Ascender-EE (25.5.0)), so readers won’t be able to match what they see in the CR.
| `ee_images` | Custom EEs from source | 1 default `Ascender-EE (Latest Ascender Version)` | Jobs can't find custom execution environments from source. |
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.
No description provided.