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.

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.

A library of pre-configured apps and Helm charts for one-click deployments. The templates will be provided both by the mogenius team ("Best of Kubernetes": Prometheus, Argo, IngressControllers, cert-manager, keycloak, etc.), partners, and by each organization for internal applications.

Via the mogenius MCP server (model context protocol) users will be able to integrate mogenius with AI tooling, such as Claude Desktop, Windsurf, Cursor, and more. This way, LLMs get access to your mogenius Workspaces via API to troubleshoot issues on Kubernetes and to browse through resources. Scope of permissions will be read-only for the start with strong focus on security.

Yvuvi

Yhjj

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 alerts 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.

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).