KubeWeekly #171

KubeWeeklyは毎週Kubernetesに関する興味深いニュースを提供しています。（http://bit.ly/kubeweekly ）この記事は 2019/06/12に発行された [Kube Weekly #171]( https://mailchi.mp/cncf/kubeweekly-1465311?e=c24d137d74 ) を読んで、感じたことをメモ的にまとめたものです。
私の勘違いや説明不足による誤解もあるかと思いますので、この記事読んで「おっ」と思ったらURLを辿って本文を確認してください。

(過去のKubeWeekly読書メモは[こちら](https://qiita.com/tags/kubeweekly))

# The Headline

## Kubernetes at 5: Joe Beda, Brendan Burns, and Craig McLuckie on its past, future, and the true value of open source
<table>
<tr>
  <td colspan="2"><a href="https://www.geekwire.com/2019/kubernetes-5-joe-beda-brendan-burns-craig-mcluckie-past-future-true-value-open-source/">Kubernetes at 5: Joe Beda, Brendan Burns, and Craig McLuckie on its past, future, and the true value of open source</a></td>
</tr>
<tr>
  <td><img src="https://cdn.geekwire.com/wp-content/uploads/2019/06/20190605_Cloud_Summit_275-1260x840.jpg"></td>
  <td>At a time when open-source enterprise software is at a crossroads, wracked by debates over licensing and monetization, Kubernetes stands as an unqualified success. First released by three senior…</td>
</tr>
</table>

Kubernetesの初期開発メンバーの4人へのインタビューの書き起こし。

# The Technical

## Week Ending June 9, 2019
<table>
<tr>
  <td colspan="2"><a href="http://lwkd.info/2019/20190610">Week Ending June 9, 2019</a></td>
</tr>
<tr>
  
  <td>Developer News</td>
</tr>
</table>

Kubernetesの開発状況。もうすぐ1.15がリリースされる予定。(6/20にリリースされました！)

## Kubernetes basics: Learn how to drive first
<table>
<tr>
  <td colspan="2"><a href="https://opensource.com/article/19/6/kubernetes-basics">Kubernetes basics: Learn how to drive first</a></td>
</tr>
<tr>
  <td><img src="https://opensource.com/sites/default/files/lead-images/truck_steering_wheel_drive_car_kubernetes.jpg"></td>
  <td>Quit focusing on new projects in the Kubernetes ecosystem and get focused on driving it.</td>
</tr>
</table>

簡単なKubernetesの紹介。

## Service Mesh Interface with Lachlan Evenson
<table>
<tr>
  <td colspan="2"><a href="https://softwareengineeringdaily.com/2019/06/06/service-mesh-interface-with-lachlan-evenson/">Service Mesh Interface with Lachlan Evenson</a></td>
</tr>
<tr>
  <td><img src="https://softwareengineeringdaily.com/wp-content/uploads/2019/06/ServiceMeshInterface.png"></td>
  <td>Containers offer a lightweight abstraction for running a server. Cloud providers are able to manage billions of containers from different users, allowing for economies of scale so that each user can pay less. Today, there is a variety of ways that users can deploy containers on a cloud provider. These containers can run in managed</td>
</tr>
</table>

先日発表されたService Mesh Interface（SMI）に関するPodCast

## Linkerd and SMI
<table>
<tr>
  <td colspan="2"><a href="https://linkerd.io/2019/05/24/linkerd-and-smi/">Linkerd and SMI</a></td>
</tr>
<tr>
  <td><img src="https://linkerd.io/images/logo-only-200h.png"></td>
  <td>Earlier this week at Kubecon EU, Microsoft announced the Service Mesh Interface (SMI). SMI is a specification that exposes core service mesh features like telemetry, traffic shifting, and policy, purely via Kubernetes primitives.
The Linkerd community has been working heavily with our friends from Microsoft and Hashicorp on SMI for the past few months. In fact, the top two contributors to SMI are Linkerd’s Thomas Rampelberg and Hashicorp’s Nick Jackson—a healthy sign of serious community involvement.
</td>
</tr>
</table>

LikerdのエンジニアやHashicorpのエンジニアが協力してSMIを策定しているという話。
LinkerdもSMIのSpecに準拠して開発されているとのこと。

## Why I no longer use Terraform for Templating Kubernetes
<table>
<tr>
  <td colspan="2"><a href="https://medium.com/@stobiewankenobi/why-i-no-longer-use-terraform-for-templating-kubernetes-9aef37741447">Why I no longer use Terraform for Templating Kubernetes</a></td>
</tr>
<tr>
  <td><img src="https://cdn-images-1.medium.com/max/1200/1*_d_KxQVEDhWUhJVUPImcaA.jpeg"></td>
  <td>One of the most important principles to being an engineer, is being able to admit when you are wrong. Well folks. I was wrong. Some of you…</td>
</tr>
</table>

[前回と同じ記事](https://qiita.com/inajob/items/533100b33af906b00ae3#why-i-no-longer-use-terraform-for-templating-kubernetes)

## 10 YAML tips for people who hate YAML
<table>
<tr>
  <td colspan="2"><a href="https://www.redhat.com/sysadmin/yaml-tips">10 YAML tips for people who hate YAML</a></td>
</tr>
<tr>
  <td><img src="https://www.redhat.com/sysadmin/sites/default/files/styles/full/public/2019-06/ten-10_0.jpeg?itok=nJyqMjP-"></td>
  <td>Do you hate YAML? These tips might ease your pain.</td>
</tr>
</table>

YAML嫌いの人のための10のTips

0. エディタにYML編集用のプラグインを入れる
1. yamllint
2. いっそPythonで書いてyamlとして出力する
3. 頻繁にYAMLをパースする
4. 仕様を読む
5. 一度紙に擬似コード的に書き出してみる
6. タブ・スペースの使い方を決める
7. インデントに注意する
8. コメントとしてYAMLのテンプレートを書いておく
9. 他の形式を使う

## The Optimal Kubernetes Cluster Size? Let’s Look at the Data - The New Stack
<table>
<tr>
  <td colspan="2"><a href="https://thenewstack.io/the-optimal-kubernetes-cluster-size-lets-look-at-the-data/">The Optimal Kubernetes Cluster Size? Let’s Look at the Data - The New Stack</a></td>
</tr>
<tr>
  <td><img src="https://cdn.thenewstack.io/media/2019/06/f3a26dc8-chart-14.png"></td>
  <td>TL;DR: smaller clusters clearly win, but the why matters. As Kubernetes emerges as the de facto management platform, we are still figuring out what that means. The challenge is that it exists in a gray zone between a specialized application platform and general purpose infrastructure abstraction. I wanted to understand if one set of use-cases …</td>
</tr>
</table>

1つのクラスタの大きさはどのくらいが妥当か？というアンケートと筆者の意見をまとめている。
今の所障害の被害やアップデートの影響範囲を小さくするために小さいクラスタを構成するというのが妥当だが、将来的には大きなクラスタをnamespaceで区切るという方法も流行るだろうとのこと。

クララスタのサイズに関するアンケート結果や一言コメント集が興味深い。

## How to Deploy a Resilient Go Application to DigitalOcean Kubernetes | DigitalOcean
<table>
<tr>
  <td colspan="2"><a href="https://www.digitalocean.com/community/tutorials/how-to-deploy-resilient-go-app-digitalocean-kubernetes">How to Deploy a Resilient Go Application to DigitalOcean Kubernetes | DigitalOcean</a></td>
</tr>
<tr>
  <td><img src="https://secure.gravatar.com/avatar/e6e2a50c903777689b3047ab1a3fe6a3?secure=true&d=identicon"></td>
  <td>In this tutorial, you will build a sample Go application and get it up and running locally on your development machine. Then you'll containerize the application with Docker, deploy it to a Kubernetes cluster, and create a load balancer that will serve</td>
</tr>
</table>

シンプルなGoのWebアプリケーションを作成し、それをDockerizeし、Kubernetesにデプロイするところまでを説明したチュートリアル。

## How we built our hybrid Kubernetes platform
<table>
<tr>
  <td colspan="2"><a href="https://medium.com/dailymotion/how-we-built-our-hybrid-kubernetes-platform-d121ea9cb0bc">How we built our hybrid Kubernetes platform</a></td>
</tr>
<tr>
  <td><img src="https://cdn-images-1.medium.com/max/1200/1*KFV_OBpOQeoccRxkluVkeQ.jpeg"></td>
  <td>Dailymotion’s Kubernetes journey: a timeline of our geo-distributed infrastructure around the world mixing Cloud and on-premises clusters</td>
</tr>
</table>

DailyMotionのKubernetes事例。

まずGKEを使うようにしていったが、自社データセンター資産の活用と、クラウドプロバイダの運用コストの高さを鑑み、オンプレ環境でもKubernetesを運用するようにし、ハイブリッドクラウド構成を実現したという話。

## 70 Best Kubernetes Tutorials
<table>
<tr>
  <td colspan="2"><a href="https://www.aquasec.com/wiki/display/containers/70+Best+Kubernetes+Tutorials">70 Best Kubernetes Tutorials</a></td>
</tr>
<tr>
  <td><img src="https://www.aquasec.com/wiki/download/attachments/950296/og.png?api=v2"></td>
  <td>World"s most comprehensive compilation of resources about all aspects of container technology.</td>
</tr>
</table>

70ものKubernetesのチュートリアルの紹介。
いくつかのジャンルに分けて紹介してある。

# The Editorial

## Kubernetes Advantage: Considerations for a Multi-Cloud World - InformationWeek
<table>
<tr>
  <td colspan="2"><a href="https://www.informationweek.com/kubernetes-advantage-considerations-for-a-multi-cloud-world/a/d-id/1334879">Kubernetes Advantage: Considerations for a Multi-Cloud World - InformationWeek</a></td>
</tr>
<tr>
  <td><img src="https://img.deusm.com/informationweek/Kip_Compton-Cisco.jpg"></td>
  <td>As more IT leaders deploy Kubernetes into mainstream production environments, the ecosystem around Kubernetes will grow and drive innovation.</td>
</tr>
</table>

マルチクラウド環境において考えるべきこと。

- マイクロサービス化など新しいアプローチが必要となる
- ネットワークセキュリティについてよく考える必要がある
- DevOps的な考え方がますます重要となる


## Researchers Find 40,000+ Exposed Containers Online
<table>
<tr>
  <td colspan="2"><a href="https://www.infosecurity-magazine.com:443/news/researchers-find-40000-containers-1/">Researchers Find 40,000+ Exposed Containers Online</a></td>
</tr>
<tr>
  <td><img src="https://assets.infosecurity-magazine.com/webpage/og/6b3d028b-b6db-4cc4-9549-c0f70953a622.jpg"></td>
  <td>Misconfigurations create extra security risk, warns Palo Alto Networks</td>
</tr>
</table>

4万以上のKubernetesクラスタやDockerの入ったホストが誤った設定でインターネットに晒されているという調査報告。

## How One of The Netherlands’ Largest Banks Came to CI/CD - The New Stack
<table>
<tr>
  <td colspan="2"><a href="https://thenewstack.io/how-one-of-the-netherlands-largest-banks-came-to-ci-cd/">How One of The Netherlands’ Largest Banks Came to CI/CD - The New Stack</a></td>
</tr>
<tr>
  <td><img src="https://cdn.thenewstack.io/media/2019/06/6b7b567f-abm-02.jpg"></td>
  <td>In this edition of The New Stack Makers podcast recorded during the KubeCon + CloudNativeCon conference held in Barcelona at the end of May, we are joined by ABN's Wiebe de Roos and Dominik de Smit to discuss CI/CD and DevOps.</td>
</tr>
</table>

とあるオランダの銀行でCI/CDを導入した話。
（PodCast）

## Why containers and Kubernetes have the potential to run almost anything
<table>
<tr>
  <td colspan="2"><a href="https://opensource.com/article/19/6/kubernetes-potential-run-anything">Why containers and Kubernetes have the potential to run almost anything</a></td>
</tr>
<tr>
  <td><img src="https://opensource.com/sites/default/files/lead-images/fail_progress_cycle_momentum_arrow.png"></td>
  <td>Go beyond deployment of simple applications and tackle day two operations with Kubernetes Operators.</td>
</tr>
</table>

Operatorなどの発達により、単純ではないアプリケーションもKubernetes上で動かせるようになってきていて、Kubernetesの将来は明るいよ！という話。

## IBM Open Sources Razee, a Pull-Based Kubernetes Continuous Delivery Tool - The New Stack
<table>
<tr>
  <td colspan="2"><a href="https://thenewstack.io/ibm-open-sources-razee-a-pull-based-kubernetes-continuous-delivery-tool/">IBM Open Sources Razee, a Pull-Based Kubernetes Continuous Delivery Tool - The New Stack</a></td>
</tr>
<tr>
  <td><img src="https://cdn.thenewstack.io/media/2019/06/1392d76f-boat-ocean-people-33689.jpg"></td>
  <td>When IBM set out to build its IBM Kubernetes Service (IKS) a couple years back, it found that it was lacking on primary component — a continuous delivery system that could provide the scale, speed and visibility needed for what it was doing. As Daniel Berg, an IBM distinguished engineer with IBM Cloud and Istio, explained in an interview with The New Stack, the team found itself in a conundrum that would only be solved by building its own continuous delivery (CD) software. IBM has open sourced the project, now called Razee, during last month's KubeCon + CloudNativeCon in Barcelona.</td>
</tr>
</table>

IBMが先日オープンソースにしたCDツールである [Razee](https://razee.io/)に関するインタビュー記事。
Pull型であることを特徴としており、これにより多数のデプロイを扱い際の負荷を減らしているようだ。

## Container & Cloud Native Security: Sharing 3 Years of Experience

動画ファイルが直リンクしていたが、おそらくこのWebinarか？

https://info.aquasec.com/cloud-native-security-deployments
（みていない）