Kstatus compatibility

[fergian94]

Problem

Since the introduction of kstatus in Helm 4, custom resources can now be monitored during install. For HTTPProxy and ExtensionService CRs, the Valid condition type is not recognized by kstatus logic,
which specifically looks for a Ready condition. This causes Helm to assume resources are immediately ready, defeating the purpose of --wait.

Solution

Mirror the Valid condition into an additional Ready condition, which kstatus recognizes. The Valid condition is preserved for backward compatibility and Contour's existing tooling, while the Ready
condition enables proper integration with Helm 4, Flux, Argo CD, and kubectl wait.

Cleanup

Removed the workaround for #7391 in hack/generate-crd-yaml.sh as it is no longer needed with k8s.io/api v0.35.4.

[codecov]

Codecov Report

❌ Patch coverage is 44.44444% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.31%. Comparing base (895e3a2) to head (0593def).
⚠️ Report is 44 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/status/extensionstatus.go	0.00%	10 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7648      +/-   ##
==========================================
- Coverage   82.32%   82.31%   -0.02%     
==========================================
  Files         130      130              
  Lines       15624    15891     +267     
==========================================
+ Hits        12863    13081     +218     
- Misses       2478     2523      +45     
- Partials      283      287       +4     

Files with missing lines	Coverage Δ
internal/status/proxystatus.go	84.90% <100.00%> (+2.68%)	⬆️
internal/status/extensionstatus.go	48.14% <0.00%> (-10.95%)	⬇️

... and 17 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[tsaarni]

Thank You @fergian94 for contributing!

I have now spent some time studying this topic, and as we discussed elsewhere, I can take over implementing it.

I propose using a different approach than currently suggested: instead of adding a Ready condition to mirror the Valid condition, we should add Stalled condition as recommended in the kstatus docs. This avoids having two redundant conditions for single success status and it can indicate failure using the abnormal-true pattern which clients can recognize immediately when it becomes true (failure becomes active), instead of timing out on a normal-true condition (no success within reasonable period of time).

We also need to implement .status.observedGeneration at the top level and add end-to-end tests using the actual kstatus library to ensure it works correctly.

This is being addressed in #7664, so I think we can close this PR.

[fergian94]

Thank you Tero for taking over this PR. I will follow it up with enthusiasm. I really appreciate your commitment! Il Mar 11 Ago 2026, 20:32 Tero Saarni ***@***.***> ha scritto:

…

Closed #7648 <#7648>. — Reply to this email directly, view it on GitHub <#7648?email_source=notifications&email_token=AOTRE4MLRHS575BAO2FMFHT5JNRFNA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTEOJSHE3TSNJZGA2TLJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FMMZXW65DFOJPWG3DJMNVQ#event-29297959055>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOTRE4LJSI2NY75ICNZ24IT5JNRFNAVCNFSNUABFKJSXA33TNF2G64TZHMYTAOBUGYZDQMRSHNEXG43VMU5TKMBRGA3TEOBUGQ32C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AOTRE4N2V6NLWE6PBNLP6G35JNRFNA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTEOJSHE3TSNJZGA2TLJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FKMZXW65DFOJPWS33T> and Android <https://github.com/notifications/mobile/android/AOTRE4KWJEORE7X3LZQMIWT5JNRFNA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTEOJSHE3TSNJZGA2TLJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FOMZXW65DFOJPWC3TEOJXWSZA>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>