Skip to content

Latest commit

 

History

History
59 lines (41 loc) · 2.29 KB

icp.md

File metadata and controls

59 lines (41 loc) · 2.29 KB
Raw

Table of Contents generated with DocToc

IBM Cloud Private Deployment Guide

Federation v2 can be deployed to and manage IBM Cloud Private clusters. As Federation v2 requires Kubernetes v1.11 or greater, please make sure to deploy IBM Cloud Private 3.1.1 or higher.

The following example deploys two IBM Cloud Private 3.1.1 clusters named cluster1 and cluster2.

Install IBM Cloud Private

Please follow the guide in IBM Cloud Private 3.1.1 Knowledge Center to install.

NOTE: We need to install two clusters named cluster1 and cluster2, so after cluster/config.yaml is generated, update the names of the 2 clusters to 'cluster1' and 'cluster2' before installing federation.

For the first cluster, set the following value in cluster/config.yaml as follows:

cluster_name: cluster1

For the second cluster, set the following value in cluster/config.yaml as follows:

cluster_name: cluster2

Post Install Configuration

As IBM Cloud Private is enforcing container image security policy by default, and the default image security policy does not allow pulling the Federation v2 image from quay.io/kubernetes-multicluster/federation-v2:*, we need to update the image security policy as follows:

$ kubectl edit clusterimagepolicies ibmcloud-default-cluster-image-policy

Update spec.repositories by adding quay.io/kubernetes-multicluster/federation-v2:*:

spec:
  repositories:
    - name: "quay.io/kubernetes-multicluster/federation-v2:*"

Once all pods are running you can return to the User Guide to deploy the cluster registry and Federation v2 control-plane.