It's also most certainly not the only example of such behaviour.
My personal favourite to use on people with an IT background is IPv4 exhaustion.
Global warming is related to the finite capacity of the atmosphere to absorb an excess pollutant, which is growing exponentially thanks to a burgeoning human population. Address exhaustion is due to a finite resource being exhausted due to an increasing population of people with networked devices.
Both are slow-motion, global-scale disasters.
Both have no clear deadline or dramatic event.
Neither has any immediacy, it's all just graphs trending the wrong way.
Just like how no individual or enterprise profits from fixing global warming, nobody profits from fixing IPv4. If you make a personal sacrifice to give up IPv4, nobody will reward you.
In both cases, the incumbents are hoarding resources, and trying to stave of the inevitable change that will devalue their accumulated capital. IPv4 has become a commodity resource traded on markets, to be hoovered up by mega-corporations to fend off smaller players from competing head to head with them. Do you think Saudi Aramco will just let go of their trillion dollars of unexploited oil fields? Do you think Azure or AWS will just give up on their millions of accumulated addresses?
There is one key difference however:
Global warming has some legitimate debate about its exact course: what specific path the curve will follow, and which model is accurate.
IPv4 exhaustion had no debate whatsoever. The exhaustion of each regional pool was predicted to the week, years ahead. Each one occurred exactly on schedule.
What have YOU done to "save the world"? What have you sacrificed, personally to enable IPv6-only networking?
You have no excuses, you can't even say you didn't see it coming!
So:
Have you forced your company to upgrade to IPv6?
Have you written your software to work flawlessly in an IPv6-only network?
Have you made it a hard requirement for all networked products you purchase or use to be IPv6 native?
No, no you haven't.
Azure doesn't support IPv6 in any meaningful way. Neither does any other major cloud provider. It's an add on. An optional extra, that may or may not work.
Kubernetes, the "future", does not support IPv6 right now, 21 years after it became widely available, and years after several regions dropped below their last /8 of available address space.
"It would be a lot of work to add IPv6 support" I hear people complaining.
Oh... oh wow. Gee. Golly. I didn't know! I take it all back. Let's just stay on IPv4 forever and use NAT five layers deep. I hear Global Warming is going to take a lot of work to fix also. Let's just all buy air conditioners and never venture outside again.