Previously, only a Gateway resource was defined as a supported
attachment type. This PR updates the API docs to include a Service
as a supported type and also fixes an incorrect link to Gateway API
documentation.
Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io>
* Allow defining CRDs from a single version
Part of https://github.com/istio/api/issues/3127. Goes with a
corresponding tools change; this will fail until that merges.
This just shows DR. The tool will support both the new and old way (we
can remove the old way if we want), so we don't have to move everything
at once. We will, though. I kept it to one so its easy to review first.
* Move all APIs over
* policy attachment: allow `targetRefs`
Based on https://github.com/kubernetes-sigs/gateway-api/pull/2966. Note
that we do not HAVE to follow the GatewayAPI here; we can make our own
decision. There is, however, a general desire to allow multiple for
ergonomics.
In this proposal, I hide `targetRef`, but the API will remain + be
implemented forever. Implementation cost here is near zero, as we can
easily translate it to a single `targetRefs`; we just hide from docs to
push users toward the new ones.
* codegen
* Align documentation
* consistency
* Fix indentation of jwt doc
* Update comment line of jwtrule
* Fix indentation of jwt doc
* Update comment line of jwtrule
* Rebase with latest master
---------
Co-authored-by: Sathish Swaminathan <sathish.swaminathan@ibm.com>
Running make gen for some other change resulted in many additional
changes showing up in my local repo. So pushing a separate review for the same.
Signed-off-by: Faseela K <faseela.k@est.tech>
* Telemetry API: Add TrafficDirection selection to Tracing/Logging
* use workloadmode instead of a new enum
* add release note
* move match clauses to top
* fix telemetry doc
* add release notes
* Update releasenotes/notes/fix-telemetry-doc.yaml
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update releasenotes/notes/fix-telemetry-doc.yaml
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Update releasenotes/notes/fix-telemetry-doc.yaml
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
* Add alpha Telemetry API to allow metrics customization
* rebase + update
* remove telemetryrulematch and add access logging
* refactor tag overrides and address comments
* more refactoring
* updates to match comments
* remove all_metrics from API
* add metric selector with client/server terminology
* add comment for TagOverride
* Add release note
* clean up some comments
* fix oneof name
* fix release note
* address review comments
* clarify logging enablement example
* Add initial Telemetry API definition
* fix names and comments
* Rename TracingConfig to Tracing
* Remove TelemetryProviders and consolidate to just Tracing providers
* add new extension providers to oneof
* Remove providers from telemetry API
* Add release note
* Address comments
* Add back providers, remove match, simplify Trace API
* Collapse TracingRule into Tracing and remove deprecations in ProxyConfig
* Move from address to service + port in providers
* Remove exclude_mesh_tags
* Revert to boolean control of span reporting
* Cleanup documentation
* Replace subdomain with telemetry type
Jacob Delgado