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

Post contentPost content