[EN] update GitOps #2121
Open
[EN] update GitOps #2121
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
MaryamTavakkoli
requested review from
caniszczyk,
CathPag,
JasonMorgan,
seokho-son,
iamNoah1 and
jihoon-seo
as code owners
✅ Deploy Preview for cncfglossary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
2 tasks
nate-double-u
changed the title
nate-double-u
force-pushed
the
update-gitops-v2
branch
from
6adb886 to
38dd8cb
Compare
|
Sorry for the delay on this review. I've rebased this on |
There was a problem hiding this comment.
Hi @MaryamTavakkoli,
Thanks for this. I've made a couple updates in-line. @iamNoah1, maybe you could take a look as well.
Comment on lines
+8
to
16
| GitOps is a set of best practices for managing software systems | ||
| from the beginning of the development workflow, all the way to deployment | ||
| based on [shared (OpenGitOps) principles](https://opengitops.dev/). | ||
|
|
||
| GitOps requires the desired state or configuration of the system to | ||
| be stored in a source control system like Git. | ||
| These practices are then used to execute a cohesive workflow that | ||
| leverages a source control system like Git as the “single source of truth” and | ||
| extends this practice to applications, infrastructure, and operational procedures. |
There was a problem hiding this comment.
Suggested change
| GitOps is a set of best practices for managing software systems | |
| from the beginning of the development workflow, all the way to deployment | |
| based on [shared (OpenGitOps) principles](https://opengitops.dev/). | |
| GitOps requires the desired state or configuration of the system to | |
| be stored in a source control system like Git. | |
| These practices are then used to execute a cohesive workflow that | |
| leverages a source control system like Git as the “single source of truth” and | |
| extends this practice to applications, infrastructure, and operational procedures. | |
| GitOps is a set of best practices for managing software systems from development | |
| to deployment based on [shared OpenGitOps principles](https://opengitops.dev/). | |
| It requires the desired state or configuration of the system to be stored in a source | |
| control system like Git, serving as the single source of truth. |
There was a problem hiding this comment.
@nate-double-u I would remove the reference to OpenGitOps. I think nowhere in the glossary we have references to other resources. Also I personally am not sure if GitOps was originated from OpenGitOps principles which this statement might imply.
Comment on lines
-17
to
+25
| Existing processes for infrastructure configuration management can face challenges | ||
| such as configuration drift, failed deployments, relying on a system's previous state for success, | ||
| missing documentation, or unknown development history. | ||
| Adopting a GitOps workflow can help alleviate these issues, among several others. | ||
| Existing processes for configuration management can face | ||
| challenges such as configuration drift, failed deployments, inconsistency | ||
| across different infrastructure, or unknown development history. | ||
| Emphasising on continues deployment and delivery, | ||
| a GitOps workflow can help alleviate these issues, | ||
| among several others. |
There was a problem hiding this comment.
Suggested change
| Existing processes for infrastructure configuration management can face challenges | |
| such as configuration drift, failed deployments, relying on a system's previous state for success, | |
| missing documentation, or unknown development history. | |
| Adopting a GitOps workflow can help alleviate these issues, among several others. | |
| Existing processes for configuration management can face | |
| challenges such as configuration drift, failed deployments, inconsistency | |
| across different infrastructure, or unknown development history. | |
| Emphasising on continues deployment and delivery, | |
| a GitOps workflow can help alleviate these issues, | |
| among several others. | |
| Existing processes for configuration management can face challenges such as | |
| configuration drift, failed deployments, inconsistency across different infrastructure, | |
| and unknown development history. By emphasizing continuous deployment and | |
| delivery, GitOps helps alleviate these issues. |
There was a problem hiding this comment.
Approved but I cannot signoff and commit through the webui, it says it cannot apply suggestions on deleted lines ^^
Comment on lines
29
to
+38
| GitOps is a paradigm that can be applied to a workflow | ||
| to help manage an application and cloud system infrastructure. | ||
| It enables organizations several advantages | ||
| such as better coordination, transparency, stability, and reliability of a system. | ||
| Operating in a close loop ensures the current live state of a system matches | ||
| against the desired target state, specified in the git repository. | ||
| Moreover, it helps organizations to manage the entire infrastructure | ||
| and application development and deployment lifecycle using a | ||
| single and unified tool. | ||
|
|
||
| GitOps brings organizations several other advantages | ||
| such as transparency and traceability of changes, | ||
| reliability and security through declarative states, | ||
| and rollback, revert and self-healing attributes. |
There was a problem hiding this comment.
Suggested change
| GitOps is a paradigm that can be applied to a workflow | |
| to help manage an application and cloud system infrastructure. | |
| It enables organizations several advantages | |
| such as better coordination, transparency, stability, and reliability of a system. | |
| Operating in a close loop ensures the current live state of a system matches | |
| against the desired target state, specified in the git repository. | |
| Moreover, it helps organizations to manage the entire infrastructure | |
| and application development and deployment lifecycle using a | |
| single and unified tool. | |
| GitOps brings organizations several other advantages | |
| such as transparency and traceability of changes, | |
| reliability and security through declarative states, | |
| and rollback, revert and self-healing attributes. | |
| GitOps helps organizations manage the entire infrastructure and application | |
| lifecycle using a unified tool. It brings advantages such as transparency and | |
| traceability of changes, reliability and security through declarative states, and | |
| rollback, revert, and self-healing attributes. |
There was a problem hiding this comment.
Approved but I cannot signoff and commit through the webui, it says it cannot apply suggestions on deleted lines ^^
iamNoah1
reviewed
Dec 7, 2024
There was a problem hiding this comment.
@nate-double-u left some comments, also please check the spellcheck which is failing atm
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.
Describe your changes
Updated an existing term - GitOps
Related issue number or link (ex:
resolves #issue-number)Resolves #2073 and #372
Checklist before opening this PR (put
xin the checkboxes)git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to yourgitconfigby runninggit config --global alias.ci "commit -s".