SShortSingh.
Back to feed

Red Hat Offers Two-Node OpenShift Edge Clusters, But Capacity Trade-offs Remain

0
·58 views

Red Hat has introduced two production-ready architectures — Two-Node with Arbiter (TNA) and Two-Node with Fencing (TNF) — that allow OpenShift edge clusters to run on just two servers instead of the traditional three. TNA uses a lightweight arbiter node to maintain quorum without carrying workloads, and reached general availability with OpenShift 4.20, while TNF relies on hardware fencing to prevent split-brain scenarios and became generally available with OpenShift 4.22 in July 2026. Both approaches are designed to cut costs at remote sites such as retail stores, clinics, and factory floors, where a third full-sized server adds significant expenses beyond just hardware. However, neither architecture changes the underlying capacity math: when one of the two workload-bearing nodes fails, only a single node remains to handle all production workloads. The two topologies preserve cluster availability in a degraded state but do not replicate the N+1 failure capacity that a standard three-node cluster provides.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

PWA or native app: when a web app suits a business better

The article argues that many businesses asking for an app really need a website or a progressive web app, and that building a native app before validating demand is an expensive mistake. A PWA is a website with a manifest and service worker, so it installs to the home screen, works offline, and skips app store review. Rough cost and timeline comparisons put websites at about $500 in 3–10 days, PWAs at about $800 in 2–4 weeks, and native apps at about $1,500 in 4–10 weeks plus store fees. The author lists cases that favor a PWA, such as validating a hypothesis, internal field tools, frequent repeat visits, and tight budgets, and cases that call for native, such as heavy background processing, complex hardware, or store-only requirements. A car dealer example describes a PWA built in 1–2 weeks for vehicle inspections, which confirmed demand and avoided store accounts and moderation.

0
ProgrammingDEV Community ·

Morocco Transport Site Uses Build-Time Checks to Catch Price Errors Before Deploy

A small Moroccan transport booking business, navetteforyou.com, operates across eight languages with more than 640 pages and thousands of price points. To avoid costly pricing mistakes, it built a build-time validation pipeline that crawls every generated page and extracts currency amounts and structured data. Any price below a set minimum fails the build, and cross-language mismatches are flagged as warnings. The team also uses AI to draft translations, generate Schema.org markup, and define the patterns the checker looks for, while the validation itself relies on deterministic matching. According to the author, no pricing errors have reached production since deployment, with about four seconds added to build time.

0
ProgrammingDEV Community ·

Alibaba's Qwen4-Max Launches as Closed API, Breaking Earlier Open-Source Pledge

Alibaba's Qwen team had recently pledged to keep its models open source, but it has now released its flagship Qwen4-Max without downloadable weights, offering access only through a closed QwenCloud API. The model reportedly has 2.4 trillion total parameters, 71 billion active per token, and a 1M-token context window. Its architectural changes reportedly cut token usage on Terminal-Bench 4.0 by about 48%–49% and lower average Work360 task cost by 62%. The author argues that, because teams cannot self-host the model, these efficiency gains do not provide the sovereignty or fallback options that open weights would, creating vendor lock-in risks.

0
ProgrammingDEV Community ·

Recording Product Demo Videos With Playwright: Six Common Failures

Playwright can capture a browser session as video in a few lines of code, which makes automated product demos appear simple to produce. However, the raw recording is only a test artifact and falls short as a demo because it lacks a visible cursor, shows text appearing instantly, and does not wait for the page to finish loading. Its output also looks blurry when zoomed in. The article notes that a demo additionally needs a clear story, defining the task being shown and its audience before scripting begins. It presents fixes for these issues, including logging cursor movement to overlay later, setting device scale at the browser level to get sharper footage, and waiting for page mutations to settle rather than using fixed delays.