Feature Ideas

Login with SSO (e.g. Azure)

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.

Each workspace comes with built-in metrics for CPU, RAM, and traffic usage. To support custom metrics charts that are created from OpenTelemetry we want to enable OpenTelemetry support.

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.

The workload manager in the clusters page and the resource browser in a workspace are currently based on simple tables that have UX limitations. Real-time updates aren't possible and the navigation experience can slow you down in quickly finding a certain resource. We're updating the navigations and tables to make it fast to navigate, and responsive for real-time data.

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.

Logs for a Pods are currently in available on detail pages for deployments, which aggregate all pods in one place. If you open the blank resource page of a single pod, it only has YAML and describe at the moment. We're adding logs to this page to make them available whenever you open a detail page with a pod.

We're streamlining the UI for pipeline starters to make it more self-explanatory and easier to navigate.

Deployments have an abstracted and easy-to-use UI that displays data from several Kubernetes resources in one place. This UI isn't available yet for DaemonSets, StatefulSets, and Cronjobs. We're updating their detail pages to provide the same user experience like with deployments.

Vollumes and mounts are currently only available in the resource browser which makes it more complicated to understand and create volume mounts in a deployment. We're adding this as a tab to the container settings, so that you can add volumes and volume mounts right from there.

Deployment settings are abstracted in a simple user interface based on form fields that provide more guidance and ease onboarding of users on Kubernetes. However, sometimes you want to go deeper, or manage the resources that are behind the abstracted service view. We're adding a toggle that allows you to switch to a raw YAML view with a resource topology. This way, you can modify YAML directly in the web editor, and navigate through dependent resources (like ingress, service, configmaps, etc).

On top of the existing Helm Management Feature in the cluster admin area, we're adding the option for teams to deploy Helm charts from within a workspace. It will be a new deployment type in addition to YAML manifests, container images, and pipeline starters. Users can select Helm charts from existing Helm repositories on the cluster, provide a custom values yaml and deploy the charts. This way, admins can control the repositories that are available for the workspaces.

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.