チュートリアルは順番に完了するように設計されています。各チュートリアルは、モニタリングと自動スケーリングが可能なサンプル アプリケーション インフラストラクチャを作成するため、前のチュートリアルをベースにしています。チュートリアルを進めていくと、新しいスキルを習得し、追加の Google Cloud プロダクトとサービスを使用できるようになります。目標は、ご自身の環境でスケーラブルなアプリケーションをより快適に実行するために必要なコア コンポーネントをすべて学習することです。
導入への道のり
この一連のチュートリアルでは、Cymbal Bank のプラットフォーム リーダーの役割を担います。Cymbal Bank は、約 10 年前に 2 台のサーバーで決済処理を行う小さな会社としてスタートしました。以来、何千人もの従業員を雇用し、成長し続けるエンジニアリング組織を擁する、成功を収めた民間金融機関に成長しました。Cymbal Bank は現在、ビジネスをさらに拡大したいと考えています。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-07-10 UTC。"],[],[],null,["[Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview)\n\n*** ** * ** ***\n\nThis set of tutorials is for IT administrators and Operators who want\nto learn how to deploy, run, and manage modern application environments that run\non Google Kubernetes Engine (GKE).\n\nIn this set of tutorials, you learn by doing. You start by deploying a sample\nmicroservices-based application named Cymbal Bank to a GKE\ncluster. Cymbal Bank uses Python and Java to run the various services, and\nincludes a PostgreSQL backend. You don't need experience with these languages or\ndatabase platform to complete the series of tutorials, as Cymbal Bank is just an\nexample application to show how GKE can support the needs of your\nbusiness. Each tutorial then builds on this sample application to show how a\nreal production environment might look as you use different\nGoogle Cloud products and services to fit your business needs and\ngoals.\n\nAs you progress through this set of tutorials, you explore the following key\nlearning areas:\n\n- **Modern application foundations**: Deploy a single Google Kubernetes Engine cluster that runs a microservices-based application.\n- **Monitoring**: Use Prometheus to monitor the performance and health of your applications.\n- **Autoscale and load balance**: Scale your cluster to meet application demand with GKE Autopilot, and use horizontal Pod autoscaling.\n- **Simulate and test failovers**: Verify that your highly available and geographically distributed deployment can failover to maintain access for customers.\n- **Centralize change management**: Minimize configuration drift and apply consistent changes with Config Sync.\n\nThe tutorials are designed for you to complete in order. Each tutorial builds on\nthe previous tutorial as you create a sample application infrastructure that you\ncan monitor and autoscale. As you progress through the set of tutorials, you\nlearn new skills and use additional Google Cloud products and services.\nThe goal is that you learn all of the core components that are needed to feel\nmore comfortable running scalable applications in your own environment.\n\nYour journey\n\nFor this set of tutorials, you play the role of the platform lead at Cymbal\nBank. Cymbal Bank started as a small business for payment processing on two\nservers almost ten years ago. Since then, it has grown into a successful\ncommercial bank with thousands of employees and a growing engineering\norganization. Cymbal Bank now wants to expand its business further.\n\nThroughout this period, you and your team have found yourself spending more time\nand money on maintaining infrastructure than on creating new business value. You\nhave decades of cumulative experience invested in your existing stack; however,\nyou know it's not the right technology to meet the scale of global deployment\nthat the bank needs as it expands.\n\nYou've adopted GKE to modernize your application and\nmigrate successfully to Google Cloud to achieve your expansion goals.\n\nCosts\n\nEnabling GKE and deploying the Cymbal Bank sample application for\nthis series of tutorials means that you incur per-cluster charges for\nGKE on Google Cloud as listed on our\n[Pricing page](/kubernetes-engine/pricing)\nuntil you disable GKE or delete the project.\n\nYou are also responsible for other Google Cloud costs incurred while running the\nCymbal Bank sample application, such as charges for Compute Engine VMs and\nload balancers.\n\nBefore you begin\n\nYou don't need to be familiar with Google Kubernetes Engine or Terraform to follow these\ntutorials, but ensure that you're familiar with\n[basic Kubernetes concepts](https://kubernetes.io/docs/tutorials/kubernetes-basics/),\nsuch as clusters.\n\nEach tutorial outlines specific prerequisites, such as needing a\nGoogle Cloud billing account and project or IAM roles.\n\nPlanning considerations\n\nWhen you plan a production GKE environment, there are a number of\nplanning considerations to keep in mind. These considerations include available\nnetworking options, your cluster management mode, and cluster availability.\n\nIn this set of tutorials, some of these considerations are simplified so that\nyou can focus on learning about key GKE features and services.\nBecause of this, these tutorials don't provide a complete production-ready\nenvironment, but rather give you the building blocks you need to learn how to\ndeploy and run your own workloads. After you complete this set of tutorials, we\nrecommend you review\n[Scalable apps - Production considerations](/kubernetes-engine/docs/learn/scalable-apps-considerations).\n\nWhat's next\n\nGet started by completing the\n[first tutorial to a deploy a single GKE cluster](/kubernetes-engine/docs/learn/scalable-apps-basic-deployment)\nthat runs a microservices-based application."]]
