Prerequisites
- A Kubernetes cluster with at least 1 CPU and 1 GB of memory available.
- Credentials for pulling the mogenius images from the container registry (see below).
- The traefik ingress controller.
- A working local installation of Helm.
- A MySQL server (optional).
Quickstart
For a quick installation of the mogenius platform with defaults where possible, follow these steps.Create a Namespace
On the cluster where you’re installing the mogenius platform, create a new namespacemogenius-platform. All following commands target this namespace.
Create Secrets
The platform services require a few secrets containing critical credentials that aren’t created by the Helm chart. The following secrets are required for the minimum configuration. Additional secrets can be used when working with more sophisticated Helm chart configurations. The commands below create each secret directly withkubectl. They generate secure random values on the fly using openssl, so you can run them as-is and only replace the placeholders that are marked with <...>.
The encryption key
MO_CORE_NEST__SSH_SYM_ENC_KEY must be identical in the mo-platform-shared and mo-platform-user-secret secrets. The commands below generate it once into a shell variable and reuse it, so run them in the same terminal session.mo-registry-credentials secret of type kubernetes.io/dockerconfigjson. Replace the placeholders with the values from your subscription.
MO_CORE_NEST__SSH_SYM_ENC_KEY reuses the $MO_ENC_KEY from step 3).
MO_USER_NEST__SYSTEM_ADMIN_EMAIL — the email address to log in with your admin user.
MO_USER_NEST__SYSTEM_ADMIN_PASSWORD — the password for your admin user.
MO_CORE_NEST__SSH_SYM_ENC_KEY — the same encryption key set in the mo-platform-shared secret.
MO_USER_NEST__JWT_PRIVATE — the base64-encoded private key for signing JWTs.
MO_USER_NEST__JWT_PUBLIC — the base64-encoded public key for verifying JWTs.
MO_USER_NEST__SESSION_SECRET — a secure random secret for session handling.
Prepare your values.yaml
The Helm chart supports wide range of values that you can use to configure your installation of the mogenius platform. Skip to values for a full reference of the chart. Below is an examplevalues.yaml for a minimal setup to install the mogenius platform in a development environment. Make sure to review the configuration and ensure that it matches your infrastructure.
values.yaml quickstart example
Deploy the Helm chart
Run the following command on your cluster to install the Helm chart with your values.yaml.Access the mogenius web interface
Check the status of the installation and make sure all Pods are starting properly.Running, access the mogenius platform with the hostname you specified in your Ingress (e.g. mogenius.yourdomain.com). You can log in with the credentials of your admin user.
Next steps
Now that mogenius is up and running you can prepare the platform for your team. Check out the following resources as next steps:- Quickstart guide for connecting your first cluster and getting started with Workspaces.
- Enable Single Sign-On to enable your team joining the mogenius platform.
- Configure GitOps for enabling Git-based workflows in mogenius using Argo CD.
Support
Need help setting up the mogenius platform? Contact us via support@mogenius.com.Values
Global Settings
Ingress
Default ingress annotations:
Feature Toggles
Platform Services
mo_platform (Frontend)
mo_platform_api (API Service)
mo_platform_user (User Service)
OpenID Configuration: