docs: link webhook-concurrency.md and gateway-api-webhook.md from navigation
What type of PR is this?
/kind docs
What this PR does / why we need it:
Two existing documentation files in examples/ were orphaned — they were not referenced from examples/README.md, the Helm chart README, or any other markdown navigation. Users following the documented onboarding path would not discover them.
This PR adds the two cross-references suggested by the issue:
- An Additional Guides section in
examples/README.mdlinking both files. - A pointer in
internal/manifests/charts/kelos/README.md(alongside the existing webhook configuration section) togateway-api-webhook.mdfor the Gateway API deployment alternative and towebhook-concurrency.mdformaxConcurrencybehavior.
Verified that the docs still match implementation before linking them:
internal/webhook/handler.go:373still logs"Max concurrency reached, dropping webhook event"and continues (HTTP 200 path) — matcheswebhook-concurrency.md.internal/manifests/charts/kelos/values.yamlexposeswebhookServer.gateway.{enabled,gatewayClassName,gatewayName,host,annotations}— matches the values shown ingateway-api-webhook.md.
Which issue(s) this PR is related to:
Fixes #1150
Special notes for your reviewer:
Scope is intentionally limited to the two locations called out in the issue's "Suggested Fix" — no other navigation files (README.md, docs/reference.md, docs/integration.md) were touched.
Does this PR introduce a user-facing change?
docs: cross-reference webhook-concurrency.md and gateway-api-webhook.md from examples/README.md and the Helm chart README so they are discoverable from the documented onboarding path.
Summary by cubic
Added links to examples/webhook-concurrency.md and examples/gateway-api-webhook.md in examples/README.md and the Helm chart README so these guides are discoverable from the onboarding path. Aligns with issue #1150 by surfacing concurrency behavior and the Gateway API alternative near existing webhook docs.