Difference between kubernetes metrics "/metrics/resource/v1alpha1" and "/metrics/cadvisor" endpoints
kubectl execã¯ç¦æ¢!? kubectl debugã®å‹§ã‚ | IIJ Engineers Blog
社会人生活ã®åŠåˆ†ã‚’フリーランスã€åŠåˆ†ã‚’IIJã§éŽã”ã™ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã€‚元々ã¯ã‚¢ãƒ—リケーション屋ã ã£ãŸã¯ãšãŒã€ã‚¯ãƒ©ã‚¦ãƒ‰ã¨å‡ºä¼šã£ãŸã°ã‹ã‚Šã«åŠèº«ã‚’インフラ屋ã«å£²ã‚Šæ¸¡ã™ç¾½ç›®ã«ã€‚ç¾åœ¨ã¯ã‚³ãƒ³ãƒ†ãƒŠæŠ€è¡“ã«å‚¾å€’ä¸ã ãŒèªžã‚Šã ã™ã¨é•·ã„ã®ã§å‰²æ„›ã€‚ã‚¿ã‚°ã‚’ã¤ã‘ã‚‹ãªã‚‰ã‚³ãƒ³ãƒ†ãƒŠã€ã‚¯ãƒ©ã‚¦ãƒ‰ã€ãƒãƒ¼ãƒ‰ãƒã‚¤ã‚¯ã€ã†ã©ã‚“。 Kubernetes 1.23ã‹ã‚‰æ¨™æº–ã§åˆ©ç”¨ã§ãるよã†ã«ãªã£ãŸã‚¨ãƒ•ã‚§ãƒ¡ãƒ©ãƒ«ã‚³ãƒ³ãƒ†ãƒŠï¼ˆEphemeral Container）をã”å˜ã˜ã§ã™ã‹ï¼Ÿ ã‚»ã‚ュアã«Kubernetesã‚’é‹ç”¨ã—ã¦ã„ãã«ã¯å¿…é ˆã®æ©Ÿèƒ½ã«ãªã‚‹ã“ã¨ã¯é–“é•ã„ãªãã€IKE（IIJ Kubernetes Engine）ã§ã¯æ—©é€Ÿæ´»ç”¨ãŒå§‹ã¾ã£ã¦ã„ã¾ã™ã€‚実利用ã«è€ãˆã‚‹ç’°å¢ƒãŒæ•´ã†ã«ã¯ã¾ã å°‘ã—時間ãŒã‹ã‹ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“ãŒã€ä»Šã®ã†ã¡ã‹ã‚‰ä½¿ã„ã“ãªã›ã‚‹ã‚ˆã†ã«ç´¹ä»‹ã—ã¾ã™ã€‚ エフェメラルコンテナ 一般的ã«ã¯èžããªã‚Œãªã„ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“ãŒã€IaaSを使ã£ã¦ã„ã‚Œã°ã‚¨ãƒ•ã‚§ãƒ¡ãƒ©ãƒ«ï¼ˆEphem
Dockerã¨Podmanã®æ¯”較 [Container Runtime Meetup #3]
Container Runtime Meetup #3 発表資料 「Dockerã¨Podmanã®æ¯”較ã€Podmanã¨ã¯Podmanã¯ã€Red Hat社をä¸å¿ƒã¨ã™ã‚‹ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãŒé–‹ç™ºã—ã¦ã„ã‚‹ã€Docker互æ›ã®ã‚³ãƒ³ãƒ†ãƒŠã‚¨ãƒ³ã‚¸ãƒ³ã§ã™ã€‚RHELã€CentOSã€Fedora ãªã©ã® Linuxディストリビューションã«æ¨™æº–ã§ä»˜å±žã—ã¦ã„ã¾ã™ã€‚ Podmanã®ä½¿ã„æ–¹ã¯ã€ã‚³ãƒžãƒ³ãƒ‰å㌠docker ã§ã¯ãªã podman ã§ã‚る点を除ã‘ã°ã€Docker ã¨ã»ã¼åŒã˜ã§ã™ã€‚(例: podman run -p 80:80 --name nginx docker.io/library/nginx ) “Podmanâ€ã¯ “Pod Manager†をæ„味ã—ã¾ã™ãŒã€Podmanを用ã„ã¦Kubernetesã®Podを管ç†ã™ã‚‹ã“ã¨ã¯ã€åŸºæœ¬çš„ã«ã¯ã§ãã¾ã›ã‚“。ãŸã ã—ã€CRIランタイムã¨ã—ã¦CRI-Oを用ã„ã¦ã„ã‚‹å ´åˆã«é™ã‚Šã€
![Dockerã¨Podmanã®æ¯”較 [Container Runtime Meetup #3]](https://cdn-ak-scissors.b.st-hatena.com/image/square/95dd437ee47af8a6787c1a615e75b7d301b636ba/height=288;version=1;width=512/https%3A%2F%2Fmiro.medium.com%2Fv2%2Fresize%3Afit%3A640%2F1%2AVD87-YoAC4PnLKoVHhC6iA.png)
kubernetesソースコードリーディング 第4回 - APC 技術ブãƒã‚°
今回ã¯ã¡ã‚‡ã£ã¨è¶£å‘を変ãˆã¦ã€ãƒ†ãƒ¼ãƒžã¯Dockerã§ã™ï¼ kubernetesã®ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã‹ã‚‰ã¯å°‘々離れã¦ã—ã¾ã„ã¾ã™ãŒã€ コンテナランタイムもkubernetesã®é‡è¦ãªã‚³ãƒ³ãƒãƒ¼ãƒãƒ³ãƒˆã®ï¼‘ã¤ãªã®ã§çŸ¥ã£ã¦ãŠã„ã¦æã¯ãªã„ã¯ãšâ€¦ï¼ アジェンダã¯ä»¥ä¸‹ã«ãªã‚Šã¾ã™ã€‚ コンテナ仮想化技術ã®æ´å²ã¨dockerã®ç‰¹å¾´ コンテナ仮想化技術ã®æ´å² “コンテナ仮想化技術â€ã¨ã¯ä½•ã‹ï¼Ÿ 隔離(isolation)ã¨ã¯ï¼Ÿ コンテナã¨ã—ã¦ã®dockerã®ç‰¹å¾´ ホストOSã®ã‚«ãƒ¼ãƒãƒ«ã‚’共有 å¯æ¬æ€§ã®ã‚ã‚‹imageã¨container registry Dockerã®æ´å²ã¨ã‚³ãƒ³ãƒ†ãƒŠãƒ©ãƒ³ã‚¿ã‚¤ãƒ dockerd OCI containerd runc dockerã‚’é‹ç”¨ã™ã‚‹ãŸã‚ã®ãƒ„ールãŸã¡ systemd-cgtop dockerpsns.sh perf event docker stats / ctop csysdig bpft
Secure your K8s cluster from multi-layers
The document discusses securing a Kubernetes cluster from multiple layers of risk. It covers securing the infrastructure layer by limiting access and exposure, the control plane layer by enabling TLS and RBAC, the workload layer using pod security policies and network policies, the container runtime layer with tools like Kata Containers, the user misconfiguration layer by avoiding defaults and val
コンテナ未経験新人ãŒå¦ã¶ã‚³ãƒ³ãƒ†ãƒŠæŠ€è¡“入門
最近勉強を始ã‚ãŸã‚³ãƒ³ãƒ†ãƒŠæŠ€è¡“ã«é–¢ã™ã‚‹åŸºç¤Žçš„ãªçŸ¥è˜ã‚’ã¾ã¨ã‚ã¾ã—ãŸã€‚ [訂æ£ã¨æ³¨é‡ˆ] p.27-30: 「Deploymentã€å†…ã®ã€ŒVersion: 1〠=> 「Version: 2〠p.37: 「終了コードをã‹ã‚‰ã€ => 「終了コードã‹ã‚‰ã€ p.39: 「HTTPSãŒåˆ©ç”¨ã§ããªã„ã€=> AWS上ã§ã¯ã€SSL終端ã™ã‚‹LBãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã¾ã™ã€‚https://kubernetes.io/docs/concepts/services-networking/service/#ssl-support-on-aws p.40: 「ユーザãŒingress controllerã‚’master上ã«ã‚»ãƒƒãƒˆã‚¢ãƒƒãƒ—ã™ã‚‹å¿…è¦ã€ => master上ã«ã‚»ãƒƒãƒˆã‚¢ãƒƒãƒ—ã—ãªã‘ã‚Œã°ãªã‚‰ãªã„ã¨ã„ã†åˆ¶ç´„ã¯ã‚ã‚Šã¾ã›ã‚“。例ãˆã°GCEã®ingress controller(GLBC)ã¯Podã¨ã—ã¦å‹•ä½œã—ã¾ã™ã€‚https://gi
Kubernetesã§å®Ÿéš›ã®ãƒ¡ãƒ¢ãƒªã‚’超ãˆã‚‹ã‚³ãƒ³ãƒ†ãƒŠã‚¢ãƒ—リを動ã‹ã™ã¨ã€ã©ã†ãªã‚‹ã‹ï¼Ÿ - ã‚ã•ã®ã²ã¨ã‚Šã”ã¨
Kubernetesã¯ã€ã‚³ãƒ³ãƒ†ãƒŠã‚¢ãƒ—リケーションをデプãƒã‚¤ã™ã‚‹ãŸã‚ã®ã‚ªãƒ¼ã‚±ã‚¹ãƒˆãƒ¬ãƒ¼ã‚·ãƒ§ãƒ³ãƒ„ールã§ã™ã€‚Kuberenetesã¯åˆ†æ•£ç’°å¢ƒã«ãŠã‘るスケーラブルãªã‚³ãƒ³ãƒ†ãƒŠå®Ÿè¡Œç’°å¢ƒã‚’ã¤ãã‚‹ãŸã‚ã®ã€ã•ã¾ã–ã¾ãªæ©Ÿèƒ½ãŒæä¾›ã•ã‚Œã¦ã„ã¾ã™ã€‚ ã‚‚ã¨ã‚‚ã¨ã¯GoogleãŒé–‹ç™ºã—ãŸBorgã‚’ã‚‚ã¨ã«OSS化ã—ãŸã‚‚ã®ã§ã™ãŒã€ä»Šæ—¥ã§ã¯ãƒžã‚¤ã‚¯ãƒã‚½ãƒ•ãƒˆã‚„（ry Kubernetesã‚’ã¤ã‹ã†ã¨ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¬ã‚¹ã§ãƒžã‚¤ã‚¯ãƒã‚µãƒ¼ãƒ“ス的ãªã‚¢ãƒ—リケーションを1æ—¥ã«ä½•åº¦ã‚‚デプãƒã‚¤ã§ãã€ã‚¹ãƒ‘イクアクセスãŒãã¦ã‚‚水平スケールãŒå®¹æ˜“ãªã®ã§ã€å¤§è¦æ¨¡Webシステムã§ã‚¹ã‚±ãƒ¼ãƒ©ãƒ–ルãªåŸºç›¤ã‚’作れるã€ã¨ã„ã†ã®ã¯åºƒã知られã¦ã„ã¾ã™ã€‚ 一方ã€Kubernetesã«ã¯ã€ŒResource Requestsã€ã¨ã„ã†æ©Ÿèƒ½ãŒã‚ã‚Šã€ã“ã‚Œã¯Podをデプãƒã‚¤ã™ã‚‹æ™‚ã«å¿…è¦ã¨ã™ã‚‹ãƒªã‚½ãƒ¼ã‚¹(CPU/メモリ)を指定ã§ãã‚‹ã‚‚ã®ã§ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€Kubernetesクラスタã®ãƒªã‚½ãƒ¼ã‚¹ã®ä½¿ç”¨çŽ‡ã‚’
Container Design Patterns
This article is more than one year old. Older articles may contain outdated content. Check that the information in the page has not become incorrect since its publication. Kubernetes automates deployment, operations, and scaling of applications, but our goals in the Kubernetes project extend beyond system management -- we want Kubernetes to help developers, too. Kubernetes should make it easy for
Slimming down Docker containers - Intercity
Dockers containers built with a Dockerfile can get quite large. We slim down our containers by these simple tricks before publishing. Cleaning APT The obvious apt-clean for cleaning out the apt-cache and cleaning out tmp. RUN apt-get clean RUN rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* Flatten an image A Dockerfile builds your container in many individual steps. Resulting in a container with so
1
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
CNCF Landscape
{{#tags}}- {{label}}
{{/tags}}