Quick start

From namespace access to publishing an application via GitOps and the GUI.

This guide walks through application delivery in a namespace: get access, prepare the image and manifests, sync state from Git with Argo CD, publish the application, and verify that it works.

1. Get access to the namespace

Sign in to the platform GUI, select a cluster, and confirm that the namespace you need is available. To work from the command line, follow Console: kubeconfig and plugin. For API access, see the API overview.

Mandatory requirement: when authenticating to the platform, enter `username` using the same character case as in the LDAP directory.

On the namespace dashboard you can see workloads, services, ingresses, metrics, quotas, events and the transition to Argo CD if the shturval-cd module is installed and a project has been created for the namespace.

2. Prepare images and manifests

Before delivering the application, build a container image, publish it to a registry accessible to the cluster, and specify a stable tag in the manifests. Requirements for the image and imagePullSecrets are described in the section What to prepare before deployment, and connecting a private registry - in the instructions How to connect a private registry.

For production workloads, keep manifests in Git, set requests and limits, configure health checks and avoid the latest tag; these rules are collected in Best Practices for Developers.

3. Set up delivery via Git and Argo CD

The platform provides application delivery via GitOps: Argo CD synchronizes the state of the cluster with a Git repository of manifests or Helm charts. How the platform connects Argo CD clusters, projects and access rights is described in the section How Shturval and Argo CD are connected; it also describes the transition to Argo CD from the namespace GUI.

To create or verify a workload manually in the GUI, see How to deploy an application. It covers Deployment, StatefulSet, DaemonSet, Job, CronJob, and Pod.

4. Publish the application

After successful deployment, open access to the application via Service, and configure Ingress for HTTP/HTTPS access from outside the cluster. Selecting a service type, preparing a TLS Secret, and checking routing are described in the instructions How to publish an application.

If the application needs to scale, configure the number of replicas, HPA, or VPA in the Modify and scale section.

5. Check status and diagnose failures

For day-to-day checks, use the namespace dashboard. It shows workload status, connections to Service and Ingress, metrics, quotas, and events. When something fails, open the pod or workload page to read container logs, review events, or use the interactive pod terminal.

For log checks, events, the pod terminal, and common errors such as CrashLoopBackOff, ImagePullBackOff, or Ingress issues, see Workload troubleshooting.

Glossary →