Skip to content

RedHatNordicsSA/from-0-to-virt-hero-2024-cph

Repository files navigation

from-0-to-virt-hero-2024-cph

Artifacts for the 2024 Summit Connect CPH Virt demo

Demo environment

Requirement

  • The oc CLI.

Optional

  • The kubevirt CLI. If running from macOS, you will likely need to approve the virtctl binary xattr -dr com.apple.quarantine virtctl.

Steps

  1. Create a Namespace, say webserver
oc new-project webserver

Switch to the newly created Namespace (if not already switched to it).

oc project webserver
  1. Grant privileges to import template data volume You'll likely need to modify the Namespace value in the RoleBinding.
oc create -f clusterrole-dv-clone.yaml
oc create -f rolebinding-dv-clone.yaml
  1. Create resoure to run NGINX as a Pod and VM from Helm You can specify the VM DataSource and template via Values under .vm.
helm template nginx | oc create -f - 

You might need to create the Secret containing PDF files manually if Helm packaging/release process is used and respects .helmignore which exceludes that Secret for size concerns. At this point you should have a working Nginx Pod and VM capable of serving the static files but only accessible via a Service, the Route will be created later. A randomly generated password for the VM was created and can be found in the nginx-vm-cloudinit Secret.

  1. Create Route Get default Ingress domain
oc get ingresses.config/cluster -o jsonpath={.spec.domain}

Edit route.yaml to use this domain in spec.host then

oc create -f route.yaml
  1. Generate some traffic
export APP_URL=$(oc get route -o jsonpath='{.items[0].spec.host}')
for n in {1..100}; do curl -I https://$APP_URL; done

About

Artifacts for the 2024 Summit Connect CPH Virt demo

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages