logoalt Hacker News

Banditoz • yesterday at 10:45 PM • 2 replies • view on HN

Sure, but I think it brings it down from "patch immediately" severity, to just "bump the JDK with next service deploy" severity.

Or, do running machines often have their CPU changed from under them without much notice?


Replies

stackskipton • yesterday at 10:55 PM

Depends on the company and deployment method. As Ops person, I generally don't think much about rolling out different Kubernetes Nodes and what SKU I select. So yes, you could be running on one node type today and tomorrow I upgrade the nodes under you.

➕ show 2 replies
Sohcahtoa82 • yesterday at 11:39 PM

> Or, do running machines often have their CPU changed from under them without much notice?

I dunno about other cloud providers, but I know AWS can move your EC2 VM from one system to another transparently. There is a server ID you can get from the metadata, but unless you're checking it frequently, you can be moved without ever being aware.

➕ show 2 replies