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容器服務(AKS)和Amazon的彈性容器服務(EKS)也應該包括在內,以便我們可以擁有提供托管Kubernetes的主機供應商的“三巨頭”。不幸的是,在撰寫本文時(2018年5月),彈性容器服務(EKS)處於預覽階段,Amazon只向相對少數的人提供訪問權限。另一方面,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和OpenShift(帶有minishift)以及EKS上進行測試。