Skip to content

[docs-scanner] Inconsistent Kubernetes provisioner name in ECI docs #25975

Description

@docker-agent

Files:

  • content/manuals/enterprise/security/hardened-desktop/enhanced-container-isolation/faq.md
  • content/manuals/enterprise/security/hardened-desktop/enhanced-container-isolation/limitations.md

Issue

The Enhanced Container Isolation documentation uses inconsistent capitalization for the Kubernetes provisioner name, and contradicts the authoritative Kubernetes documentation.

In faq.md (line 63):

  • Kubernetes with the Kind provisioner

In limitations.md (line 81):

Use the newer Docker Desktop Kubernetes "KinD" provisioner

However, the authoritative Kubernetes documentation at content/manuals/desktop/use-desktop/kubernetes.md consistently uses lowercase "kind" throughout:

  • In the table: "| Feature | kubeadm | kind |"
  • In the text: "Docker Desktop Kubernetes can be provisioned with either the kubeadm or kind provisioners."
  • In configuration examples: "if Docker Desktop Kubernetes is configured in kind mode"

Why this matters

Readers cross-referencing between the ECI documentation and the Kubernetes documentation will encounter three different capitalizations (Kind, KinD, kind) for the same provisioner, creating confusion about whether these refer to the same thing or different features. The inconsistency undermines confidence in the documentation's accuracy.

Suggested fix

Update both ECI files to use lowercase "kind" (with code formatting) to match the Kubernetes documentation:

In faq.md:

  • Change "Kubernetes with the Kind provisioner" to "Kubernetes with the kind provisioner"

In limitations.md:

  • Change "Docker Desktop Kubernetes "KinD" provisioner" to "Docker Desktop Kubernetes kind provisioner"
  • Change "The KinD provisioner" to "The kind provisioner"

Found by nightly documentation quality scanner

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions