Redact Example Base64 Secrets in All Languages

[Caesarsage]

Description

Background

Netlify builds have been failing due to “likely secret” detections in example Kubernetes Secret YAML blocks across multiple language docs. These are not real secrets, but their format triggers automated scanning.

What’s Changed

• Replaced all example base64-encoded certificate and key values in affected files (English, Indonesian, Japanese, Korean, Chinese) with clear placeholders:

  data:
    # NOTE: Replace the following values with your own base64-encoded certificate and key.
    tls.crt: "REPLACE_WITH_BASE64_CERT"
    tls.key: "REPLACE_WITH_BASE64_KEY"

(Comment translated for each language.)

Why One PR for All Languages?

Normally, we submit one language per PR. However, since this issue affects all languages in the same way and blocks Netlify builds globally, fixing all at once is more efficient and ensures the site is unblocked for everyone. The change is mechanical and identical in intent.

Why Not Change Netlify Config?

Redacting the example values is more robust and improves clarity for users, making it clear these are placeholders.

Closes: #51395

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	db2b186
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/68626d8aaafe7400089052bb
😎 Deploy Preview	https://deploy-preview-51398--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Arhell]

#51364 (review)
/hold

[tengqm]

please split this into PRs for each and every affected languages.

[Caesarsage]

please split this into PRs for each and every affected languages.

@lmktfy suggested fixing all with 1 PR exception (as described on the description) from sig-docs slack channel as it's blocking Netlify build across.

But there is currently an on going discussions on the Issue to do some settings configuration from the Netlify directly to fix the false positive issue there.

Issue #51395

[lmktfy]

Why One PR for All Languages?

Normally, we submit one language per PR. However, since this issue affects all languages in the same way and blocks Netlify builds globally, fixing all at once is more efficient and ensures the site is unblocked for everyone. The change is mechanical and identical in intent.

Thanks for explaining this clearly. Sorry to hear you had complaints despite doing that.

[lmktfy]

Cancelling the hold from #51398 (review)

This PR proposes making an exception to our normal policy, and explains why. I agree with the exception (which I also proposed). Of course, we can put back that hold if we don't agree with the idea of the exception.

[lmktfy]

/hold cancel

[Okabe-Junya]

Thank you, LGTM
I agree with merging this PR as an exception (without separating by language) because the fact that the build is failing across the entire website is more concerning

nit (does not block this PR): please insert exactly one newline at the end of each file

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tengqm

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• content/bn/OWNERS [tengqm]
• content/en/OWNERS [tengqm]
• content/hi/OWNERS [tengqm]
• content/id/OWNERS [tengqm]
• content/ja/OWNERS [tengqm]
• content/ko/OWNERS [tengqm]
• content/zh-cn/OWNERS [tengqm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[SayakMukhopadhyay]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 48ce8847cb81d4aeeb97d7818d3daf9007bbfd7b