Update rationale.md #3096
Merged
Update rationale.md #3096
Conversation
This file contains 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
bgrant0607
requested review from
droot,
frankfarzan,
mengqiy,
yuwenma and
natasha41575
as code owners
davidreuss
reviewed
May 6, 2022
site/guides/rationale.md
Outdated
|
|
||
| This enables WYSIWYG management of configuration similar to how the live state can be modified with traditional imperative tools: | ||
| Kpt enables WYSIWYG management of configuration similar to how the live state can be modified with traditional imperative tools, thus eliminating this dichtomy: |
There was a problem hiding this comment.
Thanks. Clearly spellcheck would be useful.
davidreuss
reviewed
May 6, 2022
|
Thanks for the review, @davidreuss. I've found that there's been a lot of confusion about where I'm trying to go with kpt and Configuration as Data, so I'm working to clarify that. |
justinsb
approved these changes
May 6, 2022
|
|
||
| Most Kubernetes users either manage their resources using conventional imperative graphical user interfaces, command-line tools (kubectl), and automation (e.g., Operators) that operate directly against Kubernetes APIs or IaC tools, such as Helm, Terraform, cdk8s, or one of the [dozens of other tools](https://docs.google.com/spreadsheets/d/1FCgqz1Ci7_VCz_wdh8vBitZ3giBtac_H8SBw4uxnrsE/edit#gid=0). | ||
| As companies expand the number of Kubernetes development and production clusters they use, creating and enforcing consistent configurations and security policies across a growing environment becomes difficult. At that point, the choice of management surface is no longer driven by preference, but by capabilities. To address this challenge, it is increasingly common for platform administrators to use “GitOps” methodology to deploy configuration consistently across clusters and environments with a version-controlled deployment process. Using the same principles as Kubernetes itself, GitOps reconciles the desired state of clusters with a set of Kubernetes declarative configuration files in a source control system, namely git. |
There was a problem hiding this comment.
Nit: methodology -> methodologies (?).
Supernit: We should also decide how to do the line breaks here - all on one line makes it a little harder to review.
I think it might be easier to do follow-on PRs for these nits; I'll focus on the content.
yuwenma
approved these changes
May 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@selfmanagingresource
I took a stab at updating the rationale. Next, I recommend moving it to precede the concept section of the book.