After you complete the prerequisite steps described in Prerequisites, proceed with bootstrapping your AWS-based Mirantis Container Cloud management cluster.
To bootstrap an AWS-based management cluster:
Log in to the bootstrap node running Ubuntu 18.04 that is configured as described in Prerequisites.
Download and run the Container Cloud bootstrap script:
wget https://binary.mirantis.com/releases/get_container_cloud.sh
chmod 0755 get_container_cloud.sh
./get_container_cloud.sh
Change the directory to the kaas-bootstrap folder
created by the get_container_cloud.sh script.
Obtain your license file that will be required during the bootstrap. See step 3 in Getting Started with Mirantis Container Cloud.
Save the license file as mirantis.lic under the kaas-bootstrap
directory.
Verify access to the target cloud endpoint from Docker. For example:
docker run --rm alpine sh -c "apk add --no-cache curl; \
curl https://ec2.amazonaws.com"
The system output must contain no error records. In case of issues, follow the steps provided in Troubleshooting.
In templates/aws/machines.yaml.template,
modify the spec:providerSpec:value section
by substituting the ami:id parameter with the corresponding value
for Ubuntu 18.04 from the required AWS region. For example:
spec:
providerSpec:
value:
apiVersion: aws.kaas.mirantis.com/v1alpha1
kind: AWSMachineProviderSpec
instanceType: c5d.2xlarge
ami:
id: ami-033a0960d9d83ead0
Also, modify other parameters as required.
Optional. In templates/aws/cluster.yaml.template, modify the default
AWS instance types and AMIs configuration for further creation
of managed clusters:
providerSpec:
value:
...
kaas:
...
regional:
- provider: aws
helmReleases:
- name: aws-credentials-controller
values:
config:
allowedInstanceTypes:
minVCPUs: 8
# in MiB
minMemory: 16384
# in GB
minStorage: 120
supportedArchitectures:
- "x86_64"
filters:
- name: instance-storage-info.disk.type
values:
- "ssd"
allowedAMIs:
-
- name: name
values:
- "ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20200729"
- name: owner-id
values:
- "099720109477"
Also, modify other parameters as required.
Available since 2.5.0 Optional. Configure the regional NTP server parameters to be applied to all machines of regional and managed clusters in the specified region.
In templates/aws/cluster.yaml.template, add the ntp:servers section
with the list of required servers names:
spec:
...
providerSpec:
value:
kaas:
...
regional:
- helmReleases:
- name: aws-provider
values:
config:
lcm:
...
ntp:
servers:
- 0.pool.ntp.org
...
provider: aws
...
Generate the AWS Access Key ID with Secret Access Key for the admin
user and select the AWS default region name.
For details, see AWS General Reference: Programmatic access.
Export the following parameters by adding the corresponding values
for the AWS admin credentials created in the previous step:
export KAAS_AWS_ENABLED=true
export AWS_SECRET_ACCESS_KEY=XXXXXXX
export AWS_ACCESS_KEY_ID=XXXXXXX
export AWS_DEFAULT_REGION=us-east-2
For Container Cloud to communicate with the AWS APIs, create the AWS CloudFormation stack that contains properly configured IAM users and policies:
./kaas bootstrap aws policy
If you do not have access to create the CloudFormation stack, users, or policies:
Log in to your AWS Management Console.
On the home page, expand the upper right menu with your user name and capture your Account ID.
Create the CloudFormation template:
./kaas bootstrap aws policy --account-id <accountId> --dump > cf.yaml
Substitute the parameter enclosed in angle brackets with the corresponding value.
Send the cf.yaml template to your AWS account admin to create
the CloudFormation stack from this template.
Generate the AWS Access Key ID with Secret Access Key
for the bootstrapper.cluster-api-provider-aws.kaas.mirantis.com
user, that was created in the previous step,
and select the AWS default region name.
Export the AWS bootstrapper.cluster-api-provider-aws.kaas.mirantis.com
user credentials that were created in the previous step:
export KAAS_AWS_ENABLED=true
export AWS_SECRET_ACCESS_KEY=XXXXXXX
export AWS_ACCESS_KEY_ID=XXXXXXX
export AWS_DEFAULT_REGION=us-east-2
Available since 2.6.0 Optional.
If you require all Internet access to go through a proxy server,
in bootstrap.env, add the following environment variables
to bootstrap the management and regional cluster using proxy:
HTTP_PROXY
HTTPS_PROXY
NO_PROXY
Example snippet:
export HTTP_PROXY=http://proxy.example.com:3128
export HTTPS_PROXY=http://user:pass@proxy.example.com:3128
export NO_PROXY=172.18.10.0,registry.internal.lan
The following variables formats are accepted:
Variable |
Format |
|---|---|
|
|
|
Comma-separated list of IP addresses or domain names |
For the list of Mirantis resources and IP addresses to be accessible from the Container Cloud clusters, see Reference Architecture: Hardware and system requirements.
Optional. Skip this step to use the default password password
in the Container Cloud web UI.
Caution
For security reasons, Mirantis strongly recommends changing the default password on publicly accessible Container Cloud deployments.
Configure the IAM parameters:
Create hashed passwords for every IAM role:
reader, writer, and operator for bare metal deployments:
./bin/hash-generate -i 27500
The hash-generate utility requests you to enter a password and outputs the parameters required for the next step. Save the password that you enter in a secure location. This password will be used to access the Container Cloud web UI with a specific IAM role.
Example of system response:
passwordSalt: 6ibPZdUfQK8PsOpSmyVJnA==
passwordHash: 23W1l65FBdI3NL7LMiUQG9Cu62bWLTqIsOgdW8xNsqw=
passwordHashAlgorithm: pbkdf2-sha256
passwordHashIterations: 27500
Run the tool several times to generate hashed passwords for every IAM role.
Open templates/cluster.yaml.template for editing.
In the initUsers section, add the following parameters for each
IAM role that you generated in the previous step:
passwordSalt - base64-encoded randomly generated sequence of bytes.
passwordHash - base64-encoded password hash generated using
passwordHashAlgorithm with passwordHashIterations.
Supported algorithms include pbkdf2-sha256 and pbkdf-sha512.
Optional. Configure external identity provider for IAM.
Run the bootstrap script:
./bootstrap.sh all
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.
The URL and credentials for the Container Cloud web UI. The system outputs these details when the bootstrap completes.
The StackLight endpoints. For details, see Operations Guide: 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
When the bootstrap is complete, the bootstrap cluster resources are freed up.
In case of deployment issues, collect and inspect the bootstrap and management cluster logs as described in Troubleshooting.
Optional. Deploy an additional regional cluster of a different provider type as described in Deploy an additional regional cluster (optional).
Now, you can proceed with operating your management cluster using the Container Cloud web UI and deploying managed clusters as described in Create an AWS-based managed cluster.