VM-Operator/dev-example
2025-02-16 21:06:49 +01:00
..
.gitignore Add maintenance script. 2025-02-02 16:50:52 +01:00
config.yaml Add console access to VM management. 2025-01-29 17:33:16 +01:00
gen-pool-vm-crds.sh Move test to tc1. 2024-11-17 12:21:16 +01:00
kustomization.yaml Add users for pool testing. 2025-01-25 15:14:58 +01:00
pool-action.sh Add usage info. 2025-02-16 21:06:49 +01:00
Readme.md Fix trailing space. 2025-01-30 22:32:51 +01:00
test-pool.yaml Allow users to start assigned VMs. 2025-01-31 15:26:42 +01:00
test-vm-display-secret.yaml Add viewer conlet (#25) 2024-05-27 12:57:01 +02:00
test-vm-pv-system.yaml Add/update example configurations. 2023-08-11 12:22:26 +02:00
test-vm-shell.yaml Support cloudInit in CRD. 2024-02-18 11:46:09 +01:00
test-vm-snapshot.yaml Generate test VMs. 2024-11-17 15:08:22 +01:00
test-vm.tpl.yaml Basically working. 2025-01-23 13:41:53 +01:00
test-vm.yaml Add guest agent client and retrieve OS info. 2025-02-10 22:24:10 +01:00

Example setup for development

The CRD must be deployed independently. Apart from that, the kustomize.yaml

  • creates a small cdrom image repository and

  • deploys the operator in namespace vmop-dev with a replica of 0.

This allows you to run the manager in your IDE.

The kustomize.yaml also changes the container image repository for the operator to a private repository for development. You have to adapt this to your own repository if you also want to test your development version in a container.

If you want to run the unittests, this setup must be used with a private container image repository which must match the one configured for gradle pushImages.