mirror of
https://github.com/coredns/coredns.git
synced 2026-04-17 01:15:33 -04:00
Fix broken links (#8051)
Signed-off-by: peppi-lotta <peppi-lotta.saari@est.tech>
This commit is contained in:
@@ -65,7 +65,7 @@ used.
|
||||
as a new secret in AWS Secrets Manager with the specified name and description. CoreDNS will then fetch
|
||||
the key data from AWS Secrets Manager when using the `key aws_secretsmanager` directive.
|
||||
|
||||
[AWS SDK for Go V2](https://aws.github.io/aws-sdk-go-v2/docs/configuring-sdk/#specifying-credentials) is used
|
||||
[AWS SDK for Go V2](https://docs.aws.amazon.com/sdk-for-go/v2/developer-guide/configure-auth.html) is used
|
||||
for authentication with AWS Secrets Manager. Make sure the provided AWS credentials have the necessary
|
||||
permissions (e.g., `secretsmanager:GetSecretValue`) to access the specified secrets in AWS Secrets Manager.
|
||||
|
||||
|
||||
@@ -131,7 +131,7 @@ If you prefer, you can use `curl` to populate the `etcd` server, but with `curl`
|
||||
endpoint URL depends on the version of `etcd`. For instance, `etcd v3.2` or before uses only
|
||||
[CLIENT-URL]/v3alpha/* while `etcd v3.5` or later uses [CLIENT-URL]/v3/* . Also, Key and Value must
|
||||
be base64 encoded in the JSON payload. With `etcdctl` these details are automatically taken care
|
||||
of. You can check [this document](https://github.com/coreos/etcd/blob/master/Documentation/dev-guide/api_grpc_gateway.md#notes)
|
||||
of. You can check [this document](https://github.com/etcd-io/website/blob/main/content/en/docs/v3.2/dev-guide/api_grpc_gateway.md)
|
||||
for details.
|
||||
|
||||
### Reverse zones
|
||||
|
||||
@@ -69,12 +69,12 @@ kubernetes [ZONES...] {
|
||||
If this option is omitted all namespaces are exposed
|
||||
* `namespace_labels` **EXPRESSION** only expose the records for Kubernetes namespaces that match this label selector.
|
||||
The label selector syntax is described in the
|
||||
[Kubernetes User Guide - Labels](https://kubernetes.io/docs/user-guide/labels/). An example that
|
||||
[Kubernetes Documentation - Labels and Selectors](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/). An example that
|
||||
only exposes namespaces labeled as "istio-injection=enabled", would use:
|
||||
`labels istio-injection=enabled`.
|
||||
* `labels` **EXPRESSION** only exposes the records for Kubernetes objects that match this label selector.
|
||||
The label selector syntax is described in the
|
||||
[Kubernetes User Guide - Labels](https://kubernetes.io/docs/user-guide/labels/). An example that
|
||||
[Kubernetes Documentation - Labels and Selectors](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/). An example that
|
||||
only exposes objects labeled as "application=nginx" in the "staging" or "qa" environments, would
|
||||
use: `labels environment in (staging, qa),application=nginx`.
|
||||
* `pods` **POD-MODE** sets the mode for handling IP-based pod A records, e.g.
|
||||
|
||||
Reference in New Issue
Block a user