Added design thoughts and day 2 operations sections.

This commit is contained in:
Kevin Harris 2019-12-09 14:33:54 -05:00
Родитель a3299b54c7
Коммит fed410b18f
8 изменённых файлов: 58 добавлений и 30 удалений

Просмотреть файл

@ -24,7 +24,7 @@ The end goal is to take you from having a kubernetes setup that is unsecure by d
1. [Customer Scenario](customer-scenario/README.md) 1. [Customer Scenario](customer-scenario/README.md)
2. [Governance and Security Setup](governance-security/README.md) 2. [Governance and Security Setup](governance-security/README.md)
3. [Cluster Design](cluster-design/README.md) 3. [Design Thoughts](design-thoughts/README.md)
4. [Cluster Pre-Provisioning](cluster-pre-provisioning/README.md) 4. [Cluster Pre-Provisioning](cluster-pre-provisioning/README.md)
5. [Cluster Provisioning](cluster-provisioning/README.md) 5. [Cluster Provisioning](cluster-provisioning/README.md)
6. [Post-Provisioning](post-provisioning/README.md) 6. [Post-Provisioning](post-provisioning/README.md)
@ -34,8 +34,9 @@ The end goal is to take you from having a kubernetes setup that is unsecure by d
1. [Cost Governance](cost-governance/README.md) 1. [Cost Governance](cost-governance/README.md)
2. [Deploy Sample App](deploy-app/README.md) 2. [Deploy Sample App](deploy-app/README.md)
3. [Service Mesh - Do I need it?](service-mesh/README.md) 3. [Service Mesh - Do I need it?](service-mesh/README.md)
4. [Validate Scenarios](validate-scenarios/README.md) 4. [Day 2 Operations](day2-operations/README.md)
5. [Thought Leadership & Next Steps](thought-leadership/README.md) 5. [Validate Scenarios](validate-scenarios/README.md)
6. [Thought Leadership & Next Steps](thought-leadership/README.md)
## Prerequisites ## Prerequisites

Просмотреть файл

@ -1,23 +0,0 @@
# Cluster Design
This section walks us through some of the different questions/topics that come up when it comes to designing AKS clusters.
## Tenancy
???
## Number of Clusters/Environments
???
## Networking Design
???
## Next Steps
[Control Setup](/cluster-pre-=provisioning/README.md)
## Key Links
* ???

23
day2-operations/README.md Normal file
Просмотреть файл

@ -0,0 +1,23 @@
# Day2 Operations
This section walks us through the key considerations that need to be taken into account when thinking about how to operate AKS after everythign is provisioned and running.
## Resource Mgmt
* Importance of not Starving the Cluster
## Metrics Alerts
* Low Disk Space
## Logging Alerts
* SSH into Pod
## Next Steps
[Validate Scenarios](/validate-scenarios/README.md)
## Key Links
* ???

Просмотреть файл

@ -12,7 +12,7 @@ The end result on the front-end should display what type of fruit image was proc
Before we get into setting up the application, let's have a quick discussion on what container development looks like for the customer. No development environment is the same as it is not a one size fits all when it comes to doing development. Computers, OS, languages and IDEs to name a few things are hardly ever the same configuration/setup. And if you through the developer themselves in that mix it is definitely not the same. Before we get into setting up the application, let's have a quick discussion on what container development looks like for the customer. No development environment is the same as it is not a one size fits all when it comes to doing development. Computers, OS, languages and IDEs to name a few things are hardly ever the same configuration/setup. And if you through the developer themselves in that mix it is definitely not the same.
As a result, different users work in different ways. The following are just a few of the **innter devops loop** tools that we are seeing in this eco-system, feel free to try any of them out and let us know what you think. And if it hits the mark. As a result, different users work in different ways. The following are just a few of the **inner devops loop** tools that we are seeing in this eco-system, feel free to try any of them out and let us know what you think. And if it hits the mark.
### Tilt ### Tilt

27
design-thoughts/README.md Normal file
Просмотреть файл

@ -0,0 +1,27 @@
# Design Thoughts
This section walks us through some of the different thoughts/questions/topics that come up when it comes to designing solutions around AKS.
## Tenancy
???
## Number of Clusters/Environments
???
## Networking Topology & Considerations
???
## Secrets Mgmt
???
## Next Steps
[Control Setup](/cluster-pre-provisioning/README.md)
## Key Links
* ???

Просмотреть файл

@ -69,7 +69,7 @@ Ok, now that we have the governance and security controls in place we are not re
## Next Steps ## Next Steps
[Cluster Pre-Provisioning](/cluster-design/README.md) [Cluster Pre-Provisioning](/design-thoughts/README.md)
## Key Links ## Key Links

Двоичный файл не отображается.

Просмотреть файл

@ -20,7 +20,7 @@ So why even have a Service Mesh in the workshop, after all the statement above w
Let's dig a bit deeper on some of the common Service Mesh scenarios highlighted from the article above. Let's dig a bit deeper on some of the common Service Mesh scenarios highlighted from the article above.
### Encrypte Traffic Across the Cluster (mTLS between Services) ### Encrypt Traffic Across the Cluster (mTLS between Services)
This is usually near the top of the list in terms of asks. And is also one of the key **scenarios** that Service Meshes provide. Some of the questions we typically ask are do you do this today? The typical response is no, so why all of a sudden then? Which the typical response is to improve security. Ahhh, now we are getting somewhere. Instead of relying on infrastructure to secure your service, what about having the service do it? This way no matter where the service/code goes, IaaS, PaaS, in a Container, Serverless, **security travels with the application versus depending on something to be implemented.** Ok, that is great, but what about existing services or applications that need to be migrated as is. How can we do this across the entire cluster? This is usually near the top of the list in terms of asks. And is also one of the key **scenarios** that Service Meshes provide. Some of the questions we typically ask are do you do this today? The typical response is no, so why all of a sudden then? Which the typical response is to improve security. Ahhh, now we are getting somewhere. Instead of relying on infrastructure to secure your service, what about having the service do it? This way no matter where the service/code goes, IaaS, PaaS, in a Container, Serverless, **security travels with the application versus depending on something to be implemented.** Ok, that is great, but what about existing services or applications that need to be migrated as is. How can we do this across the entire cluster?
@ -89,7 +89,7 @@ linkerd dashboard
## Next Steps ## Next Steps
[Validate Scenarios](/validate-scenarios/README.md) [Day 2 Operations](/day2-operations/README.md)
## Key Links ## Key Links