From 4f68eae620b957b83113c92d505ff2c89c58f510 Mon Sep 17 00:00:00 2001 From: mluukkai Date: Sat, 23 Nov 2024 10:42:47 +0000 Subject: [PATCH] deploy: aa620755dcb6420f04eabcafea838abfbbe8d2dc --- 404.html | 2 +- 404/index.html | 2 +- credits/index.html | 2 +- faq/index.html | 2 +- index.html | 2 +- known-problems-solutions/index.html | 2 +- page-data/part-0/page-data.json | 2 +- page-data/part-1/1-first-deploy/page-data.json | 2 +- .../part-1/2-introduction-to-debugging/page-data.json | 2 +- .../part-1/3-introduction-to-networking/page-data.json | 2 +- .../part-1/4-introduction-to-storage/page-data.json | 2 +- page-data/part-1/5-summary/page-data.json | 2 +- page-data/part-1/page-data.json | 2 +- .../part-2/1-networking-between-pods/page-data.json | 2 +- page-data/part-2/2-organizing-a-cluster/page-data.json | 2 +- .../part-2/3-configuring-applications/page-data.json | 2 +- .../part-2/4-statefulsets-and-jobs/page-data.json | 2 +- page-data/part-2/5-monitoring/page-data.json | 2 +- page-data/part-2/6-summary/page-data.json | 2 +- page-data/part-2/page-data.json | 2 +- page-data/part-3/1-introduction-to-gke/page-data.json | 2 +- page-data/part-3/2-deployment-pipeline/page-data.json | 2 +- page-data/part-3/3-gke-features/page-data.json | 2 +- page-data/part-3/4-summary/page-data.json | 2 +- page-data/part-3/page-data.json | 2 +- .../1-update-strategies-and-prometheus/page-data.json | 2 +- page-data/part-4/2-messaging-systems/page-data.json | 2 +- page-data/part-4/3-gitops/page-data.json | 2 +- page-data/part-4/4-summary/page-data.json | 2 +- page-data/part-4/page-data.json | 2 +- page-data/part-5/1-kubernetes-internals/page-data.json | 2 +- .../2-custom-resource-definitions/page-data.json | 2 +- page-data/part-5/3-service-mesh/page-data.json | 2 +- page-data/part-5/4-beyond-kubernetes/page-data.json | 2 +- page-data/part-5/5-summary/page-data.json | 2 +- page-data/part-5/page-data.json | 2 +- part-0/index.html | 2 +- part-1/1-first-deploy/index.html | 2 +- part-1/2-introduction-to-debugging/index.html | 2 +- part-1/3-introduction-to-networking/index.html | 2 +- part-1/4-introduction-to-storage/index.html | 2 +- part-1/5-summary/index.html | 2 +- part-1/index.html | 2 +- part-2/1-networking-between-pods/index.html | 2 +- part-2/2-organizing-a-cluster/index.html | 2 +- part-2/3-configuring-applications/index.html | 2 +- part-2/4-statefulsets-and-jobs/index.html | 2 +- part-2/5-monitoring/index.html | 2 +- part-2/6-summary/index.html | 2 +- part-2/index.html | 2 +- part-3/1-introduction-to-gke/index.html | 2 +- part-3/2-deployment-pipeline/index.html | 10 +++++----- part-3/3-gke-features/index.html | 2 +- part-3/4-summary/index.html | 2 +- part-3/index.html | 2 +- part-4/1-update-strategies-and-prometheus/index.html | 2 +- part-4/2-messaging-systems/index.html | 2 +- part-4/3-gitops/index.html | 2 +- part-4/4-summary/index.html | 2 +- part-4/index.html | 2 +- part-5/1-kubernetes-internals/index.html | 2 +- part-5/2-custom-resource-definitions/index.html | 2 +- part-5/3-service-mesh/index.html | 2 +- part-5/4-beyond-kubernetes/index.html | 2 +- part-5/5-summary/index.html | 2 +- part-5/index.html | 2 +- registration-and-completion/index.html | 2 +- report-issue/index.html | 2 +- sanasto/index.html | 2 +- sign-in/index.html | 2 +- sign-up/index.html | 2 +- unity-assignment/index.html | 2 +- 72 files changed, 76 insertions(+), 76 deletions(-) diff --git a/404.html b/404.html index 093808ae..a26345ea 100644 --- a/404.html +++ b/404.html @@ -134,7 +134,7 @@ } } }) -

Thank you and licence

Course material

