Jeff Lill

I'm starting to believe that Harbor may be an overkill for most neon-kube clusters and probably certainly for neon-desktop clusters.  We might be able to save another 250-300 MiB...

XenServer does support suspending VMs but we disabled that a few months ago because shutting down a Kubernetes cluster wasn't really working. Now that shutdown seems to be working much...

The basic idea here is to allow Kubernetes manifests to reference variables and secrets using the `PreprocessReader` in **Neon.Common**. Then we can have **neon-cli** define some standard **NEON_*** variables like...

I've just seen a few problems deploying a built-in cluster that seem to be related to remnants of previous cluster an potentially an invalid kubeconfig file. I did a pass...

We just saw a problem where our headend nuget repo's SSL certificate wasn't being renewed by **cert-manager**. Marcus looked into this and cert-manager appeared to be somewhat locked up and...

We're currently leaving partially deployed clusters running. This is especially bad for cloud deployments because the user will probably think that the cluster hasn't been deployed but the cloud will...

Azure has the concept of capacity reservations for VMs. I believe this would allow us to request in advance to reserve the all of the VM sizes needed to deploy...

@marcusbooyah: Doesn't know why this is happening. Perhaps we need to upgrade Harbor or perhaps handling #1613 will help.

Currently Harbor is being configured with just a public registry/library. We don't really want this to be default. Let's do this instead: - [ ] Create a private **neon** library...

- [ ] V1NeonClusterOperator resource - [ ] CA update schedule: CRON format? - [ ] Security patch schedule: CRON format? - [ ] Status where the operator can persist...