Add Automatic Local Cluster Management to Jumpstarter Admin CLI

docs/source/getting-started/guides/setup-distributed-mode.md

@@ -27,7 +27,7 @@ connection between an exporter and client without physical hardware.
 
 You need the [service](../../introduction/service.md) running in a Kubernetes
 cluster with admin access. For installation instructions, refer to the
-[installation guide](../installation/service.md).
+[installation guide](../installation/service/index.md).
 
 ## Instructions
 

docs/source/getting-started/installation/index.md

@@ -4,11 +4,11 @@ This section provides guidance on installing Jumpstarter components in your
 environment. The guides cover:
 
 - [Packages](packages.md): Installing Jumpstarter software packages
-- [Service](service.md): Setting up Jumpstarter as a Kubernetes service
+- [Service](service/index.md): Setting up Jumpstarter as a Kubernetes service
 
 ```{toctree}
 :maxdepth: 1
 :hidden:
 packages.md
-service.md
+service/index.md
 ```

docs/source/getting-started/installation/service/index.md

@@ -0,0 +1,20 @@
+# Service
+
+This section explains how to install and configure the Jumpstarter service in your Kubernetes cluster. The service enables centralized management of your Jumpstarter environment.
+
+## Getting Started
+
+For most users, we recommend starting with a **local installation** to get familiar with Jumpstarter before moving to production deployments.
+
+```{toctree}
+:maxdepth: 2
+
+service-local.md
+service-production.md
+```
+
+## Quick Start
+
+**New to Jumpstarter?** Start with the [Local Installation](service-local.md) guide to get up and running quickly on your development machine.
+
+**Ready for production?** See the [Production Deployment](service-production.md) guide for Kubernetes and OpenShift clusters with proper security, monitoring, and ingress configurations.