Post by Project Sveltos

Sveltos v1.8.0 is out. Three new features, handful number of bug fixes, each targeting a specific operational gap. 1. 𝗚𝗶𝘁𝗢𝗽𝘀-𝗳𝗿𝗶𝗲𝗻𝗱𝗹𝘆 𝗸𝘂𝗯𝗲𝗰𝗼𝗻𝗳𝗶𝗴 𝗿𝗲𝗻𝗲𝘄𝗮𝗹 When Sveltos rotated a cluster's kubeconfig, it wrote a new key (`re-kubeconfig`) and updated `SveltosCluster.spec`. GitOps tools like Flux or ArgoCD saw this as live-state drift from the Git source. The fix is a new field: 𝘴𝘱𝘦𝘤:  𝘵𝘰𝘬𝘦𝘯𝘙𝘦𝘲𝘶𝘦𝘴𝘵𝘙𝘦𝘯𝘦𝘸𝘢𝘭𝘖𝘱𝘵𝘪𝘰𝘯:  𝘬𝘶𝘣𝘦𝘤𝘰𝘯𝘧𝘪𝘨𝘒𝘦𝘺𝘕𝘢𝘮𝘦: 𝘬𝘶𝘣𝘦𝘤𝘰𝘯𝘧𝘪𝘨 # 𝘴𝘢𝘮𝘦 Set 𝘬𝘶𝘣𝘦𝘤𝘰𝘯𝘧𝘪𝘨𝘒𝘦𝘺𝘕𝘢𝘮𝘦 to the existing key name and Sveltos overwrites the Secret in-place, skipping the spec update. Live state and Git stay aligned 2. 𝗦𝗸𝗶𝗽 𝗻𝗮𝗺𝗲𝘀𝗽𝗮𝗰𝗲 𝗰𝗿𝗲𝗮𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝗿𝗲𝘀𝘁𝗿𝗶𝗰𝘁𝗲𝗱 𝗥𝗕𝗔𝗖 In multi-tenant clusters where Sveltos operates without cluster-wide Namespace permissions, the pre-flight namespace check would fail even when the namespace already existed. 𝘚𝘬𝘪𝘱𝘕𝘢𝘮𝘦𝘴𝘱𝘢𝘤𝘦𝘊𝘳𝘦𝘢𝘵𝘪𝘰𝘯: 𝘵𝘳𝘶𝘦 on 𝘗𝘰𝘭𝘪𝘤𝘺𝘙𝘦𝘧s and 𝘒𝘶𝘴𝘵𝘰𝘮𝘪𝘻𝘢𝘵𝘪𝘰𝘯𝘙𝘦𝘧𝘴 bypasses that check and deploys directly into pre-provisioned namespaces. 3. 𝗡𝗮𝘁𝗶𝘃𝗲 𝗛𝗲𝗹𝗺 𝘁𝗲𝘀𝘁 𝗲𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 Helm charts ship with test hooks that authors write precisely to validate a deployment. With 𝘳𝘶𝘯𝘛𝘦𝘴𝘵𝘴: 𝘵𝘳𝘶𝘦 in the chart spec, Sveltos runs those hooks automatically after each successful install or upgrade. Failures surface as deployment failures in ClusterSummary status. 𝗕𝘂𝗴 𝗳𝗶𝘅𝗲𝘀 𝘄𝗼𝗿𝘁𝗵 𝗻𝗼𝘁𝗶𝗻𝗴 Modifying Helm patches no longer goes undetected when chart version and values are unchanged. Sveltos now tracks a hash of the patch set. Failure messages on Helm releases are no longer overwritten before persisting. And manually deleting a ClusterSummary while a cluster is mid-update no longer causes a reconciliation deadlock. Full changelog: https://lnkd.in/d65DAXuA #Kubernetes #MultiCluster #GitOps #PlatformEngineering #Sveltos