LogoLogo
Home
Installation
Installation
  • Introduction
  • Deployment Alternatives
    • Kubernetes Deployment
      • Prerequisites
      • Recommended: Helm - Fully Automated
      • Alternative 1: Ansible - Fully Automated
      • Alternative 2: Ansible - Step-by-Step
      • Cloud Specific Details
    • Sandbox VM Deployment
      • AWS AMI - Developer Lite
    • Local Test Deployment
  • Artifacts
    • Helm Charts
      • Umbrella Charts
        • Ready Core
        • Ready CMS
        • Ready PIM
      • Initialization Charts
        • Namespaces
        • Global
        • Loader
        • Deployer API
        • Deployer
      • Application Charts
        • Admin UI
        • Gateway
        • Spring Runner
        • Samza Runner
        • Socket Runner
        • Storefront
      • Batch Charts
        • Cron
        • Job
      • Deprecated
        • Authentication
        • Session
        • H2O Wave
        • Wave App
    • Deployment Assets
      • Deprecated
    • Docker Repository
      • Front-end Images
      • Back-end Images
      • Python Images
    • Maven Repository
      • Core Packages
      • Runner Packages
      • Processors Packages
      • Custom Packages
      • Gateway Packages
    • Python Packages
    • Terraform Configurations
    • Ansible Playbooks
      • Initialization Playbooks
      • Application Playbooks
      • Enabler Playbooks
  • Administration
    • Cost & License Management
    • Secrets & Config Management
    • Testing & Health-Check
    • Logs & Traces & Metrics
    • Backup & Recovery
    • Technical Support
Powered by GitBook

© Rierino Software Inc. 2025. All rights reserved.

On this page
  1. Deployment Alternatives

Kubernetes Deployment

Initial k8s deployment steps are used to install Rierino core platform, which then facilitates easy installation of any new modules through its UI

PreviousDeployment AlternativesNextPrerequisites

Last updated 6 months ago

Rierino deployments start with installation of systems (such as database, messaging systems), followed by either the or deployment option based on requirements and preferences.

Deployment activities are designed to follow a number key principles:

  • All deployments are coordinated by a central deployer component, which simplifies monitoring, resource and security management

  • Deployment is split into various namespaces, providing ease of monitoring and domain-specific management of configurations and secrets

  • All infrastructure specific details (e.g. IP addresses) and credentials are only stored in config maps and secrets to isolate them from application level data layer

  • After the initial deployment, it is possible to deploy new runners directly through the platform itself, hence these steps are only required once throughout the platform's lifecycle

  • Any step in this initial deployment can be customized through parameter values or even forking deployment repositories and modifying helm charts, ansible playbooks and deployment assets

Typical deployment, after the prerequisites are completed, takes around 30-60 minutes for the fully automated and 2-3 hours for the step-by-step option, depending on the configuration customizations preferred.

While all deployment steps are automated and required commands are listed in this document, it is recommended to have the following skills for executing these steps:

  • Basic understanding of cloud, networking, kubernetes and helm charts

  • Experience with Terraform and Ansible (optional)

  • Familiarity with the cloud provider's marketplace and kubernetes services

prerequisite
fully automated
step-by-step