00:00.0
00:03.0
Sources mention his docker image was based off ubuntu
00:03.1
00:05.8
Its reported size is greater than 9 gigs and has caused severe internet congestion to download
00:05.9
00:10.0
We have lost container registries in AWS, GCP, and Azure
00:10.1
00:16.0
We have reason to believe that he packaged an entire VM into the docker container. We are working actively to question him regarding these claims.
00:17.6
00:20.5
Ah yes, surely the container itself is extremely performant and is working great inside kubernetes
00:28.0
00:30.2
The entire production Kubernetes cluster..
00:30.3
00:35.5
The entire production Kubernetes cluster has crashed with numerous pods lost. We have no way to stop them from crashing. Virtual racks is in flames and we fear we will lose our early adopters.
00:52.7
00:58.0
Everyone in this room except for Mark, David, Vrajesh, and Jenn. You can leave now
01:12.6
01:14.0
Who the hell gave him developer access in AWS?!
01:15.3
01:18.0
A tester I could understand, but developer!?
01:18.1
01:25.7
He had no business touching anything outside of minikube. Which one of you actually believed his seat monitor was ever going to work
01:25.8
01:30.9
My god, we are going to lose so much damn money on this effort. Joe is going to have me in his office on Monday morning
01:31.7
01:41.0
We need to come up with a plan, blame David Strand. Say he tried to help him and didn't want to cause any trouble. I don't care what you have to do, just take away his damn privileges now
01:41.1
01:42.4
Sir, we can just take his privileges away like that. Our IAM is not built that way
01:42.5
01:45.8
Don't give me that IAM crap, do something or your job is finished. Re-structure the damn roles now!
01:45.9
01:48.4
The roles alone would take hours. We don't have the manpower to do something so radical
01:48.5
02:02.9
Manpower!? What are you a junior developer!? I suppose I have to do everything myself. Just re-map his role to a tester account and the issue will be solved