Skip to content

docs: use stringData in the DigitalOcean DNS01 Secret example #2159

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
yugstar wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: use stringData in the DigitalOcean DNS01 Secret example #2159

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
16 changes: 7 additions & 9 deletions content/docs/configuration/acme/dns01/digitalocean.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,23 +12,21 @@ apiVersion: v1
kind: Secret
metadata:
name: digitalocean-dns
data:
type: Opaque
stringData:
# insert your DO access token here
access-token: "base64 encoded access-token here"
```
access-token: "your-access-token"
```

The access token must have write access.

Using `stringData` lets you provide the token in plain text; Kubernetes
base64-encodes it for you when the `Secret` is created.

To create a Personal Access Token, see [DigitalOcean documentation](https://docs.digitalocean.com/reference/api/create-personal-access-token/).

Handy direct link: https://cloud.digitalocean.com/account/api/tokens/new

To encode your access token into base64, you can use the following

```bash
echo -n 'your-access-token' | base64
```

```yaml
apiVersion: cert-manager.io/v1
kind: Issuer
Expand Down