Repkit Studio Examples

Why Teams Use Repkit Studio

Faster triage for app issues
Teams can move from cluster overview to namespace-level resources and graph relationships without jumping between multiple tools.
Reusable delivery patterns
App templates become standardized assets that can be reused across projects, reducing one-off YAML drift.
More operational clarity
Notifications and activity history provide a lightweight change trail for who applied what and when.
Lower onboarding friction
New engineers can understand service topology and template usage faster with visual and project-level context.
Safer scaling of environments
The same template can be previewed, applied, and stored as a project asset for repeatable rollout workflows.

Page By Page Overview

Clusters

See all local kube contexts in one grid. Group by provider, reorder sections, and quickly open a cluster or remove stale contexts from your kubeconfig.

Cluster Topology

Switch between table and graph at cluster scope. Spot namespace load by pods/deployments, hide system operators by default, and open a namespace with one click.

Namespace Resources

Drill into one namespace for deployments, pods, and services. Resource ordering is configurable, and YAML inspect/edit/apply is available for key resource types.

Namespace Graph

Visualize ingress to service to pods and deployment relationships with resource toggles and saved positions. Useful for fast dependency checks during incidents.

Projects

Group reusable app assets, linked repos, and environments. Deploy project assets into named environments with missing variable checks before apply.

Templates

Create reusable YAML templates with typed placeholders and optional defaults, then apply directly to a cluster or attach to a project for reuse.

Mini Topology Example

Small sample of the graph relationship style used in namespace view.

Internet
  |
Ingress (app.example.com:443)
  |
Service (app-svc:80 -> 8080)
  |
Pods (app-7c6d4, app-7c6d5)
  |
Deployment (app)
  |
PVC (app-data)

Optional Screenshot Placeholders

<clusters-overview.png> page: clusters
<cluster-topology.png> page: cluster
<namespace-resources.png> page: namespace
<namespace-graph.png> page: namespace
<projects-overview.png> page: projects

Template Syntax Overview

Use placeholders to make templates reusable across clusters, namespaces, and projects.

String placeholder: $APP_NAME
Typed placeholder: INT($REPLICAS), BOOL($ENABLED), DICT($RESOURCES), LIST($ARGS)
Optional with fallback: INT(OPTIONAL($REPLICAS, 1))
Optional without fallback: OPTIONAL($ANNOTATIONS) (resolves to undefined if empty)
Nested type shape: LIST(DICT()), DICT(LIST())

Reusable Template Example

apiVersion: apps/v1
kind: Deployment
metadata:
  name: $APP_NAME
  namespace: $NAMESPACE
spec:
  replicas: INT(OPTIONAL($REPLICAS, 1))
  selector:
    matchLabels:
      app: $APP_NAME
  template:
    metadata:
      labels:
        app: $APP_NAME
      annotations: DICT(OPTIONAL($POD_ANNOTATIONS, {}))
    spec:
      containers:
        - name: app
          image: $IMAGE
          ports:
            - containerPort: INT(OPTIONAL($CONTAINER_PORT, 8080))
          args: LIST(OPTIONAL($ARGS, []))
          env: LIST(OPTIONAL($ENV, []))
          resources: DICT(OPTIONAL($RESOURCES, {}))