Cloud Platform as a Service

 View Only

Running containers in the most secure clusters

By Chris Rosen posted 4 days ago

  

Security and visibility of your environments at initial instantiation time without requiring manual configuration is paramount for accelerating workload deployment and return on investment.

IBM Cloud is focused on regulated workloads and our customers are asking for stronger controls built into the cluster with the default deployment. The new Secure by Default is a security-focused change in the network settings for Red Hat OpenShift on IBM Cloud and IBM Cloud Kubernetes Service that does not require an administrator to manually configure limited network connectivity to decrease cluster attack surface. With Secure by Default networking, ROKS and IKS VPC clusters, only the traffic that is necessary for the cluster to function will be allowed and all other access will be blocked. This feature changes the default VPC security group settings as well as new Virtual Private Endpoints (VPEs) for common IBM services.

We provide on-by-default security integrations to your IBM Cloud Key Protect or IBM Cloud HyperProtect CryptoServices providing worker pool and cluster encryption enabling your more secure and critical workloads. Manage each of your Kubernetes secrets centrally in IBM Cloud Secrets Manager.

Lastly we provide on-by-default observability integration providing you full insights and telemetry to your workloads using IBM Cloud Monitoring and IBM Cloud Logs. Set custom alerts and create dashboards for metrics and logs from infrastructure to cloud-native applications running in the cluster.

Run your workloads with an industry-leading 99.99% SLA with highly-available master nodes and multizone clusters ensuring your applications continue to serve customer requests.

Try it on IBM Cloud today!

0 comments
2 views

Permalink