Skip to content

docs: fix dead links to the ALS example, CNCF supply chain paper and ExternalDNS guide #10464

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sarankumar1325 wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −8
Open

docs: fix dead links to the ALS example, CNCF supply chain paper and ExternalDNS guide #10464

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion site/content/en/latest/tasks/observability/proxy-accesslog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,7 +143,7 @@ curl -s "http://$LOKI_IP:3100/loki/api/v1/query_range" --data-urlencode "query={
## gGRPC Access Log Service(ALS) Sink

Envoy Gateway can send logs to a backend implemented [gRPC access log service proto](https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/accesslog/v3/als.proto).
There's an example service [here](https://raw.githubusercontent.com/envoyproxy/gateway/main/examples/kubernetes/envoy-als.yaml), which simply count the log and export to prometheus endpoint.
The OpenTelemetry Collector's [Envoy ALS receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/envoyalsreceiver) implements this service. The OpenTelemetry Collector installed by the `gateway-addons-helm` chart enables it on port 9000, which is the backend used below.

The following configuration sends logs to the gRPC access log service:

Expand Down
4 changes: 2 additions & 2 deletions site/content/en/latest/tasks/security/threat-model.md
View file
Open in desktop

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion site/content/en/latest/tasks/security/tls-cert-manager.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -320,7 +320,7 @@ Together with cert-manager, this can be used to fully automate hostname manageme
It can use various source resources, among them Gateway Routes.
Just specify a Gateway Route resource, let ExternalDNS create the domain records, and then cert-manager the TLS certificate.

[The tutorial on Gateway API](https://kubernetes-sigs.github.io/external-dns/latest/tutorials/gateway-api/) uses kubectl.
[The tutorial on Gateway API](https://kubernetes-sigs.github.io/external-dns/latest/docs/sources/gateway-api/) uses kubectl.
They also have a [Helm chart](https://github.com/kubernetes-sigs/external-dns/blob/master/charts/external-dns/README.md), which is easier to customize.
The only thing relevant to Envoy Gateway is to set the sources:

Expand Down
2 changes: 1 addition & 1 deletion site/content/en/v1.9/tasks/observability/proxy-accesslog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,7 +143,7 @@ curl -s "http://$LOKI_IP:3100/loki/api/v1/query_range" --data-urlencode "query={
## gGRPC Access Log Service(ALS) Sink

Envoy Gateway can send logs to a backend implemented [gRPC access log service proto](https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/accesslog/v3/als.proto).
There's an example service [here](https://raw.githubusercontent.com/envoyproxy/gateway/main/examples/kubernetes/envoy-als.yaml), which simply count the log and export to prometheus endpoint.
The OpenTelemetry Collector's [Envoy ALS receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/envoyalsreceiver) implements this service. The OpenTelemetry Collector installed by the `gateway-addons-helm` chart enables it on port 9000, which is the backend used below.

The following configuration sends logs to the gRPC access log service:

Expand Down
4 changes: 2 additions & 2 deletions site/content/en/v1.9/tasks/security/threat-model.md
View file
Open in desktop

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion site/content/en/v1.9/tasks/security/tls-cert-manager.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -320,7 +320,7 @@ Together with cert-manager, this can be used to fully automate hostname manageme
It can use various source resources, among them Gateway Routes.
Just specify a Gateway Route resource, let ExternalDNS create the domain records, and then cert-manager the TLS certificate.

[The tutorial on Gateway API](https://kubernetes-sigs.github.io/external-dns/latest/tutorials/gateway-api/) uses kubectl.
[The tutorial on Gateway API](https://kubernetes-sigs.github.io/external-dns/latest/docs/sources/gateway-api/) uses kubectl.
They also have a [Helm chart](https://github.com/kubernetes-sigs/external-dns/blob/master/charts/external-dns/README.md), which is easier to customize.
The only thing relevant to Envoy Gateway is to set the sources:

Expand Down
Loading