Infrastructure Software

Oracle Container Services for Use with Kubernetes 1.1.13 and 1.1.14 are currently available as Developer Previews only. Oracle does not provide support for and recommends against production usage of pre-release software.

With the release of Oracle Container Services for Use with Kubernetes 1.1.13, the kubeadm-setup.sh and kubeadm-registry.sh scripts have been deprecated in favour of the new kubeadm-ha-setup tool which replaces both of the older scripts and includes new functionality. There is feature parity between the older scripts and the new tool, so existing commands will still work. For more information about the new kubeadm-ha-setup tool, please consult the Oracle Container Services for Use with Kubernetes User Guide.

Upgrading a cluster created with kubeadm-setup.sh

Before upgrading an existing cluster created with kubeadm-setup.sh you need to create or edit the ha.yaml file at /usr/local/share/kubeadm/run/kubeadm/ha.yaml to provide information about the existing cluster include IP address information for the master nodes:

clusters:
- name: master
  # API Server Loadbalancer IP address. Used with the '--lb' flag
  # Note: if this attribute is active "vip" is not required.
  load_balancer: X.X.X.X
  # API Server Floating IP address. vip represents Virtual IP, keepalived
  # assigns the role to the appropriate node and manages the virtual IP (VIP)
  # between the master nodes. This option is only needed when 'load_balancer'
  # is not used(keepalived).
  # vip: X.X.X.1
  # Master nodes for the cluster. Valid number of nodes are: 1 or 3.  
  nodes:
  - X.X.X.2
  - X.X.X.3
  - X.X.X.4
  # SSH key for setup of remote master nodes. Only applies for >1 'nodes'
  private_key: /root/.ssh/id_rsa
  # SSH key for setup of remote master nodes. Only applies for >1 'nodes'
  user: root
  # The repository location of all the k8s docker images.
  # Note: please remove any trailing "/" from the registry url address.
  image: container-registry.oracle.com/kubernetes
  k8sversion: v1.12.7
  # kubeadm token has to be in the format as shown below
  # [0-9a-z](6).[0-9a-z](16)
  #token: 5nvo0q.kkroptfdwm7hihgf
  # Kubernetes API Server extra sans. IP address(es) separated by ","
  #apiserver_cert_extra_sans: 10.1.0.0,10.2.0.0
  # Kubernetes service CIDR (default: 10.96.0.0/12)
  #service_cidr: 10.96.0.0/12
  # Kubernetes pod cidr (default: 10.244.0.0/16)
  #pod_cidr: 10.244.0.0/16
  # Kubernetes API Server bind port (default: 6443)
  #apiserver_bind_port: 6443
  # API advertised address for internal routing to the API Server
  #apiserver_advertise_address: 100.0.0.2
  # Kubernetes proxy routing mode. Choices are: iptables, ipvs. (default: iptables)
  #kube_proxy_mode: iptables

Once this file is created, follow the steps documented in the Updating the High Availability Cluster chapter of the Oracle Container Services for Use with Kubernetes User Guide to complete the upgrade.