Skip to content

Latest commit

 

History

History
105 lines (69 loc) · 8.63 KB

container_index.md

File metadata and controls

105 lines (69 loc) · 8.63 KB
Raw
copyright lastupdated
years
2014, 2017
2017-09-25

{:new_window: target="_blank"} {:shortdesc: .shortdesc} {:screen: .screen} {:pre: .pre} {:table: .aria-labeledby="caption"} {:codeblock: .codeblock} {:tip: .tip} {:download: .download}

Getting started with {{site.data.keyword.containerlong_notm}}

{: #container_index}

Manage highly available apps inside Docker containers and Kubernetes clusters on the {{site.data.keyword.IBM}} cloud. A container is a standard way to package an app and all its dependencies so that the app can be moved between environments and run without changes. Unlike virtual machines, containers do not bundle the operating system. Only the app code, run time, system tools, libraries, and settings are packaged inside the container, which makes a container more lightweight, portable, and efficient than a virtual machine. {:shortdesc}

Click an option to get started:

With {{site.data.keyword.Bluemix_notm}} Public, you can create Kubernetes clusters or migrate single and scalable container groups to clusters. With {{site.data.keyword.Bluemix_notm}} Dedicated, click this icon to see your options.

Getting started with clusters

{: #clusters}

Kubernetes is an orchestration tool for scheduling app containers onto a cluster of compute machines. With Kubernetes, developers can rapidly develop highly available applications by using the power and flexibility of containers. {:shortdesc}

Before you can deploy an app by using Kubernetes, start by creating a cluster. A cluster is a set of worker nodes that are organized into a network. The purpose of the cluster is to define a set of resources, nodes, networks, and storage devices that keep applications highly available.

To create a lite cluster:

  1. From the catalog External link icon, in the Containers category, click Kubernetes cluster.

  2. Enter a Cluster Name. The default cluster type is lite. Next time, you can create a standard cluster and define additional customizations, like how many worker nodes are in the cluster.

  3. Click Create Cluster. The details for the cluster open, but the worker node in the cluster takes a few minutes to provision. You can see the status of the worker node in the Worker nodes tab. When the status reaches Ready, your worker node is ready to be used.

Good work! You created your first cluster!

  • The lite cluster has one worker node with 2 CPU and 4 GB memory available for your apps to use.
  • The worker node is centrally monitored and managed by a dedicated and highly available {{site.data.keyword.IBM_notm}}-owned Kubernetes master that controls and monitors all of the Kubernetes resources in the cluster. You can focus on your worker node and the apps that are deployed in the worker node without worrying about managing this master too.
  • The resources that are required to run the cluster, such as VLANS and IP addresses, are managed in an {{site.data.keyword.IBM_notm}}-owned IBM Bluemix Infrastructure (SoftLayer) account. When you create a standard cluster, you manage these resources in your own IBM Bluemix Infrastructure (SoftLayer) account. You can learn more about these resources when you create a standard cluster.
  • Tip: Lite clusters that are created with a {{site.data.keyword.Bluemix_notm}} free trial account are automatically removed after the free trial period ends, unless you upgrade to a {{site.data.keyword.Bluemix_notm}} Pay-As-You-Go account.

What's next?

When the cluster is up and running, you can check out the following tasks.

Getting started with clusters in {{site.data.keyword.Bluemix_notm}} Dedicated (Closed Beta)

{: #dedicated}

Kubernetes is an orchestration tool for scheduling app containers onto a cluster of compute machines. With Kubernetes, developers can rapidly develop highly available applications by using the power and flexibility of containers in their {{site.data.keyword.Bluemix_notm}} Dedicated instance. {:shortdesc}

Before you begin, set up your {{site.data.keyword.Bluemix_notm}} Dedicated environment to use clusters. Then, you can create a cluster. A cluster is a set of worker nodes that are organized into a network. The purpose of the cluster is to define a set of resources, nodes, networks, and storage devices that keep applications highly available. After you have a cluster, then you can deploy your app into the cluster.

Tip: If your organization does not have a {{site.data.keyword.Bluemix_notm}} Dedicated environment already, you might not need one. Try a dedicated, standard cluster in the {{site.data.keyword.Bluemix_notm}} Public environment first.

To deploy a cluster in {{site.data.keyword.Bluemix_notm}} Dedicated:

  1. Log in to the {{site.data.keyword.Bluemix_notm}} Public console (https://console.bluemix.net External link icon) with your IBMid. Though you must request a cluster from {{site.data.keyword.Bluemix_notm}} Public, you are deploying it into your {{site.data.keyword.Bluemix_notm}} Dedicated account.

  2. If you have multiple accounts, from the account menu, select a {{site.data.keyword.Bluemix_notm}} account.

  3. From the catalog, in the Containers category, click Kubernetes cluster.

  4. Enter the cluster details.

    1. Enter a Cluster Name.
    2. Select a Kubernetes version to use in the worker nodes.
    3. Select a Machine type. The machine type defines the amount of virtual CPU and memory that is set up in each worker node and that is available for all the containers that you deploy in your nodes.
    4. Choose the Number of worker nodes that you need. Select 3 for higher availability of your cluster.

    The cluster type, location, public VLAN, private VLAN, and hardware fields are defined during the creation process of the {{site.data.keyword.Bluemix_notm}} Dedicated account, so you cannot adjust those values.

  5. Click Create Cluster. The details for the cluster open, but the worker nodes in the cluster take a few minutes to provision. You can see the status of the worker nodes in the Worker nodes tab. When the status reaches Ready, your worker nodes are ready to be used.

    The worker nodes are centrally monitored and managed by a dedicated and highly available {{site.data.keyword.IBM_notm}}-owned Kubernetes master that controls and monitors all of the Kubernetes resources in the cluster. You can focus on your worker nodes and the apps that are deployed in the worker nodes without worrying about managing this master too.

Good work! You created your first cluster!

What's next?

When the cluster is up and running, you can check out the following tasks.