Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Kubeless's nine title matches show why archived platforms remain inventory

Kubeless's nine title matches show why archived platforms remain inventory An archived open-source project can stay in production for years after its repository stops receiving fixes. Kubeless is a Kubernetes-native serverless framework now maintained under the VMware archive. Nine pages named Kubeless in ZoomEye do not prove that nine clusters still run it, but they justify a review. On…

The archived open-source project Kubeless, now maintained under the VMware archive, continues to exist in production despite its repository no longer receiving updates. ZoomEye returned nine title matches for Kubeless, but this does not necessarily indicate active deployments. The archived status of the repository means that any live deployment may have missed security fixes after maintenance ended.

The security review should begin with ownership, as the team that deployed Kubeless and the cluster where it resides need to be identified, along with who receives alerts from function routes. Until a migration plan is in place, network isolation, authentication at the ingress, and least-privilege service accounts become the main controls.

Documentation pages and runtime should be separated, and for each title match, check for live function routes, Kubernetes API references, custom resource names, or a UI that matches the project.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

My shell-injection scanner flagged 3 of my own files. All 3 were wrong.

My shell-injection scanner flagged 3 of my own files. All 3 were wrong. I built a small static checker called sg audit . It finds the three call shapes that turn untrusted text into shell syntax…

  • Scanner flagged three files as vulnerable in its own source tree
  • Three flagged findings were actual vulnerabilities
  • Author suggests fixes to reduce false positives

Why Strong SREs & Backend Engineers Struggle in Meta Production Engineering Interviews (5 Advanced Technical Traps)

Most experienced SREs, DevOps engineers, Systems Engineers, and Backend SWEs do not struggle in Meta Production Engineering (PE) interviews because they lack real-world experience.

  • Parsing process info from /proc/[pid]/stat and handling JSON telemetry in Python can be tricky
  • Guard against Boolean values and non-finite floats when validating JSON telemetry in Python

More from Sunday 22 November →