Refresh What landing page for Kubecon #35
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Clean up technical marketing before Kubecon
Clarify the content after viewing the Netlify preview.
tlwu2013
reviewed
May 19, 2022
| <h2 class="of-heading of-heading--md">What is an Operator after all?</h2> | ||
| <p>An Operator represents human operational knowledge in software, to reliably manage an application. They are methods of packaging, deploying, and managing a Kubernetes application.</p> | ||
| <p>The goal of an Operator is to put operational knowledge into software. Previously this knowledge only resided in the minds of administrators, various combinations of shell scripts or automation software like Ansible. It was outside of your Kubernetes cluster and hard to integrate. With Operators, CoreOS changed that.</p> | ||
| <p>Operators implement and automate common Day-1 (installation, configuration, etc) and Day-2 (re-configuration, update, backup, failover, restore, etc.) activities in a piece of software running inside your Kubernetes cluster, by integrating natively with Kubernetes concepts and APIs. We call this a Kubernetes-native application. With Operators you can stop treating an application as a collection of primitives like Pods, Deployments, Services or ConfigMaps, but instead as a single object that only exposes the knobs that make sense for the application.</p> |
There was a problem hiding this comment.
what I like about the old/existing text here is:
- it better categorizes the activities between day1 and day2, so it's clear that Operator is more than getting things up and running but also covering the operational aspects for day 2
- I prefer "exposes the knobs" better than "ports" since "knobs" conveys the idea of "easy configurable options" better (and "port" could be misunderstood as a socket/port or endpoint, etc).
There was a problem hiding this comment.
Thanks for the feedback. This was a very aggressive edit on the first pass. I will add back the information on Day 1 and Day 2 Operations, though I will try to break it up into a couple of shorter sentences.
tlwu2013
reviewed
May 19, 2022
| <section class="of-section--largetext"> | ||
| <div class="of-section--largetext__item"> | ||
| <h2 class="of-heading of-heading--xl">Who's building Operators?</h2> | ||
| <p class="of-section--largetext__content">Cluster Admins, Site Reliability Engineers, Software Engineers, and DevOps Engineers encapsulate their shared knowledge into an operator, offering a resilient and robust solution that manages an application in a native Kubernetes way available everywhere OLM is installed.</p> |
There was a problem hiding this comment.
(it could be just me) I like the existing single sentence better being more concise and more natural on "available everywhere OLM is installed" than making it a standalone sentence. (but I'm open to other opinions too)
There was a problem hiding this comment.
Noted. Let me try to rework it a little so I can keep the conversational style of the original intact, and keep it punchy and straightforward.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Clean up technical marketing before Kubecon