Deployments are handled by a SESTEK Application Support Engineer using a GitOps workflow. Steps that the Support Engineer follows for a successful deployment are listed below.
There are some prerequisites that customers are responsible for prior to the deployment. These prerequisites can be found at Deployment Prerequisites (GitOps).
Preparing the Deployment Manifests
Prior to deployment, the Support Engineer prepares and validates the deployment manifests (Helm-rendered YAMLs, Kustomize overlays, etc.) in a local environment. These manifests describe both the platform components and the Knovvu applications, pinned to the specific versions used for the deployment.
Publishing to the Git Repository
The Support Engineer commits the generated manifests to the Git repository shared with the customer. This repository is the single source of truth for the cluster state. Repository ownership and access are covered in the Deployment Prerequisites (GitOps).
Deploying Platform Applications
The platform applications — the supporting components that Knovvu products depend on — are applied to the cluster first. Depending on the method agreed with the customer, this is done either automatically by the customer's existing GitOps controller, or by SESTEK's apply scripts where no controller is used.
Deploying Knovvu Applications
Once the platform applications are healthy, the Support Engineer publishes the Knovvu application manifests to the repository. They are applied to the cluster the same way as the platform applications, after which the Support Engineer verifies and completes the application configuration.
Ongoing Updates
Subsequent changes — version upgrades, configuration updates — follow the same path: the manifests are updated in the repository and synchronized to the cluster. The repository history therefore reflects the current and past state of the deployment.
Next topic: Deployment Prerequisites (GitOps)