September 30, 2015 | Written by: Chris Rosen
Share this post:
As of May 23rd IBM Bluemix Container Service now provides a native Kubernetes operations experience while removing the burden of maintaining master nodes. Kubernetes itself is based on the Docker engine for managing software images and instantiating containers. Get the details.
IBM Containers launched in the Bluemix United Kingdom region September 29, 2015, giving users access to enterprise-grade container technology based on Docker. IBM Containers availability in London denotes an important milestone for customers that face data sovereignty issues, security concerns, and WAN latency. Several highly regulated industries, such as banking, insurance, and healthcare are required to keep the data within the European Union.
IBM Containers is one initiative underway as the partnership with Docker nears its first anniversary. IBM continues to invest in open-source technology with a strong commitment to portability and hybrid cloud support, bringing containers into the Bluemix platform as a fully supported, first-class citizen.
Benefits of IBM Containers
In addition to the benefits users see with open-source Docker, IBM Containers also provides the following enterprise-class capabilities:
- Hosted registry in Bluemix providing IBM enterprise-ready images (i.e., MobileFirst Platform, WAS Liberty, Node.js, StrongLoop Process Manager), ability to control image access, and ability to easily push or pull your existing Docker images without modification
- Image security readiness guidance using Vulnerability Advisor which provides a vulnerability report before the first container is deployed from that image
- Bare metal deployments enhancing optimal container performance and ensuring you are billed only for the resources being utilized by the container
- Integrated container level monitoring providing agentless insight to the CPU, memory, and network I/O utilization
- Integrated container level logging providing agentless log file collection with the ability to specify additional application log files to display in the Bluemix UI
- Persistent external storage volumes for your persistent data needs
- Enhanced security and isolation by segregating container deployments to your Bluemix organization within a dedicated private network
- Request and bind publicly routed IP addresses to single container deployments, making them accessible via the exposed ports
- Scalable container group deployments with integrated load balancer and optionally the ability to set a fully qualified GoRoute domain name in bluemix.net and auto-recovery ensuring failed containers will automatically redeploy
- Ability to bind any of the 120+ existing Cloud Foundry apps or services to your containers, leveraging capabilities such as Watson, IoT, DevOps, Databases, etc
If you are new to IBM Containers, start here. However, if you are familiar with the Bluemix UI, using the CLI, and scalable groups, then we will navigate the Bluemix UI to leverage IBM Containers in London.
Selecting a Region via the Bluemix Console
Log into Bluemix. If your default region is US South, navigate to the United Kingdom region by selecting the icon in the upper right:
This will display your current region:
Click on the Dashboard link and then Start Containers:
Selecting a Region via the Command Line
Alternatively, you can use the CLI to log into the UK region. If you’ve already set up the required CLI components, logging in is this easy!
$ <b>cf login -a https://api.eu-gb.bluemix.net</b>
API endpoint: https://api.eu-gb.bluemix.net
Targeted org IBM_Containers
Targeted space dev_eu
API endpoint: https://api.eu-gb.bluemix.net (API version: 2.27.0)
$ <b>cf ic login</b>
** Retrieving client certificates from IBM Containers
** Storing client certificates in /root/.ice/certs
Successfully retrieved client certificates
** Authenticating with registry at registry.eu-gb.bluemix.net
Successfully authenticated with registry
$ <b>cf ic namespace get</b>
Have fun!! Send questions or feedback to @ChrisRosen188.