Max!
I was using quay.io/kubevirt/virt-operator:v1.0.0 at the time. I have not retested on 1.2 but I can try that this weekend 👍
+1 on this, would be nice to be able to configure SSE-C encryption this way
found this project that might be helpful : https://github.com/philipl/evdevremapkeys It's for Linux, but its bash + python and their methodology of monitoring a /dev/ input should work on macos as...
Python notebooks in a markdown browser in the terminal is 100% the future i want to be living in :pleading_face:
Ran into same issue, IIRC changing/deleting the line ``` nginx.ingress.kubernetes.io/backend-protocol: GRPC ``` Got it working for me
Agreed re: very over-engineered. You don't need virtually any of it to just expose the UI via ingress, but I also don't know what the full extent of the contributors...
just tested this minimal version and verified it worked for the UI, youd need to use port 8333 for the s3 endpoint: ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: labels: app.kubernetes.io/component:...
Oh cool, either have no password, or hard code my password in git - very safe normal and secure
Edit: I cannot say with any confidence if this will help others in this thread but here is how I was able to get my OIDC logins working: ## Context...
this would be a very cool feature!