Feature Requests

Hi, In km-kube-agent 2.3.0 (the latest version), container resources are hard-coded in the templates. There is no value to override them and no priorityClassName: DaemonSet agent: requests 100m CPU / 256Mi Cluster agent: requests 150m / 384Mi Fleet manager: requests 100m / 128Mi On our production EKS cluster (2 vCPU nodes), 2 of the 8 DaemonSet pods have been Pending since install with "Insufficient cpu". With no priority class, they can't preempt anything either, so those nodes are never monitored. The DaemonSet agent actually uses 2-3m CPU and ~90Mi. Could you expose in values.yaml, with the current values as defaults: resources for each container (DaemonSet agent and its init container, cluster agent, fleet manager) priorityClassName for the DaemonSet, and ideally for the Deployments too Thanks!

Resource orchestration. Take deterministic actions on your resources, based on pre-defined set of rules and approval "workflows".

Harness machine learning to automatically flag telemetry anomalies and presage performance trends before they impact production.

Allow use of SAML authentication via Google, Microsoft, Okta and other SAML/WSFed*

AI based recommendations to speed up error detection and resolution.

An on-premise offering that can be installed on customer or partner infrastructure.

Feature to resend pending invites to users who haven't seen them, or have expired.