| copyright | lastupdated | ||
|---|---|---|---|
|
2018-11-13 |
{:new_window: target="_blank"} {:shortdesc: .shortdesc} {:screen: .screen} {:pre: .pre} {:table: .aria-labeledby="caption"} {:codeblock: .codeblock} {:tip: .tip} {:note: .note} {:important: .important} {:deprecated: .deprecated} {:download: .download}
{: #cs_popular_topics}
Keep up with what's going on in {{site.data.keyword.containerlong}}. Learn about new features to explore, a trick to try out, or some popular topics that other developers are finding useful in the now. {:shortdesc}
{: #nov18}
| Date | Title | Description |
|---|---|---|
| 7 November | Load balancer 2.0 (beta) | You now can choose between [load balancer 1.0 or 2.0](cs_loadbalancer.html#planning_ipvs) to securely expose your cluster apps to the public. |
| 7 November | Kubernetes version 1.12 available | Now, you can update or create clusters that run [Kubernetes version 1.12](cs_versions.html#cs_v112)! 1.12 clusters come with highly available Kubernetes masters by default. |
| 7 November | Highly available masters in clusters that run Kubernetes version 1.10 | Highly available masters are available for clusters that run Kubernetes version 1.10! All the benefits described in the earlier entry for 1.11 clusters apply to 1.10 clusters, as well as the [preparation steps](cs_versions.html#110_ha-masters) that you must take. |
| 1 November | Highly available masters in clusters that run Kubernetes version 1.11 | In a single zone, your master is highly available and includes replicas on separate physical hosts for your Kubernetes API server, etcd, scheduler, and controller manager to protect against an outage such as during a cluster update. If your cluster is in a multizone-capable zone, your highly available master is also spread across zones to help protect against a zonal failure. For actions that you must take, see [Updating to highly available cluster masters](cs_versions.html#ha-masters). These preparation actions apply:
|
{: #oct18}
| Date | Title | Description |
|---|---|---|
| 25 October | [Zone available in Milan](cs_regions.html) | Welcome Milan, Italy as a new zone for paid clusters in the EU Central region. Previously, Milan was available only for free clusters. If you have a firewall, be sure to [open the firewall ports](cs_firewall.html#firewall) for this zone and the other zones within the region that your cluster is in. |
| 22 October | [New London multizone location, `lon05`](cs_regions.html#zones) | The London multizone metro city replaces `lon02` zone with the new `lon05` zone, a zone with more infrastructure resources than `lon02`. Create new multizone clusters with `lon05`. Existing clusters with `lon02` are supported, but new multizone clusters must use `lon05` instead. |
| 05 October | Integration with {{site.data.keyword.keymanagementservicefull}} | You can encrypt the Kubernetes secrets in your cluster by [enabling {{site.data.keyword.keymanagementserviceshort}} (beta)](cs_encrypt.html#keyprotect). |
| 04 October | [{{site.data.keyword.registrylong}} is now integrated with {{site.data.keyword.Bluemix_notm}} Identity and Access Management (IAM)](/docs/services/Registry/iam.html#iam) | You can use {{site.data.keyword.Bluemix_notm}} IAM to control access to your registry resources, such as pulling, pushing, and building images. When you create a cluster, you also create a registry token so that the cluster can work with your registry. Therefore, you need the registry **Administrator** platform management role to create a cluster. To enable {{site.data.keyword.Bluemix_notm}} IAM for your registry account, see [Enabling policy enforcement for existing users](/docs/services/Registry/registry_users.html#existing_users). |
| 01 October | [Resource groups](cs_users.html#resource_groups) | You can use resource groups to separate your {{site.data.keyword.Bluemix_notm}} resources into pipelines, departments, or other groupings to help assign access and meter usage. Now, {{site.data.keyword.containerlong_notm}} supports creating clusters in the `default` group or any other resource group that you create! |
{: #sept18}
| Date | Title | Description |
|---|---|---|
| 25 September | [New zones available](cs_regions.html) | Now you have even more options of where to deploy your apps!
|
| 05 September | [Zone available in Oslo](cs_regions.html) | Welcome Oslo, Norway as a new zone in the EU Central region. If you have a firewall, be sure to [open the firewall ports](cs_firewall.html#firewall) for this zone and the others within the region that your cluster is in. |
{: #aug18}
| Date | Title | Description |
|---|---|---|
| 31 August | {{site.data.keyword.cos_full_notm}} is now integrated with {{site.data.keyword.containerlong}} | Use Kubernetes-native persistent volume claims (PVC) to provision {{site.data.keyword.cos_full_notm}} to your cluster. {{site.data.keyword.cos_full_notm}} is best used for read-intensive workloads and if you want to store data across multiple zones in a multizone cluster. Start by [creating an {{site.data.keyword.cos_full_notm}} service instance](cs_storage_cos.html#create_cos_service) and [installing the {{site.data.keyword.cos_full_notm}} plug-in](cs_storage_cos.html#install_cos) on your cluster. Not sure what storage solution might be the right one for you? Start [here](cs_storage_planning.html#choose_storage_solution) to analyze your data and choose the appropriate storage solution for your data. |
| 14 August | Update your clusters to Kubernetes versions 1.11 to assign pod priority | After you update your cluster to [Kubernetes version 1.11](cs_versions.html#cs_v111), you can take advantage of new capabilities, such as increased container runtime performance with `containerd` or [assigning pod priority](cs_pod_priority.html#pod_priority). |
{: #july18}
| Date | Title | Description |
|---|---|---|
| 30 July | [Bring your own Ingress controller](cs_ingress.html#user_managed) | Do you have very specific security or other custom requirements for your cluster's Ingress controller? If so, you might want to run your own Ingress controller instead of the default. |
| 10 July | Introducing multizone clusters | Want to improve cluster availability? Now you can span your cluster across multiple zones in select metro areas. For more information, see [Creating multizone clusters in {{site.data.keyword.containerlong_notm}}](cs_clusters_planning.html#multizone). |
{: #june18}
| Date | Title | Description |
|---|---|---|
| 13 June | The `bx` CLI command name is changing to `ic` CLI | When you download the latest version of the {{site.data.keyword.Bluemix_notm}} CLI, you now run commands by using the `ic` prefix instead of `bx`. For example, list your clusters by running `ibmcloud ks clusters`. |
| 12 June | [Pod security policies](cs_psp.html) | For clusters that run Kubernetes 1.10.3 or later, you can configure pod security policies to authorize who can create and update pods in {{site.data.keyword.containerlong_notm}}. |
| 06 June | [TLS support for the IBM-provided Ingress wildcard subdomain](cs_ingress.html#wildcard_tls) | For clusters created on or after 6 June 2018, the IBM-provided Ingress subdomain TLS certificate is now a wildcard certificate and can be used for the registered wildcard subdomain. For clusters created before 6 June 2018, TLS certificate will be updated to a wildcard certificate when the current TLS certificate is renewed. |
{: #may18}
| Date | Title | Description |
|---|---|---|
| 24 May | [New Ingress subdomain format](cs_ingress.html) | Clusters created after 24 May are assigned an Ingress subdomain in a new format: <cluster_name>.<region>.containers.appdomain.cloud. When you use Ingress to expose your apps, you can use the new subdomain to access your apps from the internet. |
| 14 May | [Update: Deploy workloads on GPU bare metal worldwide](cs_app.html#gpu_app) | If you have a [bare metal graphics processing unit (GPU) machine type](cs_clusters_planning.html#shared_dedicated_node) in your cluster, you can schedule mathematically intensive apps. The GPU worker node can process your app's workload across both the CPU and GPU to increase performance. |
| 03 May | [Container Image Security Enforcement (beta)](/docs/services/Registry/registry_security_enforce.html#security_enforce) | Does your team need a little extra help to know which image to pull in your app containers? Try out the Container Image Security Enforcement beta to verify container images before you deploy them. Available for clusters that run Kubernetes 1.9 or later. |
| 01 May | [Deploy the Kubernetes dashboard from the console](cs_app.html#cli_dashboard) | Did you ever want to access the Kubernetes dashboard with one click? Check out the **Kubernetes Dashboard** button in the {{site.data.keyword.Bluemix_notm}} console. |
{: #apr18}
| Date | Title | Description |
|---|---|---|
| 17 April | {{site.data.keyword.Bluemix_notm}} Block Storage | Install the {{site.data.keyword.Bluemix_notm}} Block Storage [plug-in](cs_storage_block.html#install_block) to save persistent data in block storage. Then, you can [create new](cs_storage_block.html#add_block) or [use existing](cs_storage_block.html#existing_block) block storage for your cluster. |
| 13 April | [New tutorial to migrate Cloud Foundry apps to clusters](cs_tutorials_cf.html#cf_tutorial) | Do you have a Cloud Foundry app? Learn how to deploy the same code from that app to a container that runs in a Kubernetes cluster. |
| 05 April | [Filtering logs](cs_health.html#filter-logs) | Filter out specific logs from being forwarded. Logs can be filtered out for a specific namespace, container name, log level, and message string. |
{: #mar18}
| Date | Title | Description |
|---|---|---|
| 16 March | [Provision a bare metal cluster with Trusted Compute](cs_clusters_planning.html#shared_dedicated_node) | Create a bare metal cluster that runs [Kubernetes version 1.9](cs_versions.html#cs_v19) or later, and enable Trusted Compute to verify your worker nodes against tampering. |
| 14 March | [Secure sign-in with {{site.data.keyword.appid_full}}](cs_integrations.html#appid) | Enhance your apps that are running in {{site.data.keyword.containerlong_notm}} by requiring users to sign in. |
| 13 March | [Zone available in São Paulo](cs_regions.html) | Welcome São Paulo, Brazil as a new zone in the US South region. If you have a firewall, be sure to [open the firewall ports](cs_firewall.html#firewall) for this zone and the others within the region that your cluster is in. |
| 12 March | [Just joined the {{site.data.keyword.Bluemix_notm}} with a Trial account? Try out a free Kubernetes cluster!](container_index.html#clusters) | With a Trial [{{site.data.keyword.Bluemix_notm}} account](https://console.bluemix.net/registration/), you can deploy one free cluster for 30 days to test out Kubernetes capabilities. |
{: #feb18}
| Date | Title | Description |
|---|---|---|
| 27 February | Hardware virtual machine (HVM) images for worker nodes | Increase the I/O performance of your workloads with HVM images. Activate on each existing worker node by using the `ibmcloud ks worker-reload` [command](cs_cli_reference.html#cs_worker_reload) or the `ibmcloud ks worker-update` [command](cs_cli_reference.html#cs_worker_update). |
| 26 February | [KubeDNS autoscaling](https://kubernetes.io/docs/tasks/administer-cluster/dns-horizontal-autoscaling/) | KubeDNS now scales with your cluster as it grows. You can adjust the scaling rations by using the following command: `kubectl -n kube-system edit cm kube-dns-autoscaler`. |
| 23 February | View the web console for [logging](cs_health.html#view_logs) and [metrics](cs_health.html#view_metrics) | Easily view log and metric data on your cluster and its components with an improved web UI. See your cluster detail page for access. |
| 20 February | Encrypted images and [signed, trusted content](../services/Registry/registry_trusted_content.html#registry_trustedcontent) | In {{site.data.keyword.registryshort_notm}}, you can sign and encrypt images to ensure their integrity when you store the images in your registry namespace. Run your container instances by using only trusted content. |
| 19 February | [Set up the strongSwan IPSec VPN](cs_vpn.html#vpn-setup) | Quickly deploy the strongSwan IPSec VPN Helm chart to connect your {{site.data.keyword.containerlong_notm}} cluster securely to your on-premises data center without a Virtual Router Appliance. |
| 14 February | [Zone available in Seoul](cs_regions.html) | Just in time for the Olympics, deploy a Kubernetes cluster to Seoul in the AP North region. If you have a firewall, be sure to [open the firewall ports](cs_firewall.html#firewall) for this zone and the others within the region that your cluster is in. |
| 08 February | [Update Kubernetes 1.9](cs_versions.html#cs_v19) | Review the changes to make to your clusters before you update to Kubernetes 1.9. |
{: #jan18}
| Date | Title | Description |
|---|---|---|
| 25 January | [Global registry available](../services/Registry/registry_overview.html#registry_regions) | With the {{site.data.keyword.registryshort_notm}}, you can use the global `registry.bluemix.net` to pull IBM-provided public images. |
| 23 January | [Zones available in Singapore and Montreal, CA](cs_regions.html) | Singapore and Montreal are zones available in the {{site.data.keyword.containerlong_notm}} AP North and US East regions. If you have a firewall, be sure to [open the firewall ports](cs_firewall.html#firewall) for these zones and the others within the region that your cluster is in. |
| 08 January | [Enhanced flavors available](cs_cli_reference.html#cs_machine_types) | Series 2 virtual machine types include local SSD storage and disk encryption. [Move your workloads](cs_cluster_update.html#machine_type) to these flavors for improved performance and stability. |
{: #slack}
You can see what others are talking about and ask your own questions in the {{site.data.keyword.containerlong_notm}} Slack. 
{:shortdesc}
If you are not using an IBM ID for your {{site.data.keyword.Bluemix_notm}} account, request an invitation to this Slack. {: tip}