From b2f09a41ade1ca3d16a8ef11427933a289109a76 Mon Sep 17 00:00:00 2001 From: Stephanie Hingtgen Date: Wed, 24 Sep 2025 09:47:54 -0600 Subject: [PATCH] Docs: kubectl fix typo (#111555) --- contribute/architecture/k8s-inspired-backend-arch.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contribute/architecture/k8s-inspired-backend-arch.md b/contribute/architecture/k8s-inspired-backend-arch.md index 4d16c6e8118..7dfb95873c7 100644 --- a/contribute/architecture/k8s-inspired-backend-arch.md +++ b/contribute/architecture/k8s-inspired-backend-arch.md @@ -249,7 +249,7 @@ The frontend code is also updated gradually. As Resource API endpoints stabilize ## 5. So does it all mean I can point `kubectl` directly at the Grafana server and use it to create dashboards? -**It's not an officially supported of accessing Grafana APIs, but yes.** `kubectl` requires `server.protocol` set to `https`. Enabling `https` causes Grafana to configure its web server with TLS certificates, either loading specified certificate/key files or generating self-signed ones if none are provided. +**It's not an officially supported way of accessing Grafana APIs, but yes.** `kubectl` requires `server.protocol` set to `https`. Enabling `https` causes Grafana to configure its web server with TLS certificates, either loading specified certificate/key files or generating self-signed ones if none are provided. The easiest way to use `kubectl` is under a dev-mode-only, experimental `grafanaAPIServerEnsureKubectlAccess` feature flag: