neonKUBE
neonKUBE copied to clipboard
Incorrect priority classes for several deployments?
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)
--> neon-monitor/tempo-distributor (Deployment) - user-medium (3,000)
--> neon-monitor/tempo-querier (Deployment) - user-medium (3,000)
--> neon-monitor/tempo-query-frontend (Deployment) - user-medium (3,000)
--> neon-storage/openebs-jiva-operator-operator (Deployment) - user-medium (3,000)
--> neon-storage/openebs-nfs-provisioner (Deployment) - user-medium (3,000)
--> neon-system/neon-system-db-pooler (Deployment) - user-medium (3,000)
These should be 900,000,000 or greater, right?