Live data from Hacker News

Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

redhat.com

1–10 of 107 posts

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#3
post #2

Am I reading this correctly as Kuberetes-powered fighter jets? That's certainly not going to shoot anyone in the foot...

I agree that Kubernetes-powered fighter jets is a bad idea, bordering on catastrophically bad. That said, I assume they'll be using Kubernetes as a development and test platform -on the ground- to produce some form of binary output that would go on the plane.

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#6
post #3
post #2

Am I reading this correctly as Kuberetes-powered fighter jets? That's certainly not going to shoot anyone in the foot...

I agree that Kubernetes-powered fighter jets is a bad idea, bordering on catastrophically bad. That said, I assume they'll be using Kubernetes as a development and test platform -on the ground- to produce some form of binary output that would go on the plane.

If it's any k8s distro let it be openshift. Best selinux integration.

That said, how can you not wince reading, "To do this, Lockheed wanted to adopt principles and frameworks common in software lexicon like agile, scrum, minimum viable product (MVP) and DevSecOps."

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#7
"The Lockheed Martin F-22 Raptor is one of the world’s premier fighter jets, thanks to its unique combination of stealth, speed, agility, and situational awareness."

A huge understatement. It's the only true 5th gen that's tailored for performance, rather than cost savings (ala the F-35). The others are completely unproven (Chinese) or both unproven and in extremely limited quantities, while not providing true stealth (PAK FA, though if anything, the SU-35 family is the closer analogue).

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#8
post #2

Am I reading this correctly as Kuberetes-powered fighter jets? That's certainly not going to shoot anyone in the foot...

I was thinking more along the lines of removing features to simplify maintenance, Gnome 3 style.

"Good news, General. We've found a way to lower maintenance costs in the cockpit systems by 10% if we removed this thing here on the blueprints, so we've already gone ahead with that change."

"But that's the emergency ejection system!"

"Yes, and our data indicates that it's almost never used. It doesn't really make sense to devote manpower to keeping a system running that few people ever need. If we get rid of it, we can free up developer-hours to making the canopy opening/closing action a little smoother. Everyone uses the canopy."

Post reply on HN