Feature Ideas

E.g. installing https://github.com/bitnami/charts/tree/main/bitnami/redis requires to add oci://registry-1.docker.io/bitnamicharts/redis. This fails at the moment. Fortunately, adding https://charts.bitnami.com/bitnami works.

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

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.

Deployments and changes through our operator are currently executed on Kubernetes immediately. We want to enable GitOps to send PRs to a repository instead for reviews and approvals.

For teams using Argo we're planning an integration that visualizes your argo workflows in mogenius for a streamlined interface for the whole application lifecycle.

mogenius RBAC currently uses three default groups as an abstraction to easily configure users and permissions on clusters. We're adding the option to create custom groups with your own permission configuration.

It would be great to have pre-configured metrics whenever you create a new workspace. This could be based on an alert-manager that mogenius adds to your cluster with pre-configured events. In the workspace settings you could configure channels like webhooks, email, slack, Teams.

On tables that summarize Kubernetes resources (like the workspace dashboard, or resource browser), it would be helpful to get a summary of recent resource consumption (CPU, RAM, Traffic). This allows you to easily identify if a pod had unusual resource consumption in the past, indication issues.

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.

If users work with Gitlab CI for test & build pipelines we want to offer an integration so that the workflow, logs, and events can be monitored in mogenius.

WIthin GCP Logging, flask logs become ERROR severity (picture one) but should be INFO severity (picture two)

In products like Apigee it is possible to decide with a toggle, that an authorization header is needed to authenticated with the service. If the toggle is enabled, a token is automatically created and needed to successfully call every HTTP route. In addition it should be possible too, that this token can be used as an API key (GET-Param).