From 302f6773a73daab6249cf891c3eee176cb5b1a9a Mon Sep 17 00:00:00 2001 From: Aman Raj Date: Wed, 17 Jun 2026 04:36:37 +0530 Subject: [PATCH] docs: use stringData in the DigitalOcean DNS01 Secret example The DigitalOcean ACME DNS01 example used a base64-encoded `data` field plus separate base64 instructions, which users found confusing (#354). Switch the example to `stringData` so the token is given in plain text, matching the Cloudflare example, and drop the now-redundant base64 encoding steps. Also fixes a malformed closing code fence. Closes #354 Signed-off-by: Aman Raj --- .../configuration/acme/dns01/digitalocean.md | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/content/docs/configuration/acme/dns01/digitalocean.md b/content/docs/configuration/acme/dns01/digitalocean.md index 4d6c155863c..e4cea1458fb 100644 --- a/content/docs/configuration/acme/dns01/digitalocean.md +++ b/content/docs/configuration/acme/dns01/digitalocean.md @@ -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