You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During development, you can skip rebuilding the container and instead work from the `/localhost` folder inside of the container. The `/localhost` folder is the user's `$HOME` folder mounted into the container. Any files on this system will be persisted.
314
318
{{% /dialog %}}
315
319
316
320
# Run the shell
317
321
```bash
318
-
> $CLUSTER_NAME
322
+
$CLUSTER_NAME
319
323
```
320
324
321
325
For example, to access your geodesic project shell do the following.
Copy file name to clipboardExpand all lines: content/kubernetes-backing-services/ingress/_index.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ Configuring a web server or load balancer used to be harder than it should be, e
7
7
Typically, services and pods have IPs only routable by the cluster network. All traffic that ends up at an edge router is either dropped or forwarded elsewhere. Conceptually, this might look like:
8
8
9
9
10
-
#####
10
+
#####
11
11
```yaml
12
12
internet
13
13
|
@@ -18,7 +18,7 @@ Typically, services and pods have IPs only routable by the cluster network. All
18
18
An Ingress is a collection of rules that allow inbound connections to reach the cluster services.
19
19
20
20
21
-
#####
21
+
#####
22
22
```yaml
23
23
internet
24
24
|
@@ -56,13 +56,15 @@ In order for the Ingress resource to work, the cluster must have an Ingress cont
56
56
57
57
An Ingress Controller is a daemon, deployed as a Kubernetes Pod, that watches the API server's /ingresses endpoint for updates to the Ingress resource. Its job is to satisfy requests for Ingresses.
58
58
59
-
##### :information_source: Note
60
-
> In theory, you can install several ingress controllers, for example, for different types of service.
61
-
>This would require you to specify explicitly which instance of the ingress controller to associate with. Therefore, we recommend to only have one controller per cluster.
In theory, you can install several ingress controllers, for example, for different types of service.
61
+
This would require you to specify explicitly which instance of the ingress controller to associate with. Therefore, we recommend to only have one controller per cluster.
The goal should not include any objectives, strategies or tactics. It's very high-level and should be easily understood by anyone in the business.
20
+
{{% /dialog %}}
20
21
21
22
# Objectives
22
23
23
24
List of measurable outcomes that will be achieved by executing the strategies. Objectives describe *what* will be achieved by the goal. This is the barometer for success. It's how we will know we've achieved our goal.
24
25
25
26
**Example**: "Reduce page load times by 25%"
26
27
27
-
##### :information_source: HINT
28
-
> Typlically, these objectives are described using the following terms: "minimize", "increase", "reduce", "eliminate".
Typically, these objectives are described using the following terms: "minimize", "increase", "reduce", "eliminate".
30
+
{{% /dialog %}}
29
31
30
32
# Strategies
31
33
32
34
The specific approach that will be taken to achieve a goal and objectives. They describe *why* the objectives will be met, therefore try to map all the strategies to the objectives.
33
35
34
36
**Example**: "Use caching to reduce page load times"
35
37
36
-
##### :information_source: HINT
37
-
> Strategies should not encompass any tactics. That is, there might be multiple tacts that can be executed to fulfill the strategy. This is geared towards the CIO/CTO audience that might not be well versed on the tactics. For example, "Use Caching to reduce page load times"
Strategies should not encompass any tactics. That is, there might be multiple tacts that can be executed to fulfill the strategy. This is geared towards the CIO/CTO audience that might not be well versed on the tactics. For example, "Use Caching to reduce page load times"
40
+
{{% /dialog %}}
38
41
39
42
# Tactics
40
43
41
44
Tactics describe *how* specific tools will be used to implement the strategies. Try to map the tools to the strategies.
42
45
43
46
**Example**: "Use Memcache to cache API responses"
44
47
45
-
##### :information_source: HINT
46
-
> Tactics describe the exact solution that will be implemented by the engineering team. Typically, this is a list of technologies (E.g. MySQL, Memcache, Kubernetes, Helm, Docker, etc)
Tactics describe the exact solution that will be implemented by the engineering team. Typically, this is a list of technologies (E.g. MySQL, Memcache, Kubernetes, Helm, Docker, etc)
Copy file name to clipboardExpand all lines: content/release-engineering/build-harness.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,11 @@ excerpt: ''
5
5
6
6
The `build-harness` is a collection of [Makefiles](doc:makefile) to facilitate building stuff. It supports Golang projects, Dockerfiles, Helm charts, and much more.
|[`github-authorized-keys`](https://github.com/cloudposse/github-authorized-keys/)| A Golang project that leverages `docker/%`, `go/%`, `travis/%` targets|
45
+
|[`charts`](https://github.com/cloudposse/charts/)| A collection of Helm Charts that leverages `docker/%` and `helm/%` targets|
46
+
|[`bastion`](https://github.com/cloudposse/bastion/)| A docker image that leverages `docker/%` and `bash/lint` targets|
47
+
|[`terraform-null-label`](https://github.com/cloudposse/terraform-null-label/)| A terraform module that leverages `terraform/%` targets|
0 commit comments