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
  2. Kubernetes Deployment

Alternative 1: Ansible - Fully Automated

Fully automated option uses an ansible playbook which sequentially executes required roles to deploy all initial services.

"Complete Core" playbook performs all activities listed in step-by-step deployment automatically, calling required roles for kubectl actions and Helm chart deployments.

This playbook is available on Rierino repository which can be cloned using your GitHub user that is granted access.

# Clone Git repository with Ansible playbooks
git clone --branch release-[DEPLOYMENT_VERSION] https://[GIT_USER]:[GIT_TOKEN]@github.com/rierino-open/deployment
cd deployment/ansible
# Set Ansible config file according to your cloud service provider
# Run Ansible playbook with required credential variables
ANSIBLE_CONFIG=ansible.[CLOUD].cfg ansible-playbook playbooks/_application/complete-core.yml --extra-vars "[VARIABLE KEY VALUE PAIRS]"

All other Ansible playbook variables can be passed through this automation playbook. At a minimum the following variables are required:

Variable
Definition

gitUser

GitHub user that has been granted access to rierino-open repository

gitToken

GitHub token for your gitUser with read access rights

mavenUser

GitHub user that has been granted access to rierino repository (if different than gitUser)

mavenPassword

GitHub token for your mavenUser with read access rights (if different than gitToken)

gateway_secret

Base64 encoded random text that will be used for encoding and decoding gateway JWTs

keycloak_admin_user

Admin username for Keycloak instance (if used)

keycloak_admin_password

Admin password for Keycloak instance (if used)

keycloak_admin_secret

Admin secret to access Keycloak (if used)

domain

Domain suffix used for external address assignments

rierinoVersion

Rierino platform version to deploy

chartVersion

Helm chart version to deploy (defaults to rierinoVersion)

assetVersion

Deployment assets version to deploy on globals (defaults to rierinoVersion)

PreviousRecommended: Helm - Fully AutomatedNextAlternative 2: Ansible - Step-by-Step

Last updated 6 months ago