Description

Problem: The make test-pre-release-ossm testing mechanism is broken with the GatewayAPIWithoutOLM feature gate. This was originally implemented in NE-2108. This Enhancement Section describes it as well.

Root cause: Removing OLM means OSSM charts and images are no longer packaged together as a single subscription/bundle.

Previous (OLM) approach:

• Override catalog source → get new sail-operator image
• Sail-operator image contains: embedded Helm charts + references to istiod/envoy images
• Single override point for complete pre-release testing

Current (Sail Library) approach (implemented in NE-2471):

• Helm charts vendored in CIO via go.mod
• istiod/envoy images referenced separately
• No single override point - requires coordinating chart updates + image updates

Two Distinct Use Cases

1. NID Team Pre-Release Testing (Primary)

   Need: Test pre-release OSSM builds before production release

   Current gap: Cannot run e2e-aws-pre-release-ossm with Sail Library approach

   Proposed solutions:

   Option 1: Automated vendor bump in CI

• Add make bump-sail-library target
• CI job: bump library → mirror pre-release images → run tests
• Keeps e2e-pre-release-ossm job functional
• Risk: Vendor bumps may require code changes

   Option 2: Manual PR-based testing

• Drop automated job, use manual smoke-test PRs
• PR: vendor bump + image overrides
• Risk: Slower feedback, manual process

2. Runtime Version Override for Layered Products (Secondary)

   Need: Downstream users (RHOAI, etc.) test different Istio versions at runtime without CIO code changes

   Open question: Do we still need to support runtime version overrides for downstream users (layered products) now that OLM is removed?

• With OLM: Override subscription → get matched charts + images
• With Sail Library: Charts are vendored (fixed at CIO build time), only images can override
• Limitation: Overriding only images may be insufficient if chart changes are required

Acceptance Criteria

1. Implement Option 1 or Option 2 to restore NID team pre-release testing capability
2. Decide whether runtime version override (NE-2108 use case) is still required/feasible
3. Document limitations and process in team documentation

Other Notes

• Does not block initial Sail Library implementation
• Can be addressed post-pencils down
• Chart updates matter: new ENV vars, RBAC, config changes may be required by new istiod versions