Feature Ideas

Add support for repositories that rely on Docker compose.

Add a new feature to clone services to different projects or stages with one click.

Projects could have settings for admins to activate/deactivate certain managed policies for a project. Those policies would be defined and managed by mogenius so that users don't have to configure them manually. Examples: NetworkPolicy to allow cross-namespace communication Prevent services from getting exposed to the internet etc.

You can already create custom service templates with the template library by defining all service settings once and then reusing it to create services. If you already created a service and later decide that it could be useful to have a template for team members, it would be helpful to add a template from an existing service.

Login with SSO (e.g. Azure)

Enable two-factor authentication to add an additional security layer for accounts.

Support creation of managed databases from your cloud provider (e.g. azure, gcp, aws) from inside a project.

Track a historical list of deployments and allow a rollback to a previous version of a service.

Add a log for admins to see historical activity of all users in an organization. Each change to settings of a cluster/project/setting would be documented with details about user and time stamp.

With each Pull Request on a certain branch an environment (= clone of a stage) will be deployed that mirrors your applications based on the recent PR. The idea is to simplify testing and debugging for individual devs. Once the PR is approved the environment will be shut down.

mogenius supports metrics for services showing CPU, resource, and traffic consumption. If custom metrics are used as a developer (e.g. # of db requests) it should be possible to integrate them so that every service displays the desired custom metrics on the "metrics" tab. Users would specify endpoint and query that should be used to display the custom charts.

mogenius has a default pipeline that is used to deploy from Github/Gitlab or container registries to a Kubernetes cluster. Under the hood, templates are used to create the required Kubernetes manifests. In some cases users want to customize the pipeline, e.g. for adding securityContext in certain projects. On that level admins could also decide which registry should be used, which tools to use in the pipeline (vulnerability scan), etc.

The service page abstracts the related Kubernetes resource that are managed by mogenius on the cluster (deployment, service, ingress etc.). For experts, troubleshooting and customization could be improved by providing an expert mode on the service page where you can see and edit the related manifests to a mogenius service.

Use accounts from Google, Github, Gitlab etc. to create an account with mogenius

Currently the API can only be used with tokens from logging in with a certain user. It should be possible to create API Tokens that aren't connected to a specific user account. We're thinking about starting with tokens that are created on project level (in the project settings) with permission on project level. Later we could add tokens on organization level and granular permission handling.