Finalize the bootstrap

1. Run the bootstrap script:

   ./bootstrap.sh all
   

   • In case of deployment issues, refer to Troubleshooting and inspect logs.

   • If the script fails for an unknown reason:

     1. Run the cleanup script:

        ./bootstrap.sh cleanup
        

     2. Rerun the bootstrap script.

2. When the bootstrap is complete, collect and save the following management cluster details in a secure location:

   • The kubeconfig file located in the same directory as the bootstrap script. This file contains the admin credentials for the management cluster.

   • The private ssh_key for access to the management cluster nodes that is located in the same directory as the bootstrap script.

     Note

     If the initial version of your Container Cloud management cluster was earlier than 2.6.0, ssh_key is named openstack_tmp and is located at ~/.ssh/.

   • The URL for the Container Cloud web UI.

     To create users with permissions required for accessing the Container Cloud web UI, see Create initial users after a management cluster bootstrap.

   • The StackLight endpoints. For details, see Access StackLight web UIs.

   • The Keycloak URL that the system outputs when the bootstrap completes. The admin password for Keycloak is located in kaas-bootstrap/passwords.yml along with other IAM passwords.

   Note

   The Container Cloud web UI and StackLight endpoints are available through Transport Layer Security (TLS) and communicate with Keycloak to authenticate users. Keycloak is exposed using HTTPS and self-signed TLS certificates that are not trusted by web browsers.

   To use your own TLS certificates for Keycloak, refer to Configure TLS certificates for cluster applications.

   Note

   When the bootstrap is complete, the bootstrap cluster resources are freed up.

3. Verify that network addresses used on your clusters do not overlap with the following default MKE network addresses for Swarm and MCR:

   • 10.0.0.0/16 is used for Swarm networks. IP addresses from this network are virtual.

   • 10.99.0.0/16 is used for MCR networks. IP addresses from this network are allocated on hosts.

   Verification of Swarm and MCR network addresses

   To verify Swarm and MCR network addresses, run on any master node:

   docker info
   

   Example of system response:

   Server:
    ...
    Swarm:
     ...
     Default Address Pool: 10.0.0.0/16
     SubnetSize: 24
     ...
    Default Address Pools:
      Base: 10.99.0.0/16, Size: 20
    ...
   

   Not all of Swarm and MCR addresses are usually in use. One Swarm Ingress network is created by default and occupies the 10.0.0.0/24 address block. Also, three MCR networks are created by default and occupy three address blocks: 10.99.0.0/20, 10.99.16.0/20, 10.99.32.0/20.

   To verify the actual networks state and addresses in use, run:

   docker network ls
   docker network inspect <networkName>