istio/istio.io

Remove Workarounds

Open

#16,962 opened on Oct 30, 2025

View on GitHub
 (3 comments) (0 reactions) (1 assignee)HTML (740 stars) (1,492 forks)batch import
good first issue

Description

When Gateway API releases 1.4.1 or fixes the install, we need to remove the workarounds placed in here: https://github.com/istio/istio.io/pull/16936

The issue is described here: https://github.com/kubernetes-sigs/gateway-api/issues/4156

The fix was to flip to experimental-install.yaml and do server side application. We'll need to revert those workarounds when the fixes are implemented.

Contributor guide

Tech stack
kubernetes
Domain
infrastructuredocumentation
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic Kubernetes knowledgeunderstanding of Gateway APIfamiliarity with istio.io repo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
This issue requires reverting workarounds introduced in PR #16936 once the upstream Gateway API issue (kubernetes sigs/gateway api/issues/4156) is resolved. The workaround involves switching to experimental install.yaml and applying server side. Once the fix is released, revert those changes in the istio.io repository. Check the linked PR and the external issue for context. No additional maintainer clarification needed beyond the described steps.