Course material has been done by Jami Kousa with the help of University of Helsinki's Tietojenkäsittelytieteen osaston sovelluskehitysakatemia (Toska) and numerous course attendees.

This material is licenced under Creative Commons BY-NC-SA 3.0 -licence so you can freely use and distribute the material, as long as original creators are credited. If you make changes to material and you want to distribute altered version it must be licenced under the same licence. Usage of material for commercial use is prohibited without permission.

mooc.fi framework

The material framework, including the quizz system and other functionality, have been created by Henrik Nygren and Antti Leinonenand Agile Education Research Group of the University of Helsinki.

Thank you and licence

Course material

Course material has been done by Jami Kousa with the help of University of Helsinki's Tietojenkäsittelytieteen osaston sovelluskehitysakatemia (Toska) and numerous course attendees.

This material is licenced under Creative Commons BY-NC-SA 3.0 -licence so you can freely use and distribute the material, as long as original creators are credited. If you make changes to material and you want to distribute altered version it must be licenced under the same licence. Usage of material for commercial use is prohibited without permission.

mooc.fi framework

The material framework, including the quizz system and other functionality, have been created by Henrik Nygren and Antti Leinonenand Agile Education Research Group of the University of Helsinki.

Part 2

Summary

Submit your completed exercises through the submission application

-

We're now at the state where we have the knowledge to deploy most software we'd develop into a Kubernetes cluster. Googling and reading the documentation will still be necessary, as always, but we can confidently move from our own local Kubernetes cluster and start using Google Kubernetes Engine.

You have reached the end of this section!

Part 3

Summary

Submit your completed exercises through the submission application

When deploying running software in a maintained Kubernetes service, it really does get that easy. Vendor lock-in is a term commonly heard when talking about the cloud. In this section, we dived into GKE and the services Google offered us. As we saw here, we could migrate almost everything to Google Cloud, with Cloud SQL and monitoring as the prime examples.

There's a case for and against vendor lock-in and you should evaluate whether to use a single cloud or possibly a multi-cloud strategy based on your needs. Nothing is preventing you from cherry-picking "the best" services from each provider. Often vendor lock-in doesn't show any negatives until after you're locked-in.

-

In the next section lets look into other practices that are included in an ecosystem like this and develop the project into its final form. We'll say goodbye to GKE, but if you have any leftover credits, you may want to hold onto them until the end of the course. Part 4

You have reached the end of this section!

How to report an issue in the material


You can report a mistake you found to the issue board of the course's Github-project. Github is a service where projects, software and source code can be managed and shared to others.

Reporting an issue requires a Github account. If you don't have an account yet, you can create it here

Before you open a new issue, please check here for an already opened issue regarding the mistake you found.


How to compose the issue

  1. Press the button above.
  2. Write a short and sweet title to the issue, for example "A typo in Part 1 in the description of exercise 30".
  3. Write a more detailed description of the issue in the comment section, for example "In Part 1 exercise 30, the sample output contains a typo. The previous code includes a line System.out.println("Enter a number");, but the sample output has the text "Exit a number"".
  4. Finally, press the green button "Submit new issue".

We might ask some clarifying questions if we are unable to fix the issue without your help. Github should send an email notification regarding these questions to the email address linked to your Github account.

Thank you for helping us improve our materials!

How to report an issue in the material


You can report a mistake you found to the issue board of the course's Github-project. Github is a service where projects, software and source code can be managed and shared to others.

Reporting an issue requires a Github account. If you don't have an account yet, you can create it here

Before you open a new issue, please check here for an already opened issue regarding the mistake you found.


How to compose the issue

  1. Press the button above.
  2. Write a short and sweet title to the issue, for example "A typo in Part 1 in the description of exercise 30".
  3. Write a more detailed description of the issue in the comment section, for example "In Part 1 exercise 30, the sample output contains a typo. The previous code includes a line System.out.println("Enter a number");, but the sample output has the text "Exit a number"".
  4. Finally, press the green button "Submit new issue".

We might ask some clarifying questions if we are unable to fix the issue without your help. Github should send an email notification regarding these questions to the email address linked to your Github account.

Thank you for helping us improve our materials!

Create new account

This course uses mooc.fi accounts. If you have previously done mooc.fi -courses, you can log in with your existing account. On this page you can create a new account, which works on majority of mooc.fi courses and services.

Create new account

This course uses mooc.fi accounts. If you have previously done mooc.fi -courses, you can log in with your existing account. On this page you can create a new account, which works on majority of mooc.fi courses and services.