Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Values > Value Matrix ~ Gitops Benefits > Flashcards

Value Matrix ~ Gitops Benefits Flashcards

1
Q

Less frequent deployment

A

GitOps and Codefresh of enables the organization to deploy with every code / configuration change with the safety of GitOps which allows to know exaclty what the change is and really easy rollback in case something breaks

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Inconsistent implementation of the deployment process / pipelines

A

Standardization using controllers enables the Developer to contribute their application file to GIT and take advantage of the controllers already in place.

The automation behind this is customized by the application’s resource file (manifest) not by making changes to deployment scripting or pipelines.

A single YAML file controls all the customizations to link up the live application to the application manifests

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Long time to recover from a failure

A
  1. GitOps enables you to easily see the change the caused the failure
  2. GitOps enables you to easily rollback the identified change using git-revert because it is all in Git
  3. Codefresh provides the linkage between all data sources to alert you and show you the problem but also connect it to the actual change / Jira / etc. which saves a lot of time in finding the root cause of the issue
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Inconsistent deployments on all levels (code / config / infra) - no one stop shop for changes*

A
  1. Ability to easily know what is deployed where and what is running in your production env’
  2. Many companies need auditability for various compliance requiermentes (SOC 2 / ISO / PCI / Etc.)
  3. Easier troubleshooting across the board and not just on the application changes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

“Failed promotion (Dev -> QA -> Staging -> Production) process due to missing configurations

A
  1. Git is the enforcer of documenting everything and making sure staging and production is all the same
  2. By leveraging Codefresh you will not document just the application changes but the entire configuration of the application and infrastructure which is the number 1 issue of configuration drifts between environments
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Maintaining multiple pipelines (due to pipeline sprawl)

A
  1. Less pipelines means streamlined approach to you deployments
  2. The DevOps engineer you are chatting with does not want to maintain pipelines, they want to do much more interestring things :)
  3. Efficiency improvement on the DevOps team - can do more with less / same resources (headcount)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

No live status of deployments / applications

A
  1. Live state including change history is available through GitOps UI.
  2. GitOps UI reflects the live application and the version associated. It also reflects when the live version (Kubernetes) is not in sync with the desired version (Version Control).
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Limited Protection from Introduction of Non Approved/Reviewed Changes

A
  1. Changes must be through version control.
  2. Application is protected from changes outside of the dedicated change process.
  3. In most cases, GitOps practitioners turn off or reduce capabilities to run commands against Kubernetes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

No live feedback / status of pipeline execution

A
  1. All configuration is under constant auditing.
  2. GitOps will reflect differences between desired state of application (Version Control) and the current state (Kubernetes).
  3. GitOps can also reconcile the current state to desired state when they are out of sync through auto-reconcile capability.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Developers has access to the k8s cluster in order to do their daily job (see what is where)

A
  1. User access to Kubernetes cluster is no longer required.

2. Streamlined access control - SW developers are already in Git

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Different Development Practices - Inconsistent Developer experience between app development to app
deployment (which includes configiration / infra)

A
  1. Developers commonly use the version control system to audit their changes to source code of applications.
  2. This same best practice can be applied to changes to application configurations.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Pipeline SME Required

A
  1. Standardization through GitOps controllers will enable community support.
  2. The sophisticated scripting is eliminated and replaced with YAML definitions which can be more easliy understood.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Pipeline SME Required

A
  1. Standardization through GitOps controllers will enable community support.
  2. The sophisticated scripting is eliminated and replaced with YAML definitions which can be more easliy understood.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Developers have varying degrees of internal processes and k8s knowledge

A
  1. GitOps reduce the knowledge needed to deploy. “I literally just maintain 2 manifests, a project and an application, and that’s it.
  2. Devs can focus on other key areas, rather on how to deploy things
  3. Shorten on boarding time for new devs and projects
How well did you know this?
1
Not at all
2
3
4
5
Perfectly

Values (3 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions