The DevOps 2.4 Toolkit
暫譯: DevOps 2.4 工具包

Farcic, Viktor

  • 出版商: Packt Publishing
  • 出版日期: 2019-11-28
  • 定價: $1,600
  • 售價: 6.0$960
  • 語言: 英文
  • 頁數: 398
  • 裝訂: Quality Paper - also called trade paper
  • ISBN: 1838643540
  • ISBN-13: 9781838643546
  • 相關分類: DevOps
  • 立即出貨 (庫存=1)

相關主題

商品描述

Just like other books I wrote, this one did not have a fixed scope. I did not start with an index. I didn't write a summary of each chapter in an attempt to define the scope. I do not do such things. There was only a high-level goal to explore continuous delivery and deployment inside Kubernetes clusters. What I did do, though, was to set a few guidelines.The first guideline is that "all the examples will be tested on all major Kubernetes platforms." Well, that might be a bit far-fetched. I'm aware that any sentence that mentions "all" together with "Kubernetes" is bound to be incorrect. New platforms are popping out like mushrooms after rain. Still, what I can certainly do is to choose a few of the most commonly used ones.Minikube and Docker for Mac or Windows should undoubtedly be there for those who prefer to "play" with Docker locally.AWS is the biggest hosting provider so Kubernetes Operations (kops) must be included as well.Since it would be silly to cover only un-managed cloud, I had to include managed Kubernetes clusters as well. Google Kubernetes Engine (GKE) is the obvious choice. It is the most stable and features rich managed Kubernetes solution. Adding GKE to the mix means that Azure Container Service (AKS) and Amazon's Elastic Container Service (EKS) should be included as well so that we can have the "big trio" of the hosting vendors that offer managed Kubernetes. Unfortunately, at the time of this writing (May 2018), Elastic Container Service (EKS) is in the preview stage and Amazon is providing access only to a relatively small number of people. AKS, on the other hand, is available but, at this moment, it is too unstable. So, I'm forced to scale down from the trio to GKE as the only managed Kubernetes we'll explore.Finally, a possible on-prem solution should be included as well. Since OpenShift shines in that area, the choice was relatively easy.All in all, I decided to test everything in minikube and Docker for Mac locally, AWS with kops as the representative of a cluster in the cloud, GKE for managed Kubernetes clusters, and OpenShift (with minishift) as a potential on-prem solution. That, in itself, already constitutes a real challenge that might prove to be more than I can chew. Still, making sure that all the examples work with all those platforms and solutions should provide some useful insights.Some of you already chose the Kubernetes flavor you'll use. Others might still wonder whether to adopt one or the other. Even though the comparison of different Kubernetes platforms is not the primary scope of the book, I'll do my best to explain the differences as they come.To summarize the guidelines, the book has to explore continuous delivery and deployment in Kubernetes using Jenkins. All the examples have to be tested in minikube, Docker for Mac (or Windows), AWS with kops, GKE, and OpenShift with minishift, and EKS.

商品描述(中文翻譯)

就像我寫的其他書籍一樣,這本書並沒有固定的範圍。我沒有從索引開始,也沒有為每一章寫摘要以試圖定義範圍。我不會做這些事情。唯一的高層次目標是探索在 Kubernetes 叢集中的持續交付和部署。不過,我確實設置了一些指導方針。第一個指導方針是「所有的範例都將在所有主要的 Kubernetes 平台上進行測試。」這聽起來可能有點不切實際。我知道任何提到「所有」和「Kubernetes」的句子都注定是不正確的。新的平台如雨後春筍般湧現。不過,我可以肯定的是,我會選擇一些最常用的平台。對於那些喜歡在本地「玩」 Docker 的人來說,Minikube 和 Docker for Mac 或 Windows 無疑是必須的。AWS 是最大的託管提供商,因此 Kubernetes Operations (kops) 也必須包括在內。由於僅涵蓋未管理的雲端會顯得愚蠢,我還必須包括受管理的 Kubernetes 叢集。Google Kubernetes Engine (GKE) 是明顯的選擇。它是最穩定且功能豐富的受管理 Kubernetes 解決方案。將 GKE 加入混合意味著 Azure Container Service (AKS) 和亞馬遜的 Elastic Container Service (EKS) 也應該包括在內,這樣我們就可以擁有提供受管理 Kubernetes 的「大三」託管供應商。不幸的是,在撰寫本文時(2018 年 5 月),Elastic Container Service (EKS) 正處於預覽階段,亞馬遜僅向相對少數人提供訪問權限。另一方面,AKS 雖然可用,但此時仍然不夠穩定。因此,我被迫從三者中縮減到僅探索 GKE 作為唯一的受管理 Kubernetes。最後,還應包括一個可能的本地解決方案。由於 OpenShift 在這方面表現出色,因此選擇相對容易。總的來說,我決定在本地的 minikube 和 Docker for Mac 中測試所有內容,使用 kops 的 AWS 作為雲端叢集的代表,GKE 作為受管理的 Kubernetes 叢集,以及 OpenShift(搭配 minishift)作為潛在的本地解決方案。這本身已經構成了一個真正的挑戰,可能超出我的能力範圍。不過,確保所有範例都能在這些平台和解決方案上運行,應該能提供一些有用的見解。你們中的一些人已經選擇了將要使用的 Kubernetes 版本。其他人可能仍在考慮是否採用其中一種。儘管不同 Kubernetes 平台的比較不是本書的主要範圍,但我會盡力在出現時解釋它們之間的差異。總結一下指導方針,本書必須探索在 Kubernetes 中使用 Jenkins 的持續交付和部署。所有範例必須在 minikube、Docker for Mac(或 Windows)、使用 kops 的 AWS、GKE 和搭配 minishift 的 OpenShift 以及 EKS 中進行測試。