Merge branch 'main' of github.com:mnlipp/VM-Operator

This commit is contained in:
Michael Lipp 2024-07-17 22:46:14 +02:00
commit 605ede7cf3
3 changed files with 7 additions and 7 deletions

View file

@ -1,6 +1,6 @@
---
title: VM-Operator by mnlipp
description: A Kubernetes operator for running virtual machines (notably Qemu VMs) in pods on Kubernetes
title: Run Qemu based VMs on Kubernetes
description: A Kubernetes operator for running virtual machines (notably Qemu VMs) in pods on Kubernetes with a web interface for admins and users.
layout: vm-operator
---

View file

@ -1,5 +1,5 @@
---
title: "VM-Operator: The Manager — Provides the controller and a Web-GUI"
title: "VM-Operator: The Manager — Provides the controller and a web user interface"
layout: vm-operator
---
@ -7,7 +7,7 @@ layout: vm-operator
The Manager is the program that provides the controller from the
[operator pattern](https://github.com/cncf/tag-app-delivery/blob/eece8f7307f2970f46f100f51932db106db46968/operator-wg/whitepaper/Operator-WhitePaper_v1-0.md#operator-components-in-kubernetes)
together with a Web-GUI. It should be run in a container in the cluster.
together with a web user interface. It should be run in a container in the cluster.
## Installation

View file

@ -1,11 +1,11 @@
---
title: "VM-Operator: Web-GUI — Provides easy access to VM management"
title: "VM-Operator: Web user interface — Provides easy access to VM management"
layout: vm-operator
---
# The Web-GUI
The manager component provides a GUI via a web server. The web GUI is
The manager component provides a GUI via a web server. This web user interface is
implemented using components from the
[JGrapes WebConsole](https://jgrapes.org/WebConsole.html)
project. Configuration of the GUI therefore follows the conventions
@ -31,7 +31,7 @@ from the
## User Access
Access to the web GUI is controlled by the login conlet. The framework
Access to the web user interface is controlled by the login conlet. The framework
does not include sophisticated components for user management. Rather,
it assumes that an OIDC provider is responsible for user authentication
and role management.