neonKUBE icon indicating copy to clipboard operation
neonKUBE copied to clipboard

Public NeonKUBE Kubernetes distribution related projects

Results 180 neonKUBE issues
Sort by recently updated
recently updated
newest added

Kubernetes nodes can be labeled with fault domain/availability zone information and its scheduler can then take this into account when scheduling pods. This has been available since Kubernetes v1.2. https://kubernetes.io/docs/setup/best-practices/multiple-zones/...

neon-kube
cluster-setup

It would be nice to be able to automate the selection of specific VM sizes when deploying a cluster. The issue here is that AWS and Azure each have a...

The way we determine cluster status needs some work. It's currently focused on the health of the VMs with a bit of code that checks the Kubernetes API server health....

bug
neon-kube

Virtualization for the Mac: https://tutorials.tinkink.net/en/mac/how-to-use-docker-on-m1-mac.html#colima

investigate

`ClusterProxy.GetHealthAsync()` is currently doing mostly hosting level cluster health checks. We need to enhance this by using the API server's `/livez` and `/readyz` endpoints. https://kubernetes.io/docs/reference/using-api/health-checks/ We're already calling this in...

feature
neon-kube

We currently requires users to log out of all clusters before deploying a new cluster. It would be nice if cluster setup used a separate temporary kubeconfif file so user...

bug
feature
cluster-setup

I'm running **neon-cli** unit tests now to verify the login refactor. The `neon cluster check` command is reporting several deployments with **priorityClass=3000**: ``` --> neon-monitor/tempo-compactor (Deployment) - user-medium (3,000) -->...

bug
cluster-setup

Client tools like **neon-cli** provide commands like **delete** to manage deployed clusters. These require knowledge of the currently deployed cluster nodes as well as hosting credentials for cloud and remote...

All headend services need to be defined in neonKUBE such that we call call this with the generated `HeadendClient` class as opposed to manually wiring up `JsonClient` calls. We want...

debt

We've just realized that redeploying the **headend** cluster after it's been deleted (accidentally by me while testing neon-desktop uninstall) is non-trivial. I wonder if we can implement a deployment mode...

investigate
feature
cluster-setup