Post by Project Sveltos
811 followers
YAML-based filters cover the common case: match by label, match by field value. But real infrastructure has nuance ā conditions that don't reduce to a single equality check. Sveltos supports two scripting languages for evaluation logic wherever conditions need to go beyond simple filters: ššš® and ššš (Common Expression Language). ššš®: š³šš¹š¹ šš°šæš¶š½šš¶š»š“ š³š¼šæ š°š¼šŗš½š¹š²š š°š¼š»š±š¶šš¶š¼š»š An EventSource that fires only when a Service has a LoadBalancer type š®š»š± an external IP assigned. ššš: š°š¼š»š°š¶šš² š²š š½šæš²ššš¶š¼š»š š³š¼šæ šæš²š®š±š®šÆš¹š² š°š¼š»š±š¶šš¶š¼š»š The same Lua evaluation context is used for health checks in š·š¢ššŖš„š¢šµš¦šš¦š¢ššµš©š“ ā assess whether a Deployment is actually healthy by inspecting .š“šµš¢šµš¶š“.š¤š°šÆš„šŖšµšŖš°šÆš“, not just .š“šµš¢šµš¶š“.š³š¦š¢š„šŗšš¦š±ššŖš¤š¢š“. Multiple CEL expressions are ORed by default. CEL is Google's open standard ā the same language used in Kubernetes admission policies (ValidatingAdmissionPolicy) and Argo's expression engine. Both languages run inside the Sveltos evaluation engine. No external webhook, no sidecar, no Lambda function. The logic ships with the resource definition. https://lnkd.in/dzP3RG88 #Kubernetes #MultiCluster #Lua #CEL #PlatformEngineering #PolicyAsCode