# control-plane

A control plane is the administrative component or set of operations used to create, manage, and govern computing resources, distinct from the data plane that provides the resources' primary runtime capabilities.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Provable Authority: A Protocol for Verifiable Authority Resolution and Control Across Human, Organizational, and Agentic Transactions

DevFeed: [Provable Authority: A Protocol for Verifiable Authority Resolution and Control Across Human, Organizational, and Agentic Transactions](<https://devfeed.tech/articles/provable-authority-a-protocol-for-verifiable-authority-resolution-and-control-across-human-organizational-and-agentic-transactions-146009.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.22899>)

Author: Jeremy Blackburn, Tim Hines, Matthew Koepp, Russell Lessard, Jason Patrick

Published: 2026-11-20T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [ach](<https://devfeed.tech/tags/ach.md>), [adapter](<https://devfeed.tech/tags/adapter.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-runtime](<https://devfeed.tech/tags/agent-runtime.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-commerce](<https://devfeed.tech/tags/agentic-commerce.md>), [agentic-transactions](<https://devfeed.tech/tags/agentic-transactions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [assertions](<https://devfeed.tech/tags/assertions.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [bounded](<https://devfeed.tech/tags/bounded.md>), [budget](<https://devfeed.tech/tags/budget.md>), [canonical](<https://devfeed.tech/tags/canonical.md>), [control](<https://devfeed.tech/tags/control.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-ma](<https://devfeed.tech/tags/cs-ma.md>), [organizational](<https://devfeed.tech/tags/organizational.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

### AI overview

The ChainIT Authority Protocol proposes a pre-execution control plane to let relying parties verify that a person, organization, or AI agent is authorized for the exact transaction being submitted. It keeps identity, versioned organizational authority, evidence, policy checks, and configured dispositions distinct; binds decisions and human approvals to a canonical transaction digest; reserves capacity atomically; and gates commit on a single-use, sender-constrained credential consumed at the rail adapter. For AI agents, an Agent Subject Profile adds workload registration, attested keys, and a sovereignty boundary. The abstract says it specifies bounded-freshness status rules and enforcement profiles for fiat and stablecoin rails, while also identifying residual risks and non-goals.

### Source excerpt

arXiv:2610.22899v2 Announce Type: replace Abstract: Payment systems authenticate users, devices, accounts, and cryptographic credentials, but a relying party, such as a counterparty, payment rail, marketplace, or autonomous agent runtime, generally cannot obtain compact, independently verifiable evidence that the party presenting one exact transaction holds current organizational authority to execute it under the applicable evidence, policy, budget, and approval state. Agentic commerce makes this gap operationally urgent: a software agent can produce a valid signature while acting outside its delegated purpose, after its sponsor's authority has changed, or on transaction details that differ from those a human approved. We describe the ChainIT Authority Protocol, a subject-neutral and rail-neutral pre-execution authority and evidence control plane. The protocol separates durable identity, a versioned organizational authority record (the Authority Resolution Pactvera), sourced evidence assertions, deterministic reason-coded policy predicates, and organization-configured dispositions; binds each decision and human approval to a canonical transaction digest; reserves capacity atomically so that limits hold under concurrency; and authorizes commit only through a single-use, sender-constrained Execution Authorization Credential consumed at the rail adapter, with append-only lifecycle evidence sealed after the terminal outcome. An Agent Subject Profile adds the workload registration, attested key hierarchy, and sovereignty boundary required when the acting subject is an AI agent, without introducing a separate authority concept. We specify the commit-time execution predicate and bounded-freshness status rules, give enforcement profiles for fiat (ACH, wire, card, instant payment) and stablecoin rails, and state residual risks and non-goals.

## ChainIT Transaction Truth: Stablecoins, Web3 Wallets, and Multi-Rail Commerce. A Zero-Trust Control Plane for Verified Identity, Organizational Authority, Runtime Compliance, Secure Wallet Execution, and Immutable Settlement Evidence

DevFeed: [ChainIT Transaction Truth: Stablecoins, Web3 Wallets, and Multi-Rail Commerce. A Zero-Trust Control Plane for Verified Identity, Organizational Authority, Runtime Compliance, Secure Wallet Execution, and Immutable Settlement Evidence](<https://devfeed.tech/articles/chainit-transaction-truth-stablecoins-web3-wallets-and-multi-rail-commerce-a-zero-trust-control-plane-for-verified-identity-organizational-authority-runtime-compliance-se-143160.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.24659>)

Author: Eric Tacl, Matthew Koepp, Tim Hines, Russell Lessard, Jason Patrick, Jeremy Blackburn

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [audit trail](<https://devfeed.tech/topics/audit-trail.md>)

Tags: [compliance](<https://devfeed.tech/tags/compliance.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [execution](<https://devfeed.tech/tags/execution.md>), [identity](<https://devfeed.tech/tags/identity.md>), [organizational](<https://devfeed.tech/tags/organizational.md>), [q-fin-gn](<https://devfeed.tech/tags/q-fin-gn.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [settlement](<https://devfeed.tech/tags/settlement.md>), [stablecoins](<https://devfeed.tech/tags/stablecoins.md>), [transaction](<https://devfeed.tech/tags/transaction.md>), [trust](<https://devfeed.tech/tags/trust.md>), [web3](<https://devfeed.tech/tags/web3.md>), [zero-trust](<https://devfeed.tech/tags/zero-trust.md>)

### AI overview

The ChainIT Transaction Truth Architecture treats a valid blockchain transaction and a wallet signature as insufficient proof of a complete commercial transaction. It places verified individual and organizational identity, current authority records and policy, transaction-specific runtime compliance, approval of the exact transaction digest, atomic capacity reservation, and a single-use Execution Authorization Credential before wallet execution. Afterward, it records settlement, reconciliation, and lifecycle evidence. The design distinguishes key control from identity, identity from organizational authority, authority from compliance, compliance from execution authority, and network confirmation from commercial settlement. It describes wallet and custody profiles, including MPC custody kept independent of business authority, layered finality, stablecoin and Web3 evidence domains, and a phased deployment whose pilots must preserve control invariants under attack and failure. The supplied material is an abstract and does not provide implementation details.

### Source excerpt

arXiv:2611.24659v1 Announce Type: new Abstract: Stablecoins can move value continuously across programmable networks, and Web3 wallets can authorize those transfers with cryptographic signatures, but neither capability, standing alone, establishes a complete commercial transaction. A blockchain may prove that a transaction satisfied protocol rules, and a wallet may prove that sufficient signing authority existed; neither proves who initiated the transaction, for which legal entity, under what current authority, against which current compliance evidence, on what exact instruction, or with what settlement and accounting outcome. We describe the ChainIT Transaction Truth Architecture, a zero-trust control, execution, and evidence architecture that places verified individual and organizational identity, the organizational authority record and authority policy of the ChainIT Authority Protocol, transaction-specific runtime compliance decisions, exact-digest approval, atomic capacity reservation, and a single-use Execution Authorization Credential in front of wallet execution, and that records settlement, reconciliation, and lifecycle evidence after the transaction. The architecture separates five boundaries: control of a key is not identity, identity is not organizational authority, authority is not compliance, compliance is not execution authority, and network confirmation is not complete commercial settlement. We describe wallet and custody profiles, including a multi-party computation (MPC) profile in which custody security is kept independent of business authority, stablecoin and Web3 evidence domains, layered finality, the U.S. stablecoin regulatory context as of September 2026, and a phased deployment in which pilot success requires that the control invariants hold under attack and failure.

## Who Changed the AI Agent's Rules? Measuring How AI Coding Agents Escalate Authority in CI/CD Pipelines

DevFeed: [Who Changed the AI Agent's Rules? Measuring How AI Coding Agents Escalate Authority in CI/CD Pipelines](<https://devfeed.tech/articles/who-changed-the-ai-agent-s-rules-measuring-how-ai-coding-agents-escalate-authority-in-ci-cd-pipelines-142128.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23251>)

Author: Miroslaw Staron

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>)

Tags: [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [framework](<https://devfeed.tech/tags/framework.md>), [governance](<https://devfeed.tech/tags/governance.md>), [model](<https://devfeed.tech/tags/model.md>), [risk](<https://devfeed.tech/tags/risk.md>)

### AI overview

The study evaluates a joint penalty model combining execution cost and governance risk across 932,791 agent-authored pull requests from five coding agents. Control-plane changes had a higher mean joint penalty than data-plane changes (0.498 vs. 0.218) and higher mean governance risk (0.530 vs. 0.135); all 775 extreme-risk pull requests modified the control plane. Policy-violation flags appeared in 46.6% of control-plane pull requests and 63.6% of merged ones. Mean joint penalty varied by agent, from 0.166 for Cursor to 0.328 for Copilot, with differences not explained by execution cost or merge rate. Manual review of 34 pull requests gave the authority-scope classifier a Cohen's kappa of 0.72. These findings suggest the metric can support risk detection and agent-specific authority tuning, though the supplied text describes an abstract rather than the full study.

### Source excerpt

arXiv:2611.23251v1 Announce Type: new Abstract: AI coding agents can modify CI/CD control-plane structures, including workflows and permission settings, thereby extending their authority beyond routine code changes. Because such modifications can affect an entire development pipeline, this study examines the trade-off between execution cost and governance risk in agentic CI/CD. We introduce a joint penalty model, P(M), that combines these two dimensions and evaluate it on all 932,791 agent-authored pull requests in the AIDev dataset, covering five autonomous coding agents. Each pull request is automatically classified by authority scope - data-plane or control-plane - and assigned a penalty score. We found that control-plane actions have a 2.3x higher mean joint penalty than data-plane actions (0.498 vs. 0.218) and a 3.9x higher mean governance risk (0.530 vs. 0.135), which means that they indeed increase the risk. All 775 pull requests in the extreme-risk category, defined as P(M) > 0.8, modify the control plane. Policy-violation flags occur in 46.6% of all control-plane pull requests and in 63.6% of merged control-plane pull requests. We have also found an indication that governance risk differs substantially across agent implementations, ranging from 0.166 for Cursor to 0.328 for Copilot in mean joint penalty. These differences are not explained by execution cost or merge rate, suggesting that authority policies should be calibrated for individual agents. Manual assessment of 34 pull requests yielded a Cohen's kappa of 0.72 for the authority-scope classifier. The results show that a single compound metric can identify and measure changes to CI/CD governance structures at scale. The proposed framework supports detecting high-risk pull requests and comparing governance behavior across agent implementations, providing a basis for authority tuning and pipeline governance in agentic software development.

## Meet Superplane: HackerNoon Company of the Week

DevFeed: [Meet Superplane: HackerNoon Company of the Week](<https://devfeed.tech/articles/meet-superplane-hackernoon-company-of-the-week-140890.md>)

Original publisher: [Read original article](<https://hackernoon.com/meet-superplane-hackernoon-company-of-the-week?source=rss>)

Author: Company of the Week

Published: 2026-11-18T16:46:02Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [ai-orchestration](<https://devfeed.tech/tags/ai-orchestration.md>), [ai-orchestration-platform](<https://devfeed.tech/tags/ai-orchestration-platform.md>), [ai-software-factory](<https://devfeed.tech/tags/ai-software-factory.md>), [automate](<https://devfeed.tech/tags/automate.md>), [company](<https://devfeed.tech/tags/company.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [devops](<https://devfeed.tech/tags/devops.md>), [hackernoon](<https://devfeed.tech/tags/hackernoon.md>), [hackernoon-company-of-the-week](<https://devfeed.tech/tags/hackernoon-company-of-the-week.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-source-ai](<https://devfeed.tech/tags/open-source-ai.md>), [open-source-ai-orchestration](<https://devfeed.tech/tags/open-source-ai-orchestration.md>), [superplane](<https://devfeed.tech/tags/superplane.md>), [tasks](<https://devfeed.tech/tags/tasks.md>), [tech-companies](<https://devfeed.tech/tags/tech-companies.md>), [tech-company-database](<https://devfeed.tech/tags/tech-company-database.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

SuperPlane is an open-source orchestration platform that coordinates AI agents to take selected software tasks from backlog through planning, coding, testing, and review, aiming to produce verified, review-ready pull requests. It analyzes a team's codebase and backlog, applies consistent rules and quality checks, and prompts agents to retry when issues arise; engineers are brought in when human judgment is needed. It integrates with existing development tools, supports teams' choice of AI models, and can be deployed in the cloud or on-premises. The company reports autonomous handling of 30% of backlog issues, 70% less engineer involvement in routine tasks, and a fourfold faster path from issue to reviewed pull request. These are company-reported figures.

### Source excerpt

Superplane is an open-source AI software factory and DevOps control plane designed to automate routine engineering and workflow tasks.

## LinkedIn Cuts Daily Spark Shuffle Fetch Failures from 750 to 20 with Apache Celeborn

DevFeed: [LinkedIn Cuts Daily Spark Shuffle Fetch Failures from 750 to 20 with Apache Celeborn](<https://devfeed.tech/articles/linkedin-cuts-daily-spark-shuffle-fetch-failures-from-750-to-20-with-apache-celeborn-140877.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/linkedin-celeborn-remote-shuffle/>)

Author: Leela Kumili

Published: 2026-11-18T15:05:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Apache Spark](<https://devfeed.tech/topics/spark.md>), [Apache Flink](<https://devfeed.tech/topics/apache-flink.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [algorithms](<https://devfeed.tech/tags/algorithms.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-flink](<https://devfeed.tech/tags/apache-flink.md>), [apache-spark](<https://devfeed.tech/tags/apache-spark.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [big-data](<https://devfeed.tech/tags/big-data.md>), [big-data-infrastructure](<https://devfeed.tech/tags/big-data-infrastructure.md>), [cloud-architecture](<https://devfeed.tech/tags/cloud-architecture.md>), [compression](<https://devfeed.tech/tags/compression.md>), [compute](<https://devfeed.tech/tags/compute.md>), [compute-costs](<https://devfeed.tech/tags/compute-costs.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [data-platform](<https://devfeed.tech/tags/data-platform.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [fault-tolerance](<https://devfeed.tech/tags/fault-tolerance.md>), [flink](<https://devfeed.tech/tags/flink.md>), [linkedin](<https://devfeed.tech/tags/linkedin.md>), [linkedin-celeborn-remote-shuffle](<https://devfeed.tech/tags/linkedin-celeborn-remote-shuffle.md>), [news](<https://devfeed.tech/tags/news.md>), [optimizations](<https://devfeed.tech/tags/optimizations.md>), [performance-tuning](<https://devfeed.tech/tags/performance-tuning.md>), [platform](<https://devfeed.tech/tags/platform.md>), [remote](<https://devfeed.tech/tags/remote.md>), [replication](<https://devfeed.tech/tags/replication.md>), [runtimes](<https://devfeed.tech/tags/runtimes.md>), [spark](<https://devfeed.tech/tags/spark.md>), [storage](<https://devfeed.tech/tags/storage.md>)

### AI overview

LinkedIn deployed Apache Celeborn as a shared remote shuffle service for most Spark and Flink workloads, separating shuffle storage from compute. Map tasks push intermediate data to dedicated workers, and reducers fetch it directly; this reduces contention and dependence on executor lifecycles. Compared with its previous Magnet implementation, LinkedIn reports daily shuffle fetch failures falling from about 750 to 20, compute costs down 10%, and application runtimes improved 14%. Reliability work included a five-node Raft control plane across availability zones, network-aware replication, and health-based worker exclusion; task failures during infrastructure disruptions fell 20-fold. LinkedIn also reports 40% shorter shuffle duration after moving storage to NVMe, a 35% smaller shuffle-worker fleet with Zstandard instead of LZ4, and nearly 90% lower shuffle cost per task. The deployment required substantial engineering beyond the upstream project.

### Source excerpt

LinkedIn deployed Apache Celeborn as a shared remote shuffle platform across most Spark and Flink workloads, reducing daily shuffle fetch failures from approximately 750 to 20. The deployment also lowered compute costs by 10%, improved application runtimes by 14%, and reduced shuffle costs per task by nearly 90% through dedicated storage, replication, and data-plane optimizations. By Leela Kumili

## Optimizing Kubernetes admission control: Where Kyverno's CEL admission cost actually goes

DevFeed: [Optimizing Kubernetes admission control: Where Kyverno's CEL admission cost actually goes](<https://devfeed.tech/articles/optimizing-kubernetes-admission-control-where-kyverno-s-cel-admission-cost-actually-goes-142441.md>)

Original publisher: [Read original article](<https://www.cncf.io/blog/2026/11/18/optimizing-kubernetes-admission-control-where-kyvernos-cel-admission-cost-actually-goes/>)

Author: Raunak Madan (Software Engineer Intern, Nirmata)

Published: 2026-11-18T12:30:00Z

Content type: article

Language: en

Sources: [Cloud Native Computing Foundation](<https://devfeed.tech/sources/cloud-native-computing-foundation.md>)

Topics: [Kyverno](<https://devfeed.tech/topics/kyverno.md>), [rule-engine](<https://devfeed.tech/topics/rule-engine.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [admission](<https://devfeed.tech/tags/admission.md>), [blog](<https://devfeed.tech/tags/blog.md>), [cel](<https://devfeed.tech/tags/cel.md>), [cost](<https://devfeed.tech/tags/cost.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kyverno](<https://devfeed.tech/tags/kyverno.md>)

### AI overview

Profiling found that ValidatingPolicy's CEL path spent 86.8% of its allocations converting the admitted object, because it repeated the conversion for every matched policy. Kyverno 1.19.2 moves that conversion to once per request while preserving each engine's existing request.object behavior; the MutatingPolicy engine's 64-policy benchmark fell from 258,943 to 52,689 allocations and 10.59 ms to 2.97 ms. Image verification received the same memory-saving change. In a 16-policy comparison measured on an earlier Kyverno version, Kyverno was slower than native ValidatingAdmissionPolicy with one policy but faster with 16; the comparison has not been rerun after the fix. Benchmarks isolate the engine on one machine and omit webhook network and etcd costs. Remaining work includes the per-request JSON round-trip, mutating-policy object threading, and unaddressed single-replica tail latency.

### Source excerpt

Kyverno's CEL (Common Expression Language)-based engines exist to evaluate policy expressions. So when we profiled the admission path, we expected to find the bulk of the cost in CEL evaluation. It was not there. About 86%...

## Compliance Memory: Keep Rule-to-Control Links When Staff Leave

DevFeed: [Compliance Memory: Keep Rule-to-Control Links When Staff Leave](<https://devfeed.tech/articles/compliance-memory-keep-rule-to-control-links-when-staff-leave-141052.md>)

Original publisher: [Read original article](<https://www.lyzr.ai/blog/compliance-memory-in-banks/>)

Author: Lyzr Team

Published: 2026-11-18T11:45:51Z

Content type: article

Language: en

Sources: [Lyzr.ai](<https://devfeed.tech/sources/lyzr-ai.md>)

Topics: [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [audit](<https://devfeed.tech/topics/audit.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [bank](<https://devfeed.tech/tags/bank.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [control](<https://devfeed.tech/tags/control.md>), [controls](<https://devfeed.tech/tags/controls.md>), [leave](<https://devfeed.tech/tags/leave.md>), [links](<https://devfeed.tech/tags/links.md>), [memory](<https://devfeed.tech/tags/memory.md>), [policies](<https://devfeed.tech/tags/policies.md>), [rules](<https://devfeed.tech/tags/rules.md>)

### AI overview

"Compliance memory" is the article's nonstandard term for preserving links among bank rules, policies, controls, evidence, and the reasons for those links so staff turnover does not erase institutional knowledge. It recommends recording rationale and signed approvals before departures, assigning ownership to persistent roles with fallbacks, and using agents to propose and re-check mappings, flag stale evidence or gaps, and route work for human approval. Agents cannot recover undocumented reasons and should not present guesses as fact or remediate automatically. Madison is described as storing this record for US banks and credit unions; the excerpt says an HR offboarding integration is unconfirmed and long-term tamper-resistant retention depends on the customer's environment. Opencontroller is described as a separate runtime control layer. The term and product claims are presented by a vendor, and cited regulatory expectations were not verified against primary sources.

### Source excerpt

Compliance memory is our shorthand for a record that keeps the links between a bank's rules, policies and controls, and the reasons behind them, so...

## wasmCloud 2.12.2: Host directories for plugins, and scanners that gate merges

DevFeed: [wasmCloud 2.12.2: Host directories for plugins, and scanners that gate merges](<https://devfeed.tech/articles/wasmcloud-2-12-2-host-directories-for-plugins-and-scanners-that-gate-merges-144206.md>)

Original publisher: [Read original article](<https://wasmcloud.com/blog/wasmcloud-2-12-2-release/>)

Author: Eric Gregory

Published: 2026-11-18T00:00:00Z

Content type: release

Language: en

Sources: [wasmCloud](<https://devfeed.tech/sources/wasmcloud-blog.md>)

Topics: [wasmCloud](<https://devfeed.tech/topics/wasmcloud.md>), [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [qualitygates](<https://devfeed.tech/topics/qualitygates.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [codeql](<https://devfeed.tech/tags/codeql.md>), [directories](<https://devfeed.tech/tags/directories.md>), [gate](<https://devfeed.tech/tags/gate.md>), [host-memory](<https://devfeed.tech/tags/host-memory.md>), [memory](<https://devfeed.tech/tags/memory.md>), [merge](<https://devfeed.tech/tags/merge.md>), [plugins](<https://devfeed.tech/tags/plugins.md>), [scanners](<https://devfeed.tech/tags/scanners.md>), [tables](<https://devfeed.tech/tags/tables.md>), [wasmcloud](<https://devfeed.tech/tags/wasmcloud.md>)

### AI overview

wasmCloud 2.12.2 adds host-directory mounts for component plugins, faster placement when hosts become ready, and page-table accounting in the host memory guard. Plugin filesystems remain opt-in: only hostPath volumes are supported, paths are validated, host reserved paths stay protected, and workload hostPath mounts cannot expose plugin directories. The release also makes OSV-Scanner lockfile findings and selected CodeQL alerts merge-blocking, with written malicious-dependency and remediation policies. Linux memory readings will be higher because VmPTE and, on 4.x kernels, VmPMD are counted; hosts unable to detect capacity now fail closed unless given an explicit limit or `off`. Before upgrading, apply the updated CRDs and check mount paths and hosts near memory thresholds. The excerpt also reports opt-in mimalloc/jemalloc throughput gains with modest per-workload memory increases, and digest-based caching for components lacking a digest.

### Source excerpt

wasmCloud 2.12.2 lets a host component plugin mount directories from the host, puts OSV-Scanner and CodeQL in front of every merge, counts page tables in the host memory guard, and places a waiting workload the moment a host turns ready.

## Dell puts a single gateway between enterprise AI agents and the data they crave

DevFeed: [Dell puts a single gateway between enterprise AI agents and the data they crave](<https://devfeed.tech/articles/dell-puts-a-single-gateway-between-enterprise-ai-agents-and-the-data-they-crave-138448.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/17/data-intelligence-lifts-enterprise-ai-factory-accuracy-dellatsc26/>)

Author: Ryan Stevens

Published: 2026-11-17T18:19:45Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [AI-Ready Data](<https://devfeed.tech/topics/ai-ready-data.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [dell](<https://devfeed.tech/topics/dell.md>)

Tags: [accelerated-computing](<https://devfeed.tech/tags/accelerated-computing.md>), [adam-glick](<https://devfeed.tech/tags/adam-glick.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-data-centers](<https://devfeed.tech/tags/ai-data-centers.md>), [ai-data-platform](<https://devfeed.tech/tags/ai-data-platform.md>), [ai-factory](<https://devfeed.tech/tags/ai-factory.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-supercomputers](<https://devfeed.tech/tags/ai-supercomputers.md>), [alison-biers](<https://devfeed.tech/tags/alison-biers.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [context](<https://devfeed.tech/tags/context.md>), [cube-event-coverage](<https://devfeed.tech/tags/cube-event-coverage.md>), [data](<https://devfeed.tech/tags/data.md>), [data-intelligence](<https://devfeed.tech/tags/data-intelligence.md>), [dell](<https://devfeed.tech/tags/dell.md>), [dell-ai-factory](<https://devfeed.tech/tags/dell-ai-factory.md>), [dell-fabric-manager](<https://devfeed.tech/tags/dell-fabric-manager.md>), [dell-openmanage-rack-scale](<https://devfeed.tech/tags/dell-openmanage-rack-scale.md>), [dell-powerrack](<https://devfeed.tech/tags/dell-powerrack.md>), [dell-technologies](<https://devfeed.tech/tags/dell-technologies.md>), [dell-technologies-inc](<https://devfeed.tech/tags/dell-technologies-inc.md>), [dellatsc26](<https://devfeed.tech/tags/dellatsc26.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [governed-context](<https://devfeed.tech/tags/governed-context.md>), [gpus](<https://devfeed.tech/tags/gpus.md>), [high-performance-computing](<https://devfeed.tech/tags/high-performance-computing.md>), [high-performance-storage](<https://devfeed.tech/tags/high-performance-storage.md>), [high-speed-networking](<https://devfeed.tech/tags/high-speed-networking.md>), [hpc](<https://devfeed.tech/tags/hpc.md>), [hpc-infrastructure](<https://devfeed.tech/tags/hpc-infrastructure.md>), [john-furrier](<https://devfeed.tech/tags/john-furrier.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [neocloud](<https://devfeed.tech/tags/neocloud.md>), [news](<https://devfeed.tech/tags/news.md>), [sc26](<https://devfeed.tech/tags/sc26.md>), [sc26-2026](<https://devfeed.tech/tags/sc26-2026.md>), [sc26eventpage](<https://devfeed.tech/tags/sc26eventpage.md>), [srinath-alapati](<https://devfeed.tech/tags/srinath-alapati.md>), [supercomputing](<https://devfeed.tech/tags/supercomputing.md>), [thecube](<https://devfeed.tech/tags/thecube.md>)

### AI overview

Dell's Agentic Data Gateway is designed as a single control point between enterprise AI agents and company data. Backed by a Model Context Protocol server, it works with Dell's data intelligence features for lineage and provenance, while hybrid workflows send metadata so data can remain at the edge, in the cloud or in the data center. Dell says this avoids the expense and ongoing effort of consolidating data, while storage intelligence tracks what data exists, who owns it and its size. The excerpt also describes OpenManage Rack Scale management across compute, networking, power and cooling, plus validated designs built with Nvidia and other partners. Dell product leaders report accuracy rising from roughly 60% to 94% with the right context and claim PowerRack deployment can reach production in six hours; these are attributed company claims.

### Source excerpt

Data intelligence is becoming the deciding layer of the enterprise AI factory as companies learn that racks of GPUs deliver little value when agents lack trusted, governed context. Neocloud providers built the first wave of large-scale AI systems, and core enterprise customers now want the same capabilities inside their own organizations. Dell Technologies Inc. recently [...] The post Dell puts a single gateway between enterprise AI agents and the data they crave appeared first on SiliconANGLE.

## Netmap caching: keeping Tailscale up on iffy connections

DevFeed: [Netmap caching: keeping Tailscale up on iffy connections](<https://devfeed.tech/articles/netmap-caching-keeping-tailscale-up-on-iffy-connections-139735.md>)

Original publisher: [Read original article](<https://tailscale.com/blog/netmap-caching>)

Author: Claus Lensbøl

Published: 2026-11-17T16:45:00Z

Content type: article

Language: en

Sources: [Tailscale](<https://devfeed.tech/sources/blog-on-tailscale.md>)

Topics: [tailscale](<https://devfeed.tech/topics/tailscale.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [app startup](<https://devfeed.tech/topics/app-startup.md>), [cache-invalidation](<https://devfeed.tech/topics/cache-invalidation.md>)

Tags: [caching](<https://devfeed.tech/tags/caching.md>), [startup](<https://devfeed.tech/tags/startup.md>), [tailnet](<https://devfeed.tech/tags/tailnet.md>), [tailscale](<https://devfeed.tech/tags/tailscale.md>)

### AI overview

Netmap caching lets Tailscale start from a locally saved copy of a node's network map, speeding startup and enabling connections to some tailnet nodes when the coordination server is unavailable. The cache includes node settings and permitted peer information, such as endpoints and home DERP region; the client writes only changed data to limit disk writes. Cached data can support encrypted connections relayed over DERP. Clients can also exchange their short-lived DISCO public keys through that encrypted tunnel, allowing direct connections to be negotiated without the coordination server. Availability degrades as endpoints, membership, policies, or other map data change without updates. The feature is opt-in via tailnet policy during early testing, and is not yet available on Android or iOS.

### Source excerpt

Tailscale can now start from a saved copy of your tailnet map, speeding everybody's startup times and mitigating some rough connections.

## You've decided to repatriate cloud workloads. Now what?

DevFeed: [You've decided to repatriate cloud workloads. Now what?](<https://devfeed.tech/articles/you-ve-decided-to-repatriate-cloud-workloads-now-what-137074.md>)

Original publisher: [Read original article](<https://www.networkworld.com/article/4247951/youve-decided-to-repatriate-cloud-workloads-now-what.html>)

Author: Zeus Kerravala

Published: 2026-11-17T10:00:00Z

Content type: article

Language: en

Sources: [Network World](<https://devfeed.tech/sources/network-world.md>)

Topics: [cloud-migration](<https://devfeed.tech/topics/cloud-migration.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>), [cloud security](<https://devfeed.tech/topics/cloud-security.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [applications](<https://devfeed.tech/tags/applications.md>), [budget](<https://devfeed.tech/tags/budget.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [cloud-computing-data-center-private-cloud](<https://devfeed.tech/tags/cloud-computing-data-center-private-cloud.md>), [cloud-spending](<https://devfeed.tech/tags/cloud-spending.md>), [cloud-workloads](<https://devfeed.tech/tags/cloud-workloads.md>), [colocation](<https://devfeed.tech/tags/colocation.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [control](<https://devfeed.tech/tags/control.md>), [cost](<https://devfeed.tech/tags/cost.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [data-ownership](<https://devfeed.tech/tags/data-ownership.md>), [data-sovereignty](<https://devfeed.tech/tags/data-sovereignty.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-it](<https://devfeed.tech/tags/enterprise-it.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [it](<https://devfeed.tech/tags/it.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [private-cloud](<https://devfeed.tech/tags/private-cloud.md>), [storytype-feature](<https://devfeed.tech/tags/storytype-feature.md>)

### AI overview

Foundry's 2026 survey of 527 IT decision makers reports that 66% of organizations have moved or plan to move workloads from public cloud to on-premises or colocation, while 69% expect cloud spending to rise. Respondents cite security (60%), cost control and performance/reliability (42% each), and data sovereignty/privacy (40%) as reasons. Storage, databases, and web apps are common early moves; AI is also shifting toward hybrid and private infrastructure, though bursty training may remain in cloud. Repatriation brings capacity and power constraints, network integration and latency challenges, portability and compatibility work, skills gaps, and more complex operations. The article recommends securing space and power early, designing a unified hybrid network, planning AI infrastructure separately, preserving cloud-like self-service and cost visibility, and cross-training staff.

### Source excerpt

For 15 years, enterprise IT moved in one direction: out of the data center and into the public cloud. Hardware teams were trimmed, leases weren't renewed, and "cloud first" became "cloud only." That era is ending, not because the cloud failed, but because many organizations never made a placement decision. They made a migration decision and assumed it would fit everything. AI, global macro issues, data ownership, and other trends are prompting IT leadership to rethink their cloud strategy. New data from Foundry's 2026 Cloud Computing Study, which surveyed 527 IT decision makers, shows how far the pendulum has swung. Two-thirds (66%) of respondents say their organizations have moved or plan to move applications or workloads out of the public cloud to on-premises or colocation locations. On average, respondents report that about 22% of their public cloud workloads have already been moved back and expect to move about 24% over the next 12 months. What gets lost in the "cloud is dead" headlines is that the same study shows 69% of organizations expect cloud spending to increase, and 74% default to the cloud when buying new capabilities. Repatriation isn't a retreat from the cloud. It's a rebalancing, and a hybrid estate is fundamentally harder to run than either an all-cloud or all-on-prem estate. The strategic "why?" is one important question (See our related CIO feature: Cloud repatriation on the rise but tricky questions remain). For the people who rack the gear, light the circuits and keep things running, the question is "how?" Why workloads are coming back The top driver may surprise those who remember that security was the primary objection to moving to the cloud in the first place. Sixty percent of respondents cite security concerns as a reason for moving workloads out of the public cloud, followed by budget and cost control (42%), performance and reliability (42%), and data sovereignty and privacy (40%). Compliance comes in at 31%. That's a control story more tha

## LoopSkill: Evidence-Bound Lifecycle Control and the Safety-Liveness Tradeoff in Coding Agents

DevFeed: [LoopSkill: Evidence-Bound Lifecycle Control and the Safety-Liveness Tradeoff in Coding Agents](<https://devfeed.tech/articles/loopskill-evidence-bound-lifecycle-control-and-the-safety-liveness-tradeoff-in-coding-agents-137959.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18573>)

Author: Zengjian Liu, Tommy He, ELE Zhao, HongLiang Sun

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [test](<https://devfeed.tech/topics/test.md>), [long-running](<https://devfeed.tech/topics/long-running.md>)

Tags: [artifacts](<https://devfeed.tech/tags/artifacts.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [control](<https://devfeed.tech/tags/control.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [independent](<https://devfeed.tech/tags/independent.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [routing](<https://devfeed.tech/tags/routing.md>), [safety](<https://devfeed.tech/tags/safety.md>), [swe-bench](<https://devfeed.tech/tags/swe-bench.md>)

### AI overview

LoopSkill adds evidence-bound controls to coding-agent workflows, including a schema-validated sole writer, durable outbox routing, artifact-bound reports, recovery, independent review, and heartbeat-gated finalization. In a locally frozen v3.3.12 integration tested for 1,800 seconds on a selected SWE-bench Lite subset, blind artifact success was 7/19 for LoopSkill, 11/19 for implementation plus independent review, and 14/20 for an ordinary coding agent; two cells were apparatus null. No scored LoopSkill workflow finalized, illustrating a safety-liveness and fixed-budget cost tradeoff. The 60-cell analysis was exploratory and nonconfirmatory because the original 140-cell plan was administratively truncated after interim outcomes were visible. The results do not establish comparative superiority, long-horizon efficacy, or a false-accept rate.

### Source excerpt

arXiv:2611.18573v1 Announce Type: new Abstract: Coding agents can edit repositories and announce completion, but conversational claims do not prove that artifacts, dispatches, state versions, and authority still agree. LoopSkill is an evidence-bound lifecycle control plane with a schema-validated sole writer, durable outbox routing, artifact-bound reports, recovery, independent review, and heartbeat-gated finalization. We evaluate a locally frozen v3.3.12 integration under a common 1,800-second budget on a selected subset of SWE-bench Lite. The original 140-cell plan was administratively truncated after interim outcomes were visible, so the 60-cell analysis is exploratory and nonconfirmatory. Of 58 scored cells, blind artifact success was 7/19 for LoopSkill, 11/19 for implementation plus independent review, and 14/20 for an ordinary coding agent; two cells were apparatus null. Across 18 complete LoopSkill-versus-review pairs, the descriptive risk difference was -0.222 with exact McNemar p=0.125. No scored LoopSkill workflow finalized. The results expose a safety-liveness and fixed-budget cost tradeoff. They do not establish comparative superiority, long-horizon efficacy, or a false-accept rate.

## Azure Red Hat OpenShift with hosted control planes is now generally available

DevFeed: [Azure Red Hat OpenShift with hosted control planes is now generally available](<https://devfeed.tech/articles/azure-red-hat-openshift-with-hosted-control-planes-is-now-generally-available-138655.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/azure-red-hat-openshift-hosted-control-planes-now-generally-available>)

Author: Anes Kim

Published: 2026-11-17T00:00:00Z

Content type: release

Language: en

Sources: [Red Hat Blog](<https://devfeed.tech/sources/red-hat-blog.md>)

Topics: [Azure](<https://devfeed.tech/topics/azure.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [Azure Kubernetes Service](<https://devfeed.tech/topics/azure-kubernetes-service.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [application-platform](<https://devfeed.tech/tags/application-platform.md>), [applications](<https://devfeed.tech/tags/applications.md>), [azure](<https://devfeed.tech/tags/azure.md>), [build](<https://devfeed.tech/tags/build.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [containers](<https://devfeed.tech/tags/containers.md>), [control](<https://devfeed.tech/tags/control.md>), [costs](<https://devfeed.tech/tags/costs.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [flexibility](<https://devfeed.tech/tags/flexibility.md>), [hosted](<https://devfeed.tech/tags/hosted.md>), [hybrid-cloud](<https://devfeed.tech/tags/hybrid-cloud.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [machines](<https://devfeed.tech/tags/machines.md>), [managed](<https://devfeed.tech/tags/managed.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>)

### AI overview

Azure Red Hat OpenShift with hosted control planes is generally available. Its control plane runs in a dedicated Azure service account instead of alongside worker nodes in the customer's Azure subscription, reducing the cluster footprint. The source estimates control-plane cost at $0.25/hour versus $1.152/hour for three smallest-supported Standard_D8s_v5 nodes in East US, and reports provisioning time falling from about 45 minutes to 15-20 minutes, based on Red Hat customer-deployment observations. Teams can update worker nodes independently of control-plane nodes. At GA, clusters can be deployed through Azure portal, CLI, ARM, or Bicep; Red Hat Advanced Cluster Management supports lifecycle operations and centralized observability and governance. Security features include managed and workload identities, BYOK, etcd encryption, and Azure Key Vault Managed HSM support. Isovalent Networking for Kubernetes is certified as a supported CNI. Initial regional availability includes UK South, Canada Central, Australia East, Switzerland North, Brazil South, Central India, US East 2, and West Europe; expansion is planned.

### Source excerpt

Microsoft Azure Red Hat OpenShift with hosted control planes is now generally available to help teams reduce infrastructure costs, simplify Day 2 operations, and provision clusters with more flexibility.Jointly engineered, supported, and operated by Red Hat and Microsoft, Azure Red Hat OpenShift is a fully-managed application platform designed to help organizations build and deploy workloads at scale. Teams can deploy containers, virtual machines (VMs), and AI-enabled applications with a unified application platform that offers consistency across the hybrid cloud.What changes with hosted

## CVE-2026-120699 - CubeSandbox: Unrestricted host-directory bind-mount: any sandbox-create caller mounts arbitrary host paths (RW) into their MicroVM

DevFeed: [CVE-2026-120699 - CubeSandbox: Unrestricted host-directory bind-mount: any sandbox-create caller mounts arbitrary host paths (RW) into their MicroVM](<https://devfeed.tech/articles/cve-2026-120699-cubesandbox-unrestricted-host-directory-bind-mount-any-sandbox-create-caller-mounts-arbitrary-host-paths-rw-into-their-microvm-136270.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-120699>)

Author: CVEFEED.io; github.com

Published: 2026-11-16T21:17:20Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [AI Sandbox](<https://devfeed.tech/topics/ai-sandbox.md>), [container escape](<https://devfeed.tech/topics/container-escape.md>), [mount](<https://devfeed.tech/topics/mount.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bind](<https://devfeed.tech/tags/bind.md>), [call](<https://devfeed.tech/tags/call.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [container](<https://devfeed.tech/tags/container.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-120699](<https://devfeed.tech/tags/cve-2026-120699.md>), [directory](<https://devfeed.tech/tags/directory.md>), [execution](<https://devfeed.tech/tags/execution.md>), [existing](<https://devfeed.tech/tags/existing.md>), [microvm](<https://devfeed.tech/tags/microvm.md>), [mount](<https://devfeed.tech/tags/mount.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>)

### AI overview

Before CubeSandbox 0.5.1, any authenticated tenant allowed to create sandboxes could set metadata["host-mount"] to an arbitrary existing host path. The control plane did not authorize or validate the path; Cubelet then recursively bind-mounted it as root and exposed it read-write to the tenant's MicroVM through virtio-fs. The flaw could enable host file access and modification, code execution, container-runtime access, and compromise of co-resident tenants, without a kernel or virtual-machine-monitor flaw. The source says the issue is fixed in version 0.5.1.

### Source excerpt

CVE ID :CVE-2026-120699 Published : Nov. 16, 2026, 9:17 p.m. | 1 hour, 37 minutes ago Description :CubeSandbox is an instant, concurrent, secure, and lightweight sandbox for AI agents. Prior to 0.5.1, any authenticated tenant permitted to call POST /sandboxes can supply metadata["host-mount"] with an arbitrary existing host path because the control plane performs no authorization check or allowed-prefix validation for the path. injectHostDirMounts forwards the path to prepareHostDirVolume, where Cubelet uses mount --rbind through the function to perform a recursive bind mount as root and exposes the host subtree to the tenant's MicroVM through virtio-fs, read-write by default. This allows host-root file access and modification, host code execution, access to the container runtime, and compromise of co-resident tenants without a kernel or virtual-machine-monitor flaw. This issue is fixed in version 0.5.1. Severity: 9.4 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Why we rebuilt LangSmith around the agent

DevFeed: [Why we rebuilt LangSmith around the agent](<https://devfeed.tech/articles/why-we-rebuilt-langsmith-around-the-agent-137785.md>)

Original publisher: [Read original article](<https://www.langchain.com/blog/we-rebuilt-langsmith-around-the-agent>)

Author: LangChain Accounts

Published: 2026-11-16T18:37:11Z

Content type: article

Language: en

Sources: [LangChain Blog](<https://devfeed.tech/sources/langchain-blog.md>)

Topics: [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-fleet](<https://devfeed.tech/tags/agent-fleet.md>), [agent-sprawl](<https://devfeed.tech/tags/agent-sprawl.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-leaders](<https://devfeed.tech/tags/ai-leaders.md>), [ai-platform](<https://devfeed.tech/tags/ai-platform.md>), [ai-platform-teams](<https://devfeed.tech/tags/ai-platform-teams.md>), [annotation](<https://devfeed.tech/tags/annotation.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [audio](<https://devfeed.tech/tags/audio.md>), [audit](<https://devfeed.tech/tags/audit.md>), [build](<https://devfeed.tech/tags/build.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [framework](<https://devfeed.tech/tags/framework.md>), [langsmith](<https://devfeed.tech/tags/langsmith.md>), [run](<https://devfeed.tech/tags/run.md>), [runtime](<https://devfeed.tech/tags/runtime.md>)

### AI overview

LangSmith reorganizes agent development and governance around one record per agent, linking its owner, immutable ID, type, environments, traces, evaluations, deployments, and issues. Teams can build with LangSmith Studio, open-source harnesses, or other frameworks; run agents on Agent Server or existing runtimes; and use tracing, evaluation, datasets, annotation, and Engine for agents that send traces to LangSmith. The registry and LLM Gateway provide organization-level visibility and controls, including for connected agents on platforms supporting OTLP. Agent types tailor dashboards, evaluation criteria, and data connections: general-purpose and coding types are available, with coding agents able to connect GitHub to track outcomes. The platform is composable, though validation across Agent Server previews is an example for teams building and running there. Org-level dashboards, more agent types, and identity-provider registration are described as forthcoming.

### Source excerpt

We reorganized LangSmith around a single agent record. Build, run, improve, and govern every agent from one place, on any framework or runtime.

## Scheduling the removal of the kube-proxy IPVS backend

DevFeed: [Scheduling the removal of the kube-proxy IPVS backend](<https://devfeed.tech/articles/scheduling-the-removal-of-the-kube-proxy-ipvs-backend-136734.md>)

Original publisher: [Read original article](<https://kubernetes.io/blog/2026/11/16/ipvs-removal/>)

Author: Dan Winship

Published: 2026-11-16T18:35:00Z

Content type: news

Language: en

Sources: [Kubernetes Blog](<https://devfeed.tech/sources/kubernetes-blog.md>)

Topics: [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [deprecated](<https://devfeed.tech/topics/deprecated.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [scalable-architecture](<https://devfeed.tech/topics/scalable-architecture.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [backend](<https://devfeed.tech/tags/backend.md>), [backends](<https://devfeed.tech/tags/backends.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [data](<https://devfeed.tech/tags/data.md>), [deprecate](<https://devfeed.tech/tags/deprecate.md>), [deprecation](<https://devfeed.tech/tags/deprecation.md>), [edge](<https://devfeed.tech/tags/edge.md>), [experiment](<https://devfeed.tech/tags/experiment.md>), [feature](<https://devfeed.tech/tags/feature.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-services](<https://devfeed.tech/tags/kubernetes-services.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [network](<https://devfeed.tech/tags/network.md>), [nftables](<https://devfeed.tech/tags/nftables.md>), [performance](<https://devfeed.tech/tags/performance.md>), [plan](<https://devfeed.tech/tags/plan.md>), [planning](<https://devfeed.tech/tags/planning.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [scheduling](<https://devfeed.tech/tags/scheduling.md>)

### AI overview

Kubernetes SIG Network plans to remove kube-proxy's IPVS backend in 1.40 after deprecating it in 1.35. IPVS improved on iptables' service lookup and update costs, but its limited API, lack of batch updates, incomplete Kubernetes Service compatibility, and reliance on iptables for some features made it complex to maintain and prone to scaling limits. For Kubernetes 1.36 or later on Linux kernel 5.13 or later, the article recommends switching to the GA nftables backend, which is feature complete and has performance comparable to or slightly better than IPVS. Change kube-proxy's mode and restart it; adjust any backend-specific options too. Where nftables is unavailable, iptables is an alternative: its rule generation and resync behavior have improved, though the article says it remains slower than IPVS and recommends rebooting nodes after switching.

### Source excerpt

The ipvs backend for kube-proxy was an experiment in providing a service proxy implementation with better performance than the iptables backend. While it succeeded in that goal, the kernel IPVS API has turned out to be a bad match for the Kubernetes Services API, and the ipvs backend was never able to implement all of the edge cases of Kubernetes Service functionality correctly. In Kubernetes 1.29, the project introduced the nftables backend for kube-proxy, which became GA in 1.33. Part of the plan behind adding the nftables backend was the idea that it would eventually replace both the iptables and ipvs backends. Because the ipvs backend in particular is complex, not 100% feature complete, and architecturally quite different from the other two backends (and thus more work to maintain), Kubernetes SIG Network decided to officially deprecate it as of Kubernetes 1.35. Although it currently remains available in kube-proxy (with a warning about its deprecation), we (Kubernetes SIG Network) now plan to remove it in Kubernetes 1.40. All ipvs users should therefore be planning to migrate to either the nftables or iptables backends. Why was the ipvs backend written? The ipvs backend was originally designed to fix two different kinds of performance problems in the iptables backend: First, iptables had problems with data plane latency (the speed at which clients could establish new connections to services), because kube-proxy would write a separate iptables rule to match each service IP, so every new connection would need to be matched against a long series of rules that was O(n) in the number of services in the cluster. Second, it had an even larger problem with control plane latency (the speed at which kube-proxy could process changes to services and endpoints and update the data plane rules), because kube-proxy would rewrite the entire iptables ruleset every time any service or endpoint changed. While the list of rules itself was only O(n) in the total number of endpoints,

## 40 Kubernetes Interview Questions That Expose Weak Senior Engineers

DevFeed: [40 Kubernetes Interview Questions That Expose Weak Senior Engineers](<https://devfeed.tech/articles/40-kubernetes-interview-questions-that-expose-weak-senior-engineers-136234.md>)

Original publisher: [Read original article](<https://blog.devops.dev/40-kubernetes-interview-questions-that-expose-weak-senior-engineers-f183baad39fb?source=rss----33f8b2d9a328---4>)

Author: Devrim Ozcay | Founder, ProdRescue

Published: 2026-11-16T13:26:05Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [consistency](<https://devfeed.tech/topics/consistency.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [health check](<https://devfeed.tech/topics/health-check.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>)

Tags: [advanced](<https://devfeed.tech/tags/advanced.md>), [affinity](<https://devfeed.tech/tags/affinity.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [devops](<https://devfeed.tech/tags/devops.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [docker](<https://devfeed.tech/tags/docker.md>), [failure](<https://devfeed.tech/tags/failure.md>), [interview](<https://devfeed.tech/tags/interview.md>), [interview-questions](<https://devfeed.tech/tags/interview-questions.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-cluster](<https://devfeed.tech/tags/kubernetes-cluster.md>), [latency](<https://devfeed.tech/tags/latency.md>), [load-balancing](<https://devfeed.tech/tags/load-balancing.md>), [memory](<https://devfeed.tech/tags/memory.md>), [networking](<https://devfeed.tech/tags/networking.md>), [persistent-volume](<https://devfeed.tech/tags/persistent-volume.md>), [production](<https://devfeed.tech/tags/production.md>), [programming](<https://devfeed.tech/tags/programming.md>), [questions](<https://devfeed.tech/tags/questions.md>), [routing](<https://devfeed.tech/tags/routing.md>), [scheduling](<https://devfeed.tech/tags/scheduling.md>), [staff](<https://devfeed.tech/tags/staff.md>)

### AI overview

The article argues that senior Kubernetes troubleshooting requires tracing how scheduling, networking, application lifecycle, resources, and dependencies interact. It explains practical failure patterns and diagnostics: a Pending Pod may lack an eligible node despite spare aggregate CPU; CPU limits can throttle latency-sensitive work; premature readiness can route traffic to unprepared instances; and autoscaling can worsen overload by increasing pressure on a saturated dependency. It recommends checking scheduling events and requests, probe behavior, EndpointSlices, DNS and conntrack metrics, resource throttling, traces, and downstream capacity. Other sections cover safe rollouts and shutdown, database connection budgets, stateful workload recovery, security boundaries, incident response, and tradeoffs in multi-zone, multi-region, and multi-tenant designs. The text presents hypothetical interview scenarios and diagnostic approaches, not evidence of a specific incident or a complete Kubernetes reference.

### Source excerpt

Advanced Kubernetes troubleshooting, distributed systems, networking, autoscaling, and production reliability for Senior and Staff Engineers. A Kubernetes cluster with 180 nodes had plenty of available CPU. Every deployment reported success, and the control plane appeared healthy. Yet customers were experiencing intermittent 503 errors, and the API's p99 latency had climbed from 180 milliseconds to almost nine seconds. The infrastructure team increased the number of replicas. The application team increased connection pool sizes. Someone suggested moving the workloads to larger nodes because the existing cluster was obviously struggling. The situation became worse. The problem was that newly created Pods were passing readiness checks before their applications could serve real traffic. Every additional replica introduced another temporarily unhealthy endpoint into the load-balancing path. Autoscaling was increasing the number of requests routed toward instances that were technically running but operationally useless. This is why Kubernetes interviews become considerably harder at the Staff level. Knowing which command describes a Pod is useful, but it does not demonstrate an understanding of how scheduling, network routing, application lifecycle, resource allocation, and distributed dependencies interact during failure. The following 40 questions focus on those interactions. The scenarios are hypothetical, but the failure mechanisms and diagnostic approaches are grounded in Kubernetes and production engineering behavior. Part I -- Kubernetes Scheduling and Resource Management1. A Pod is Pending even though the cluster has available CPU and memory. Why? A candidate who immediately recommends adding nodes is missing several possibilities. Kubernetes scheduling evaluates requested resources alongside node selectors, affinity rules, taints, tolerations, topology constraints, persistent-volume placement, and other scheduling restrictions. Aggregate cluster capacity is irrel

## EU AI Act Article 26: What Deployers of High-Risk AI Must Do

DevFeed: [EU AI Act Article 26: What Deployers of High-Risk AI Must Do](<https://devfeed.tech/articles/eu-ai-act-article-26-what-deployers-of-high-risk-ai-must-do-136069.md>)

Original publisher: [Read original article](<https://www.lyzr.ai/blog/eu-ai-act-article-26-deployer-obligations/>)

Author: Lyzr Team

Published: 2026-11-16T08:53:26Z

Content type: article

Language: en

Sources: [Lyzr.ai](<https://devfeed.tech/sources/lyzr-ai.md>)

Topics: [ai regulation](<https://devfeed.tech/topics/ai-regulation.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [act](<https://devfeed.tech/tags/act.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [article](<https://devfeed.tech/tags/article.md>), [cv](<https://devfeed.tech/tags/cv.md>), [eu](<https://devfeed.tech/tags/eu.md>), [eu-ai-act](<https://devfeed.tech/tags/eu-ai-act.md>), [hr](<https://devfeed.tech/tags/hr.md>), [risk](<https://devfeed.tech/tags/risk.md>)

### AI overview

Article 26 places duties on professional users of high-risk AI, including organizations outside the EU when system outputs are used in the EU. Deployers must follow provider instructions, appoint competent human overseers with authority to intervene, keep input data relevant, monitor and report risks, retain accessible system logs for at least six months, and notify workers and affected people. The article says these duties apply from December 2, 2027 for Annex III systems and August 2, 2028 for Annex I systems. Under Article 25, branding, substantially modifying, or repurposing a system into a high-risk use can make the deployer its provider. Public bodies and some credit and insurance uses also face fundamental-rights assessment requirements; financial institutions have specified monitoring and logging arrangements, and law enforcement has extra rules for post-remote biometric identification. For agents, oversight and audit depend on controlling individual actions and retaining tool-call records. A readiness sequence is to inventory systems, confirm roles, secure provider instructions and log access, assign oversight owners, set retention, prepare notices and assessments, and map

### Source excerpt

TL;DR An HR team rolls out a vendor's CV-screening agent across its EU offices (a composite scenario). Procurement signed the contract and assumed the vendor...

## Starlight: Whittle-Driven Fidelity Rescue for Satellite-Terrestrial Quantum Networks

DevFeed: [Starlight: Whittle-Driven Fidelity Rescue for Satellite-Terrestrial Quantum Networks](<https://devfeed.tech/articles/starlight-whittle-driven-fidelity-rescue-for-satellite-terrestrial-quantum-networks-134917.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.17865>)

Author: Yaliang Shi, Zhiwei Zhao, Bangguo Yuan

Published: 2026-11-16T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [Network Operations Center](<https://devfeed.tech/topics/network-operations-center.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [bandit](<https://devfeed.tech/tags/bandit.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [decoherence](<https://devfeed.tech/tags/decoherence.md>), [entanglement](<https://devfeed.tech/tags/entanglement.md>), [low-earth-orbit](<https://devfeed.tech/tags/low-earth-orbit.md>), [memory](<https://devfeed.tech/tags/memory.md>), [multi-armed-bandit](<https://devfeed.tech/tags/multi-armed-bandit.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [quantum](<https://devfeed.tech/tags/quantum.md>), [quantum-networks](<https://devfeed.tech/tags/quantum-networks.md>), [routing](<https://devfeed.tech/tags/routing.md>), [satellite](<https://devfeed.tech/tags/satellite.md>), [scheduling](<https://devfeed.tech/tags/scheduling.md>), [simulations](<https://devfeed.tech/tags/simulations.md>), [style](<https://devfeed.tech/tags/style.md>), [top-k](<https://devfeed.tech/tags/top-k.md>), [under](<https://devfeed.tech/tags/under.md>), [up](<https://devfeed.tech/tags/up.md>)

### AI overview

Starlight prioritizes satellite assistance for quantum network connections whose terrestrial entanglement is degrading, aiming to rescue them before fidelity becomes unusable. It uses Effective Age of State (EAoS) to combine heterogeneous decoherence and swapping penalties into an additive metric, then models rescue scheduling as a Restless Multi-Armed Bandit and applies a Whittle-style index approximation to select the top K connections. A two-timescale control plane and asynchronous dispatch-and-mask pipeline are designed to reduce redundant in-flight allocations. In simulations, it reaches up to 84.5% average satisfaction under constrained rescue capacity and sub-0.5-ms orchestration at 1,000 connections; the abstract reports robustness to heterogeneous memory decay and stochastic atmospheric degradation.

### Source excerpt

arXiv:2611.17865v1 Announce Type: new Abstract: A planetary-scale quantum internet is constrained by exponential attenuation in terrestrial fibers. Low-Earth-orbit (LEO) satellites provide a low-loss vacuum backbone, but limited satellite resources must be allocated among competing connections under continuously evolving and heterogeneous physical conditions. Existing satellite scheduling remains largely provisioning-oriented, optimizing satellite-resource assignment for aggregate entanglement delivery. Recent age-based approaches instead incorporate chronological freshness into entanglement scheduling. Neither line of work directly identifies the connections most urgently requiring satellite assistance as their physical states evolve. We propose Starlight, a demand-driven satellite-terrestrial entanglement routing architecture that targets degrading connections before their terrestrial entanglement becomes unusable. Starlight introduces Effective Age of State (EAoS), a physics-aware metric that maps heterogeneous decoherence and swapping-induced fidelity penalties onto a unified additive coordinate. Representing each connection by evolving EAoS, we formulate rescue scheduling as a Restless Multi-Armed Bandit (RMAB) problem and derive a closed-form Whittle-style index approximation for top-K selection. Starlight further employs a two-timescale control plane and an asynchronous dispatch-and-mask pipeline to suppress redundant in-flight allocations. Simulations show that Starlight achieves up to 84.5% average satisfaction under constrained rescue capacity and sub-0.5-ms orchestration at 1,000 connections, while remaining robust to heterogeneous memory decay and stochastic atmospheric degradation.

## Introducing Red Hat OpenShift Service Mesh 3.5

DevFeed: [Introducing Red Hat OpenShift Service Mesh 3.5](<https://devfeed.tech/articles/introducing-red-hat-openshift-service-mesh-3-5-135990.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/introducing-red-hat-openshift-service-mesh-35>)

Author: Jamie Longmuir

Published: 2026-11-16T00:00:00Z

Content type: release

Language: en

Sources: [Red Hat Blog](<https://devfeed.tech/sources/red-hat-blog.md>)

Topics: [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [istio](<https://devfeed.tech/topics/istio.md>), [SPIRE](<https://devfeed.tech/topics/spire.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-chatbot](<https://devfeed.tech/tags/ai-chatbot.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [ambient](<https://devfeed.tech/tags/ambient.md>), [dual-stack](<https://devfeed.tech/tags/dual-stack.md>), [envoy](<https://devfeed.tech/tags/envoy.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kiali](<https://devfeed.tech/tags/kiali.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [multicluster](<https://devfeed.tech/tags/multicluster.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>), [sidecar](<https://devfeed.tech/tags/sidecar.md>), [spire](<https://devfeed.tech/tags/spire.md>), [workload-identity](<https://devfeed.tech/tags/workload-identity.md>), [zero-trust](<https://devfeed.tech/tags/zero-trust.md>)

### AI overview

OpenShift Service Mesh 3.5 is generally available on OpenShift Container Platform 4.20 and later, including OpenShift 5.0. Based on Istio 1.31 and Kiali 2.33, it makes ambient-mode multiprimary multicluster and dual-stack IPv4/IPv6 generally available, and adds generally available SPIRE workload identity integration in sidecar mode, including federation; SPIRE is not yet supported in ambient mode. Sidecar-mode users can skip one Service Mesh minor release with revision-based upgrades, allowing workloads to jump two Service Mesh minor releases with one restart. Highlights include inherited mesh-wide resilience defaults, zone-aware load balancing, secure metrics scraping, and dynamic DNS for external HTTP destinations. Canary waypoint upgrades and standalone VM integration are Technology Preview; fleet management through Advanced Cluster Management is Developer Preview. Ambient multicluster currently supports multiprimary, multinetwork topology, while other topologies remain unsupported.

### Source excerpt

Red Hat OpenShift Service Mesh 3.5 is now generally available with Red Hat OpenShift Container Platform. Based on the Istio, Envoy, and Kiali projects, this release updates the version of Istio to 1.31 and Kiali to 2.33, and is supported on OpenShift Container Platform 4.20 and above, including Red Hat OpenShift 5.0. This release graduates multicluster with ambient mode, dual-stack IPv4/IPv6 with ambient mode, and Red Hat's zero trust workload identity manager (SPIRE) with sidecar mode to general availability, along with a substantial set of enhancements from Istio 1.31. Red Hat OpenShift 5.0

## LangChain Raises $300M Series C at $3B Valuation

DevFeed: [LangChain Raises $300M Series C at $3B Valuation](<https://devfeed.tech/articles/langchain-raises-300m-series-c-at-3b-valuation-133502.md>)

Original publisher: [Read original article](<https://www.langchain.com/blog/series-c>)

Author: LangChain Accounts

Published: 2026-11-13T16:06:29Z

Content type: news

Language: en

Sources: [LangChain Blog](<https://devfeed.tech/sources/langchain-blog.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [observability](<https://devfeed.tech/topics/observability.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [LangChain](<https://devfeed.tech/topics/langchain.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [company](<https://devfeed.tech/tags/company.md>), [intelligence](<https://devfeed.tech/tags/intelligence.md>), [langchain](<https://devfeed.tech/tags/langchain.md>), [langsmith](<https://devfeed.tech/tags/langsmith.md>), [platform](<https://devfeed.tech/tags/platform.md>), [raises](<https://devfeed.tech/tags/raises.md>), [series-c](<https://devfeed.tech/tags/series-c.md>), [valuation](<https://devfeed.tech/tags/valuation.md>)

### AI overview

LangChain says it raised $300 million at a $3 billion valuation in a round led by existing investor CapitalG, with participation from GIC, DFJ Growth, IVP and Sapphire Ventures. It presents LangSmith as a framework-agnostic platform for running, improving and governing agents, organized around runtime, improvement and governance. Described tools cover deployment and execution across cloud or customer environments, observability and evaluation, automated fixes and regression monitoring, trace-based fine-tuning, and centralized controls for model budgets, fallbacks, sensitive data and tool access. The announcement says more than 7,000 organizations use LangSmith and cites customer examples, including Workday reducing agent deployment time from five months to under a day; these are company-reported claims.

### Source excerpt

LangChain raises $300M Series C at a $3B valuation, led by CapitalG, to help every company own its intelligence with LangSmith, the agent engineering platform.

## Leaving VMware starts as a cost decision, but day-two operations decide whether it works

DevFeed: [Leaving VMware starts as a cost decision, but day-two operations decide whether it works](<https://devfeed.tech/articles/leaving-vmware-starts-as-a-cost-decision-but-day-two-operations-decide-whether-it-works-132368.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/13/data-management-layer-eases-vmware-exit-kubernetes-teams-kubeconna/>)

Author: Jonathan Anthony

Published: 2026-11-13T15:04:32Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [cloud-migration](<https://devfeed.tech/topics/cloud-migration.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [broadcom](<https://devfeed.tech/tags/broadcom.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [cloud-native-computing-foundation](<https://devfeed.tech/tags/cloud-native-computing-foundation.md>), [cloudnativecon](<https://devfeed.tech/tags/cloudnativecon.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cube-event-coverage](<https://devfeed.tech/tags/cube-event-coverage.md>), [data](<https://devfeed.tech/tags/data.md>), [data-management](<https://devfeed.tech/tags/data-management.md>), [electronics](<https://devfeed.tech/tags/electronics.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [everpure](<https://devfeed.tech/tags/everpure.md>), [john-furrier](<https://devfeed.tech/tags/john-furrier.md>), [jon-owings](<https://devfeed.tech/tags/jon-owings.md>), [kubecon](<https://devfeed.tech/tags/kubecon.md>), [kubecon-plus-cloudnativecon-na-2026](<https://devfeed.tech/tags/kubecon-plus-cloudnativecon-na-2026.md>), [kubeconna](<https://devfeed.tech/tags/kubeconna.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [layer](<https://devfeed.tech/tags/layer.md>), [leaving](<https://devfeed.tech/tags/leaving.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [license](<https://devfeed.tech/tags/license.md>), [machines](<https://devfeed.tech/tags/machines.md>), [management](<https://devfeed.tech/tags/management.md>), [migration](<https://devfeed.tech/tags/migration.md>), [mouser-electronics](<https://devfeed.tech/tags/mouser-electronics.md>), [moving](<https://devfeed.tech/tags/moving.md>), [news](<https://devfeed.tech/tags/news.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [openshift-virtualization](<https://devfeed.tech/tags/openshift-virtualization.md>), [operations](<https://devfeed.tech/tags/operations.md>), [platform](<https://devfeed.tech/tags/platform.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [portable](<https://devfeed.tech/tags/portable.md>), [portworx](<https://devfeed.tech/tags/portworx.md>), [portworx-by-everpure](<https://devfeed.tech/tags/portworx-by-everpure.md>), [portworx-enterprise](<https://devfeed.tech/tags/portworx-enterprise.md>), [pure-storage](<https://devfeed.tech/tags/pure-storage.md>), [rebecca-knight](<https://devfeed.tech/tags/rebecca-knight.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [ronald-waller](<https://devfeed.tech/tags/ronald-waller.md>), [thecube](<https://devfeed.tech/tags/thecube.md>), [vmware](<https://devfeed.tech/tags/vmware.md>)

### AI overview

Mouser Electronics is building a production OpenShift Virtualization cluster to move workloads off VMware, following five to six years of running containers on OpenShift. Its systems engineer says using one platform lets the team manage VMs and containers with the same tools and skills, though learning Kubernetes has been a steep curve. In a proof of concept, storage setup was straightforward: he configured the Portworx operator and storage cluster through Portworx Central using a user ID and API key, and Portworx Enterprise handled the backend. Portworx is presented as a data management layer for Kubernetes, with the goal of supporting operations across clouds and Kubernetes distributions. The interview frames the move as an opportunity to rethink day-two operations and past vendor or scripting dependencies. Portworx sponsored the segment.

### Source excerpt

Enterprises leaving legacy hypervisors are finding that moving virtual machines is only half the job, and that a portable data management layer often decides whether a Kubernetes migration succeeds. Rising license costs are pushing teams to run containers and VMs on one platform. That shift is playing out at Mouser Electronics Inc., one of the [...] The post Leaving VMware starts as a cost decision, but day-two operations decide whether it works appeared first on SiliconANGLE.

## Best Tools for AI Agent HITL (Human-in-the-Loop) Workflows

DevFeed: [Best Tools for AI Agent HITL (Human-in-the-Loop) Workflows](<https://devfeed.tech/articles/best-tools-for-ai-agent-hitl-human-in-the-loop-workflows-131246.md>)

Original publisher: [Read original article](<https://www.lyzr.ai/blog/best-tools-for-ai-agent-human-in-the-loop-workflows/>)

Author: Lyzr Team

Published: 2026-11-13T05:53:59Z

Content type: comparison

Language: en

Sources: [Lyzr.ai](<https://devfeed.tech/sources/lyzr-ai.md>)

Topics: [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [AI for customer service automation](<https://devfeed.tech/topics/ai-for-customer-service-automation.md>)

Tags: [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-governance](<https://devfeed.tech/tags/ai-agent-governance.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [approval-workflows](<https://devfeed.tech/tags/approval-workflows.md>), [human-in-the-loop](<https://devfeed.tech/tags/human-in-the-loop.md>), [tools](<https://devfeed.tech/tags/tools.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

HITL workflows should pause an agent before consequential actions and resume only after an authorized human decision. The article recommends risk-based checkpoints with context-rich requests, role-based routing, support for approval, rejection or changes, persistent state, and an audit trail. Tool choices depend on where agents run and what needs approval: LangGraph and the OpenAI Agents SDK provide developer controls over execution or tool calls, while n8n and Microsoft Copilot Studio integrate approvals into visual workflows and existing business processes. Temporal supports durable, long-running approvals; HumanLayer supplies approval infrastructure for existing agents. Lyzr's GitAgent Approval Flows govern promotion of agent versions between environments and are distinct from runtime approval of individual actions. The article emphasizes that HITL is one part of broader security and agent governance, not a substitute for them.

### Source excerpt

An AI agent can identify a customer refund request, check the transaction history, validate the refund policy, and prepare the transaction in seconds. But should...

## When Connectivity Is Not Enough: Cross-Layer Attacks on UAV C2 over 5G

DevFeed: [When Connectivity Is Not Enough: Cross-Layer Attacks on UAV C2 over 5G](<https://devfeed.tech/articles/when-connectivity-is-not-enough-cross-layer-attacks-on-uav-c2-over-5g-133250.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2603.04662>)

Author: Wagner Comin Sonaglio, \\'Agney Lopes Roth Ferraz, Andr\\'e Elias Melo, Murray Evangelista de Souza, Sidnei Barbieri, Henrique Curi de Miranda, Guevara Noubir, Louren\\c{c}o Alves Pereira J\\'unior

Published: 2026-11-13T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [5G](<https://devfeed.tech/topics/5g.md>), [Security](<https://devfeed.tech/topics/security.md>), [C2](<https://devfeed.tech/topics/c2.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [5g](<https://devfeed.tech/tags/5g.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [availability](<https://devfeed.tech/tags/availability.md>), [c2](<https://devfeed.tech/tags/c2.md>), [command-and-control](<https://devfeed.tech/tags/command-and-control.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [core](<https://devfeed.tech/tags/core.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cves](<https://devfeed.tech/tags/cves.md>), [delay](<https://devfeed.tech/tags/delay.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [experiments](<https://devfeed.tech/tags/experiments.md>), [failures](<https://devfeed.tech/tags/failures.md>), [gcs](<https://devfeed.tech/tags/gcs.md>), [hijacking](<https://devfeed.tech/tags/hijacking.md>), [layer](<https://devfeed.tech/tags/layer.md>)

### AI overview

Connectivity indicators such as registration, PDU session status, and IP reachability do not establish that UAV command and control remains safe over 5G. In experiments using MAVLink on an Open5GS/UERANSIM testbed, with a commercial Nokia core used to ground deployment assumptions, the authors report three cross-layer failures without a clean disconnect: shared User Plane contention caused stale telemetry and heavy-tailed delay; Control Plane instability led to failsafe after handover; and command rewriting at a compromised gNodeB enabled navigation hijacking. The study evaluates mitigations for timeliness, availability, and integrity failures and reports five robustness issues with assigned CVEs. This overview is based on the supplied abstract.

### Source excerpt

arXiv:2603.04662v5 Announce Type: replace Abstract: Beyond Visual Line of Sight (BVLOS) unmanned aerial vehicle (UAV) operations increasingly use 5G standalone (SA) networks for command and control (C2) between the UAV and the ground control station (GCS). The 3rd Generation Partnership Project (3GPP) has specified mechanisms for authentication and authorization of unmanned aircraft systems (UAS) in this architectural setting. As a result, operators may treat registration state, Protocol Data Unit (PDU) session status, and IP reachability as evidence that the C2 path is available. In practice, however, these connectivity indicators alone do not guarantee that closed-loop control remains operationally safe. Attacks can degrade UAS C2 when timeliness degrades under shared User Plane contention, mobility continuity fails during Control Plane instability, or command integrity is violated at a trusted next-generation Node B (gNodeB). Such failures undermine connectivity as the central security indicator for UAV operations. In this paper, we demonstrate these issues using three distinct threat models on a reproducible Open5GS and UERANSIM testbed that carries Micro Air Vehicle Link (MAVLink) over the 5G User Plane, and we use a commercial Nokia core to ground deployment assumptions. We address timeliness, availability, and integrity through experiments in which attack success is defined as forcing an unsafe closed-loop state without a clean disconnect. We observe stale telemetry and heavy-tailed delay under co-tenant User Plane contention, failsafe after handover under Control Plane instability, and navigation hijacking after command rewriting at a compromised gNodeB. We further discuss why each threat model arises and evaluate mitigations for these cross-layer failures. Across the study, we disclosed five robustness issues, all with assigned CVEs.

[Next page](<https://devfeed.tech/topics/control-plane.md?cursor=WyIyMDI2LTExLTEzVDA1OjAwOjAwKzAwOjAwIiwgIjM5YjQ2ODVlLWMzNmEtNDU5OC04NmI2LTE5ODc1NGFjNjFjMCJd>)