Skip to content

docs(k8s): align dashboard guidance with pinned Kubespray - #1424

Merged
michael-balint merged 1 commit into
masterfrom
dholt/k8s-dashboard-https
Oct 19, 2026
Merged

michael-balint merged 1 commit into
masterfrom
dholt/k8s-dashboard-https

Conversation

@dholt

@dholt dholt commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Clarify that the pinned Kubespray v2.31.0 does not install Kubernetes Dashboard.
  • Remove ineffective dashboard settings from the sample inventory and the offline-cache download command.
  • Replace the legacy helper setup instruction with separate-install guidance, including air-gapped deployment considerations and the helper's existing assumptions.

Validation

  • Role lint: passed, 323 files processed.
  • Playbook syntax checks: passed, 12 playbooks.
  • Changed configuration YAML parse, shell syntax, and whitespace checks: passed.
  • Confirmed the pinned Kubespray has no dashboard add-on consumer.
  • Independent review found no blocking issues or private information. The automated content scan flags generic Kubernetes authentication terminology; independent review confirmed it is a false positive, not sensitive data.

Notes

No dashboard access code changed. HTTPS behavior has not been reproduced or verified by this change. This does not close the separate HTTPS report.

Release-note draft

Correct Kubernetes Dashboard documentation and remove obsolete example settings for the pinned Kubespray release. Dashboard installation is a separate operator-managed step.

Remove ineffective dashboard settings and explain separate installation.
Keep the legacy HTTPS helper unchanged.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@dholt
dholt requested a review from michael-balint October 16, 2026 17:33
@michael-balint
michael-balint merged commit f19d7a2 into master Oct 19, 2026
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants