How to Fairly Split Shared Kubernetes Costs Across Engineering Teams

·6 views

Managing cost attribution in shared infrastructure like Kubernetes clusters is a growing challenge for engineering organizations, especially those with more than 50 engineers. Dr. Samson Tanimawo outlines a four-level framework ranging from no attribution to full charge-back, where team budgets are actually debited for their cloud usage. For shared services used across teams, costs can be distributed by equal split, usage-based allocation, or absorbed centrally, depending on the service's share of total spend. Untagged resources — often around 20% of total spend — should be assigned to a platform team to incentivize proper tagging discipline. Experience shows that after three months of cost visibility reporting, most teams voluntarily reduce waste by 15 to 25 percent.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

AI Agent Framework Choice Has Negligible Impact on Security, Study Finds

A controlled study involving 7,020 payload-verified trials across 6 large language models and 6 agent execution conditions found that the choice of AI agent framework — such as LangChain or CrewAI — accounts for only 0.06% of variance in security outcomes, a statistically insignificant result. In contrast, the type of attack used explained roughly 29% of variance, while the underlying model accounted for about 4%. The research was conducted to test whether framework selection meaningfully affects security in agentic AI systems, a common assumption among developers. The study is part of a series of four connected preprints also examining the reliability of automated detectors used in AI red-teaming pipelines, which the author found to be less dependable than widely assumed. All preprints are published under a CC BY 4.0 open license, with evaluation code available as open-source.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Security checklist for importing external AI agent definitions safely

Developers using AI coding tools like Claude Code or Codex often import external agent definition files from public collections without fully vetting them, which poses security and compatibility risks. Security-focused guidance recommends treating every external agent file as untrusted input, reading it in full rather than relying on its README before deployment. Reviewers should verify what the file claims to read, write, and execute against what the host environment actually permits, and stage files in a read-only location before placing them in any auto-watched directory. Changes should be minimal and categorised as either mechanical formatting fixes or deliberate meaning-altering decisions, each requiring a stated reason and an owner. Adopting an agent should also be contingent on clearly defining the specific gap it fills — compressed to a single sentence covering input, expected output, and explicit restrictions — before any file is added to a live agents directory.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds CSS-only poutine art with 50 fries, curds, and animated gravy

A developer created a detailed CSS art piece of poutine for DEV Community's Frontend Challenge: Comfort Food Edition, using no images, SVG, or canvas. The artwork features 50 fries, 13 cheese curds, and 11 gravy patches, with every element rendered purely through HTML and CSS. Each fry uses custom CSS variables to control its position, rotation, size, and individual browning level via color-mix() in the oklab color space. The only JavaScript present is roughly 20 lines powering a single 'Add more gravy' button that replays an animation and adds a cheese curd. The developer also shared key technical lessons, including why vmin is unreliable for responsive CSS art and why defining a scene-relative unit produces more consistent results across screen sizes.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Accessible Poutine Landing Page Using Pure CSS and No Frameworks

A developer created 'Gravy Boat,' a fictional poutinerie landing page submitted to DEV Community's Frontend Challenge: Comfort Food Edition. The interactive hero features a fully CSS-built poutine — with 50 fries and 13 curds rendered without images — controlled by a slider that adjusts gravy levels from dry to drenched. The project uses just three files with no build tools, dependencies, or JavaScript frameworks, relying on CSS custom properties and a single data attribute to drive all visual changes. Accessibility was a core focus, with all color contrast ratios verified against actual rendered values, screen reader announcements added for filters and the gravy slider, and keyboard navigation fully supported including focus management. The developer also tested the page with JavaScript disabled, discovering and fixing gaps to ensure progressive enhancement worked as intended.

0 comments Read more at DEV Community