Kubernetes itself is made up of many default controllers. These controllers maintain the desired state of the cluster, as set by users and administrators. Deployments, ReplicaSets, and Endpoints are just a few examples of cluster resources that are managed by their own controllers. Each of these resources involves an administrator declaring the desired cluster state, and it is then the controller's job to maintain that state. If there is any deviation, the controller must act to resolve what they control. I know now it wasn’t just that. I’d just finished my first year of college basketball and was feeling burned-out. Not with playing but with the concept of practice, practice, school, and practice. The grind probably wouldn’t have gotten to me if it hadn’t been for the girl. I couldn’t seem to get over her, and she was still in town—I could bump into her anywhere. I knew I didn’t want to find myself on a barstool at Maloney’s every night drinking to forget. I could already imagine the rut I could dig. It was time to do something. I've listened to just about every SEAL book on Audible and the Operator is my favorite. You will be moved in all the right ways by this story. We began this chapter by examining some of the problems that arise when manually managing applications and clusters without Operators. This was done through the lens of a simple generic web application based on a couple of Pods and a Persistent Volume. The main difficulties in managing something such as this include the time and resources required to debug applications. This is especially important in cloud applications, where high availability ( HA) and consistent uptime are top priorities. In this chapter, we introduced the fundamental concepts of the Operator Framework. These include the Operator SDK, OLM, and OperatorHub. In addition to the development and distribution pillars of the Operator Framework, the Capability Model provides an additional tool for measuring the functionality of an Operator. Throughout this book, we will be exploring these components in deeper detail to get a hands-on understanding of how they actually work.

When developing an Operator, the image is compiled into a bundle, and that bundle is installed via OLM. The bundle consists of several YAML files that describe the Operator, its CRD, and its dependencies. OLM knows how to process this bundle in its standardized format to properly manage the Operator in a cluster. There are a number of reasons a cluster state can change. Some may not even technically be considered a failure, but they are still changes of which the running application must be aware. For example, if your database access credentials change, then that update needs to be propagated to all the Pods that interact with it. Or, a new feature is available in your application that requires tactful rollout and updated settings for the running workloads. This requires manual effort (and, more importantly, time), along with a keen understanding of the application architecture. I wasn’t going to hook any giant marlins in Butte, Montana, but I could aspire to be like Mike. There was a school right next to my new house, Greeley Elementary, with an outdoor basketball hoop. So I asked my mom to get me a basketball and she did. I would go over there every day and play by myself, hours at a time, just seeing how many free throws in a row I could make, working on my jump shot, driving left, driving right. My dad, who was about forty then, had played some at the University of Montana. He was a damn good basketball player. He found out what I was doing and he said, “Hey, do you want to start playing?” The American male, as a species, is in crisis. At least in the realm of public life, the norms for masculine behavior in our society have deteriorated to such an extent that American men are now expected to act like frat boys for the rest of their lives. You just wouldn’t be manly if you acted any other way. This is the message we get from our popular publications, television and movies. The wild bachelor party where a prostitute is accidentally (or purposefully) killed and her body must be hidden in the desert has become a comfortable trope of too many popular narratives. Maxim and Esquire, even Men’s Journal, to say nothing of more overtly pornographic men’s magazines like Playboy and Penthouse have added a sheen of respectability to juvenile behavior. They provide guides for how to dress for success and debauchery, rules for the etiquette of manliness, liquor and leather ads and a nice war story or two thrown in for political relevance. Alcohol and women, tobacco and (depending on geography) firearms are not so much to be savored as part of a full life, but instead are the gadgets and gizmos of manhood to be consumed with abandon, in public, on camera.When I graduated high school in Butte, Montana—the same school my grandfather and father had graduated from—and enrolled at Montana Tech, the local college, this girl was still a junior. It’s just one of those things; you’re not going to date a high school girl when you’re in college. So I stayed away, but I couldn’t keep my mind off her. She went on doing her high school thing, dating and going to dances, which she damn well should have been doing. But I wanted it both ways, me having my fun and her staying on hold. I simmered miserably for weeks, then finally snapped when I heard she’d spent the day with some high school boy. With a couple drinks in me I went to her house to find out what was going on, and promptly made a complete ass out of myself. Next, we examined OperatorHub and its role in the broader open source Kubernetes community. As an open index of freely available Operators, OperatorHub serves to promote the adoption and maintenance of Operators. It consumes the same manifests as OLM to provide a standardized set of metadata about each Operator to users. These three pillars are what have made the Operator Framework so successful. They transform the framework from just development patterns to an encompassing, iterative process that spans the entire lifecycle of an Operator. This helps support the contract between Operator developers and users to provide consistent industry standards for their software. We’d been bombarded with hagiographic profiles and heroic narratives of almost all our military leaders…Here, I realized, was a chance to tell a different story, to capture what the men running the war actually said and did. What I’d been seeing and hearing was distinctly human: frustration, arrogance, getting smashed, letting off stress” (74). He refers to seeing a Michael Jordan video, and if you know the story about what made Michael Jordan so great, then you start to see the same foundation, and drive that makes a Rob O'Neill, or any body at his level great.

Level V—Auto Pilot: Level V is the most sophisticated level for Operators. It includes Operators that offer the highest capabilities, in addition to the features in all four previous levels. This level is called Auto Pilot because the features that define it focus on being able to run almost entirely autonomously. These capabilities include Auto Scaling, Auto-Healing, Auto-Tuning, and Abnormality Detection. Words formed so clearly in my mind that I may have said them out loud. “Oh, my God, these are hard. I need to get better at pull-ups!” The lifecycle of an Operator begins with development. To help with this, the Operator SDK exists to guide developers in the first steps of creating an Operator. Technically, an Operator does not have to be written with the Operator SDK, but the Operator SDK provides development patterns to significantly reduce the effort needed to bootstrap and maintain an Operator's source code.Kubernetes is a powerful microservice container orchestration platform. It provides many different controllers, resources, and design patterns to cover almost any use case, and it is constantly growing. Because of this, applications designed to be deployed on Kubernetes can be very complex. Essentially, this is the story of one Vivian Dalton — though alternating chapters are told from other characters’ points of view — who works as a switchboard operator in the small town of Wooster, Ohio — a real-life place — during the early 1950s. Though Vivian and her co-workers aren’t supposed to listen in on the phone conversations they connect, they do so anyway. One day, as Vivian is listening to a phone call, a piece of gossip about her own family is revealed, seeking to crumble the façade of Vivian’s life. It takes about half of the book before the reader is brought into what that gossip is, but, in a 1950s small town in America, it probably was as powerful as a match being dropped into a pool of gasoline. The puzzle of this book is whether Hastings, who seems to have some guts and a lot of experience on the ground, understands the military he so roundly criticizes, or cares to in the first place. There's a difference between traveling as a correspondent and traveling as a man with a rifle who may have to use it to commit state-sponsored killings, then live with the aftermath.