Knative is a Kubernetes-based platform to build, deploy, and manage modern serverless workloads.
– Source: Google, who “owns” the project
…a reasonable follow-up question is okay, but what does “serverless” mean?
So you’re a Java/C++/web developer and you’ve heard about all of these “cloud native” technologies, and containers, and you’re wondering “excuse me, what is a Kubernetes please, and why do I care?”
…or maybe you’re a general technologist – idly curious enough to wonder what all the fuss is about but not super interested in digging into the guts of the thing.
…or maybe you tend to understand technology more big-picture than detail and you wish someone would just tl;dr it for you.
Well…welcome to the first of our Technology TLDR posts! Kubernetes, you’re up.
In late 2018, Red Hat released OpenShift 3.11. Major features we cared about were:
There are some great words here about what else was part of 3.11.
One of our favorite things to do is to observe people. You can learn a ton about people by watching them (uh…in a non-creepy way, ideally) and seeing what they display as valuable. With nerds, one of the best ways to do this is to look at their laptops – make and model and operating system, sure, but actually the best source of information is to look at their stickers. A laptop is very important among nerds. It is the tool with which they fulfill their purpose, and so it has inherent value. It’s also only so big, so real estate given to stickers is important. You can learn a ton about a nerd by the tech and things they choose to affiliate with.
In this blog post, we’re going to talk about distributed architectures, and the progression they’ve made over time. We’re going to do this because a long time ago, when we were watching the Getting Started with Docker training on PluralSite, Josh started ranting about this very topic and Laine told him it should to be a blog post because the information that just falls out of his head sometimes is really cool. You’re welcome, internet!
If you’re a Java developer who’s been working with OpenShift 3.x for a while, odds are very high you’ve worked with their OpenJDK 8 S2I image.
That container includes Red Hat’s S2I magic, which can take a git URL or a JAR and turn it into a running Java application. Combined with Spring Boot, it’s a fantastic way to get running Java containers in minutes.
There is freedom and peace and pride in being truly good at something.
Not to seem good.
Not to check off the boxes of good.
But to actually be good.
Everyone should have the freedom to be actually good.
Establishing governance philosophy in an enterprise is a tricky combination of “how much do we trust our people?” and “okay, but how much do we actually trust our people?” The fact is, people are going to screw up. Some of them might deliberately try to screw something up, but mostly they’ll just make mistakes. If the organization can’t handle mistakes, that’s a problem with the adaptability and flexibility of the organization, not with its people. This means that people’s potential mistakes are not a reason to default to not trusting them.
We were talking (arguing!) about the most important ingredients that are critical for executing technical work (aka doing Technical Stuff ™). Josh claimed there were four skills necessary, at which Laine scoffed and said that couldn’t possibly be true. Turns out, he was pretty much right – so we wrote that post. Then we realized there’s a fifth thing that’s not only necessary, but vital – but it isn’t a skill. So…we had to change the title. Usually in a list, three or four things is the right answer, but… not today, apparently.
And so, with no more ado, the ingredients critical for doing Technical Stuff are: