Volume 343, Issue 3 · 6 articles from 3 issues
SUSE examines how vendor lock-in builds up through hard-to-reverse platform decisions and how open source keeps options open.
The post argues that vendor lock-in usually starts as a reasonable decision made under pressure, such as adopting a managed service that ships faster.
The real risk is not relying on vendors but accumulating dependencies that become too expensive to unwind, built up across APIs, contracts, data models, identity patterns, observability pipelines and operational tooling.
SUSE frames reversibility as the key to a platform team's ability to pivot.
SUSE explores how agentic AI can help manage multi-cluster Kubernetes if teams draw clear lines between observing, recommending and acting.
SUSE says AI is pushing deployment, scaling and governance responsibilities onto platform teams as clusters and environments multiply, and agentic software that can observe, reason and act within predefined limits could ease that operational load.
The value depends on the context an agent can see, such as cluster state, policy and access rules, and the boundaries it operates within.
The post urges clear separation between what the system observes, recommends and changes.
SUSE shows how agentic SecOps on SUSE AI Factory can triage container CVEs, build fixes and open reviewable pull requests.
SUSE notes that scanning a mid-sized container estate can return thousands of findings, of which only a few dozen matter.
Triaging each means checking SBOMs, inherited base layers, what runs in production and vendor errata, and the post argues chatbots have not dented this backlog.
It describes an agent running on SUSE AI Factory with the NVIDIA Open Agent Safety Platform that reads findings, decides relevance, makes and verifies fixes, and hands engineers a pull request.
SUSE explains how infrastructure controls, NVIDIA OpenShell sandboxing and egress proxies kept its autonomous SecOps agents in check.
SUSE argues that prompt and model safeguards only guide agent behavior, while infrastructure controls limit what agents can actually access and do.
Using SUSE AI Factory with NVIDIA and the NVIDIA Open Agent Safety Platform, NVIDIA OpenShell isolates agent execution in sandboxes, where SecOps agents investigate container vulnerabilities, prepare fixes and submit pull requests while humans keep approval authority.
SUSE reports that all agent egress went through out-of-process proxies, with zero direct git merges or Kubernetes API calls.
SUSE shows how Kube-OVN in SUSE Virtualization delivers tenant isolation and VM microsegmentation via Kubernetes CRDs.
As enterprises consolidate VM workloads onto SUSE Virtualization clusters, SUSE argues they need both tenant isolation and microsegmentation, since each alone leaves gaps.
SUSE Virtualization uses Kube-OVN to deliver both natively through Kubernetes CRDs: Vpc and Subnet resources for isolation, and NetworkPolicy plus Kube-OVN SubnetACL for microsegmentation.
Each tenant gets its own routing domain on shared infrastructure, while microsegmentation prevents a compromised VM from becoming a foothold.
SUSE adds zero-trust agent security via NVIDIA OpenShell and SLES for NVIDIA to SUSE AI Factory with NVIDIA.
SUSE introduced new capabilities to help enterprises adopt private enterprise AI while keeping operational control, security and governance over their systems.
The latest release of SUSE AI Factory with NVIDIA adds zero-trust agent security through the NVIDIA OpenShell Reference Architecture, alongside SUSE Linux Enterprise Server for NVIDIA.
SUSE says the solution is designed to support next-generation NVIDIA silicon immediately.
It provides a unified foundation for developers building AI applications and agents, platform teams deploying them and IT governing them across any footprint.