Skip to content

Commit

Permalink
Merge pull request #105 from stakater/update-ld-images
Browse files Browse the repository at this point in the history
[MAN-1] update images
  • Loading branch information
rasheedamir authored Jan 6, 2023
2 parents e2a5fb9 + b5ae1d0 commit 76e88e1
Show file tree
Hide file tree
Showing 5 changed files with 2 additions and 2 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions docs/content/sre/local-development/inner-vs-outer-loop.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Inner vs Outer Loop

![Inner vs Outer Loop](./images/local-development-2.png)
![Inner vs Outer Loop](./images/local-development-6.png)

The inner loop consists of local coding, building, running, and testing the application—all activities that you, as a developer, can control. The outer loop consists of the larger team processes that your code flows through on its way to the cluster: code reviews, integration tests, security and compliance, and so on. The inner loop could happen mostly on your laptop. The outer loop happens on shared servers and runs in containers, and is often automated with continuous integration/continuous delivery (CI/CD) pipelines. Usually, a code commit to source control is the transition point between the inner and outer loops.

First, let's consider a typical workflow for a developer whose team has adopted Kubernetes. The workflow starts with local development activities and finishes with containers deployed and code running in one or more Kubernetes clusters. To help visualize this flow, you can think of it in terms of an inner loop and an outer loop. Following figure illustrates the interplay of these loops in a Kubernetes development process.

![A flow diagram of the inner and outer loops in a Kubernetes development process](./images/inner-vs-outer-v2.png)
![A flow diagram of the inner and outer loops in a Kubernetes development process](./images/inner-vs-outer-v4.png)

Notice that, while you code, you are constantly iterating through various development activities: You code, build, deploy locally, and debug—and you keep going until you achieve a degree of feature completeness. At some point, you will be ready to transition from inner to outer, right? Not so quick.

Expand Down

0 comments on commit 76e88e1

Please sign in to comment.