So his solution to the perceived problem of long development/deployment cycles in the DoD is to install Kubernetes and Istio on a fighting jet?! Making an already complex product even more complex by adding multiple layers of unknown quality on top of it to fight a problem that has actually not much to do with the choosen solution at all!? That sounds like a real smart idea, except that it doesn't. He surely has an impressive track record if you look at his linkedin profile. Until you realize, that he had written this all by himself and that it includes sentences like this: "Built DoD’s first side-car container security stack for Kubernetes to ensure automated cybersecurity..." That's complete nonsense. It "ensures(!) automated(!) cybersecurity"...what does this even mean? And if that would be possible, why doesn't everybody do it? I guess that's because most people, me included, aren't that smart. I could go on and on about why this is all wrong on multiple levels, but I could just cite his last sentence from the self description: "...early contributor to the programming language PHP" That actually says it all.
I did not find it interesting. Repetitive and forceful, unrelated Could have worked on cases, challenges and how they were overcome. Eg. Fuel injection system is now controlled by a set of containers with HPA, which otherwise would have to be filled by redundant heavy VMs and like.
At 11:10 you can see the exact same legacy mess he starts off complaining about, I really hope they're not genuinely using that much software to manage kubernetes. Pick 1 maybe 2 tools for each step not all of them... This was a disappointing talk.
in a world where there were no bad guys this would be great. otph in the real world that includes real bad guys this is obviously a catastrophe in the making
in a world where there were no bad guys this would be great. otph in the real world that includes real bad guys this is obviously a catastrophe in the making
Kubernetes kubernetes everywhere!
that's awesome..
So his solution to the perceived problem of long development/deployment cycles in the DoD is to install Kubernetes and Istio on a fighting jet?! Making an already complex product even more complex by adding multiple layers of unknown quality on top of it to fight a problem that has actually not much to do with the choosen solution at all!? That sounds like a real smart idea, except that it doesn't. He surely has an impressive track record if you look at his linkedin profile. Until you realize, that he had written this all by himself and that it includes sentences like this:
"Built DoD’s first side-car container security stack for Kubernetes to ensure automated cybersecurity..."
That's complete nonsense. It "ensures(!) automated(!) cybersecurity"...what does this even mean? And if that would be possible, why doesn't everybody do it? I guess that's because most people, me included, aren't that smart. I could go on and on about why this is all wrong on multiple levels, but I could just cite his last sentence from the self description:
"...early contributor to the programming language PHP"
That actually says it all.
I did not find it interesting. Repetitive and forceful, unrelated
Could have worked on cases, challenges and how they were overcome.
Eg. Fuel injection system is now controlled by a set of containers with HPA, which otherwise would have to be filled by redundant heavy VMs and like.
More complex but more standard for most of the development world.
It's about standardizing the tech stack. Meaning reducing technical debt, meaning simplifying processes.
At 11:10 you can see the exact same legacy mess he starts off complaining about, I really hope they're not genuinely using that much software to manage kubernetes.
Pick 1 maybe 2 tools for each step not all of them...
This was a disappointing talk.
Ok..what?
The presentation slides are terrible, information overload...
Welcome to the DoD :) www.wired.com/images_blogs/dangerroom/2010/09/atl_wall_chart.jpg
in a world where there were no bad guys this would be great. otph in the real world that includes real bad guys this is obviously a catastrophe in the making
This sounds like the most stupid thing i've heard in ages. Especially considering how unstable Docker tends to be
unstable when?
@@amabamo5769 well... it fails more often than a bare metal RTOS installation.
@@amabamo5769 Docker can give up at any given moment and just stop responding, i've learn this the hard way after running it in prod multiple years
@@nunezmartin7441 Do you have any logs? Did you report any bugs?
@@amabamo5769 many times over the years :)
in a world where there were no bad guys this would be great. otph in the real world that includes real bad guys this is obviously a catastrophe in the making