Containers and Environment Variables

My previous article “Inotify in Containers” has demonstrated that when ConfigMap is mounted as directories, any changes in the ConfigMap will propagate to related pods. A follow-up question might be: what if the ConfigMap is mounted as environment variables? Some said that the answer is NO in Kubernetes1; even in the old Docker world2. Therefore, I’d like to begin with a simple experiment to try to answer the question: After

Inotify in Containers

It is usually necessary to watch for any changes in file systems, both in development and in production modes. For example, in the development mode Webpack can watch files and recompile whenever they change; in the production mode Consul Template can watch runtime configs and invoke specific applications whenever they change. These are well-known scenarios in traditional pre-container world. How about the container world? Do they behave the same in

Next '19 的 Istio 場次重點摘要

四月 9–11 日去舊金山參加 Google Cloud 的 Next ’19 大會,收穫頗大。

這場大會,同一時段就有近 30 場專題演講同時進行,議程滿滿,勢必得做取捨。基於工作需要及個人興趣,我主要選擇與容器相關的場次:service mesh、Windows containers、混合雲、資安實務。

我發現,光是這些場次,就得花很大力氣去消化、實驗與應用。

我們這些所謂的「台港團」會在 GCPUG Taipei 舉辦一場分享會。因為自己不克參加,便以這篇文章,針對我鎖定的核心議題:Istio,做一番重點摘要,以饗讀者。

在 WSL 裡使用 Ansible + Vagrant

既然要開始在 Windows 上沿用 Mac 及 Unix 的命令列工具習慣1,免不了要處理 AnsibleVagrant

雖然這兩個軟體都有對應的 Windows 版本,但據我以前的經驗,卡卡的,有許多小地雷;畢竟這些發跡自泛 Unix 家族的軟體,不是那麼容易無縫移植到對命令列不友善的 Windows 家族。

如今 Windows 已經有 WSL (Windows Subsystem for Linux) 機制,是否可以更無痛享用 Ansible 及 Vagrant 呢?

可以的。