If you've ever wanted to run a web server, an API gateway, an Ingress controller, a Kafka proxy, a service that has a binary protocol like an MQTT service or database, or essentially anything that runs on TCP (or UDP), you can now run it in IBM Cloud Kubernetes Service on a host name.
We are excited to introduce the IBM Cloud Kubernetes Service Diagnostics and Debug Tool (Beta)—a tool that customers can run in order to collect information and identify potential issues with their IBM Cloud-managed Kubernetes cluster.
In keeping with our goal to provide you with a robust, trusted platform for your applications, and to comply with the PCI Security Standards Council mandate, the Ingress controller will have TLS 1.0 and 1.1 disabled by default in the upcoming version upgrade of the IBM Cloud Kubernetes Service ALB.
In the IBM Cloud Kubernetes Service, the Calico configuration file can now be generated automatically with just a single command. For clusters 1.10 and above, you can use the new flag to download your cluster config.
Effective immediately, IBM Cloud Kubernetes Service customers can gain control over when the IBM Cloud Kubernetes Service ALB pods are updated in their clusters. The default setting for each newly created cluster remains—the Ingress controller will get updated automatically by IBM Cloud Kubernetes Service whenever a new version is available.
IBM Cloud Kubernetes Service Deployment Patterns #3: Multi-Zone Cluster, LoadBalancer with In-Zone Backends Only
Learn how to deploy an IBM Cloud Kubernetes Service multi-zone cluster by keeping the destination endpoints of the application where the NLB sends the requests to within the same zone.
IBM Cloud Kubernetes Service Deployment Patterns #4: Multi-Zone Cluster, LoadBalancer Aggregating Whole Region Capacity
Learn how to deploy an IBM Cloud Kubernetes Service multi-zone cluster by aggregating the capacity of the whole region by allowing the NLBs to distribute traffic to all zones within the region.
Learn how to deploy an IBM Cloud Kubernetes Service multi-zone cluster with the app exposed via ALB/Ingress controller.
When considering Kubernetes cluster deployment patterns, the simplest pattern is deploying an IBM Cloud Kubernetes Service cluster in a single zone within a region, and we'll go into more detail on this option here.