The Kubernetes Installer for Oracle Classic IaaS provides a Terraform-based Kubernetes installation for the Oracle Cloud@Customer (OCC) & OCI-Classic (OCI-C) Oracle Cloud Infrastructure platforms.

This installer utilises the Terraform Oracle Public Cloud Provider. It consists of a set of Terraform configurations & shell scripts that are used to provision the Kubernetes control plane in accordance with Oracle Container Services for use with Kubernetes (OCS-K) - which is based on Kubernetes version 1.8.4, as released upstream.

The OCSK Kubernetes distribution has passed the CNCF Certified Kubernetes conformance program. For enterprises and startups using Kubernetes, conformance guarantees interoperability from one Kubernetes installation to the next. It allows them flexibility and vendor independence.

Terraform is used to provision the cloud infrastructure and any required local resources for the Kubernetes cluster including:

• Creates single-node compute instance:

  • x1 OCPU utilised.
  • Installed OS distribution is Oracle Linux 7.2.
  • Includes associated storage and networking elements.
  • Reserves and associates a public IP address to the instance.

• Installs Kubernetes cluster (master node):

  • Taints the node to support worker function.

Terraform uses remote-exec scripts to handle the instance-level configuration for the instance to provision:

• Single node Kubernetes master configuration.
• Installation is in accordance with the previously referenced OCS-K.
• Kubernetes cluster version: 1.8.4.
• Kubernetes Dashboard and kube-DNS cluster add-ons.
• Optional - Monitoring and Metrics:
  • Grafana, Heapster, & InfluxDB for enhanced monitoring and metrics.
• Optional - Functions as a Service:
  • Include the Fn, Fn Flow, & Fn UI server-side components. Installed via published helm charts.
• Optional - Microservices Environment:
  • Include WeaveScope Microservices Dashboard and E-Commerce application. Functioning microservices e-commerce application (Socks Shop) with additional enhanced management dashboard.
• Optional - Kubernetes Ingress:
  • Include Traefik Ingress and sample applications. Functioning K8s ingress & controller (L7 Load Balancer) deployed and configured to perform path based traffic steering to x3 sample microservices applications.
• Optional - Service Mesh:
  • Include Istio Service Mesh. Functioning Istio service mesh and integrated sample microservices application (BookInfo – per istio.io).

1. Download and install Terraform (v0.11.3 or later). Follow the link for Hashicorp instructions.
2. Terraform OPC provider (can be pulled automatically using terraform init directive once Terraform is configured).
3. Register an account at the Oracle Container Registry (OCR). Be sure to accept the Oracle Standard Terms and Restrictions after registering with the OCR. The installer will request your OCR credentials at build time. Registration with the OCR is a dependency for the installer to be able to download the containers which will be used to assemble the K8s control plane.

Initialize Terraform:

$ terraform init

View what Terraform plans do before actually doing it:

$ terraform plan

Use Terraform to Provision resources and stand-up k8s cluster on OCI:

$ terraform apply

At this point the configuration will prompt for the following inputs before building the cluster:

$ variable "ociUser"
$ #(input compute user account with compute_operations rights)

$ variable "ociPass"
$ #(input password for “ociUser”)

$ variable "idDomain"
$ #(input compute tenancy service instance id)

$ variable "apiEndpoint"
$ #(input compute tenancy rest endpoint url)

$ variable "containerRepoUser"
$ #(input oracle container registry username)

$ variable "containerRepoPass"
$ #(input oracle container registry password)

Installer will also ask the user if any of the following environments should be provisioned to the cluster. Enter true or false for each item accordingly:

$ Enhanced Dashboard, Monitoring and Metrics:
$ #include grafana, heapster, & influxdb..

$ microservices environment:
$ #include weavescope microservices dashboard and e-commerce application..

$ kubernetes ingress:
$ #include traefik ingress and sample applications..

$ Service Mesh:
$ #include istio service mesh, and integrated sample microservices application..

$ fn:
$ #include fn installed via published helm charts..

The entire build and cluster creation process is automated – no further input is required.

The Kubernetes cluster will be running after the configuration is applied successfully, and the remote-exec scripts have completed. Typically, this takes around 15-25 minutes after terraform apply and will vary depending on the overall configuration, geographic location, and number of environments selected.

Once completed, Terraform will output the public IP address of the cluster:

$ Apply complete! Resources: 14 added, 0 changed, 0 destroyed.
$
$ Outputs:
$
$ Master_Node_Public_IPs = [
$     129.199.199.199
$]

Terraform will also output the Kubernetes running services and pods via tabular format at the conclusion of the installation process.

To access Kubernetes dashboard, or any of the other web interfaces running in the cluster: SSH tunnel to the IP address of the Kubernetes dashboard pod &/or other pods via the public/NAT IP address assigned to the compute instance. Keys are located in the directory ./ssh.

To access the Traefik dashboard, browse to the public IP address of the instance on port 8080.

Keys are provided for simplicity only, for long running deployments it is strongly recommended that you replace the provided keys prior to deployment.

During the setup process, kubeadm-setup.sh generates and outputs to stdout a token that can be used to add more nodes to the cluster. Further instruction is available via OCS-K.

• Oracle Container Services for use with Kubernetes (OCS-K): Oracle provides a setup and configuration script that takes advantage of the kubeadm-setup.sh cluster configuration utility. This script eases the setup on Oracle Linux including configuration of networking, firewall, proxies and the initial cluster deployment, as well as providing additional support for backup and recovery.
• environments: Additional documentation, instructions and references will be included here (Wiki) which describe how to access and utilise each of the additional environments that can be automatically provisioned to the cluster.