The three kinds of probe: Liveness, Readiness, and Startup probes

Kubernetes (since version 1.16) has three types of probe, which are used for three different purposes:

• Liveness probe. This is for detecting whether the application process has crashed/deadlocked. If a liveness probe fails, Kubernetes will stop the pod, and create a new one.
• Readiness probe. This is for detecting whether the application is ready to handle requests. If a readiness probe fails, Kubernetes will leave the pod running, but won't send any requests to the pod.
• Startup probe. This is used when the container starts up, to indicate that it's ready. Once the startup probe succeeds, Kubernetes switches to using the liveness probe to determine if the application is alive. This probe was introduced in Kubernetes version 1.16.

Source: Andrew Lock

Một số kết quả các dịch vụ hosting và in-house hosting

Benchmark script: curl -LsO bench.monster/speedtest.sh; bash speedtest.sh -asia

Cloud IOT Core là một trong những dịch vụ được cung cấp bởi Google trong nền tảng Google Cloud Platform (GCP), giúp việc kết nối, quản lý và điều khiền các thiết bị IOT một cách dễ dàng và khả năng scale lên hàng triệu thiết bị.

Tuy nhiên, ngày 16/08/2022 Google đã ra thông báo sẽ đóng dịch vụ sau ngày 15/08/2023!

Source: https://www.civo.com/learn/migrating-your-ingresses-in-k3s-1-20

Kubernetes version 1.20+ introduces the networking.k8s.io API version as stable. If you have ingresses that predate K3S 1.20, you have until Kubernetes 1.22 to update them. Until then, if you use old-style ingress definitions, you will receive a warning like Warning: networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress when you apply the ingress to a cluster.

Goolge cloud VM support connect using serial port, using in case we cannot boot VM or SSH got problem