Notes About Server In admin.conf (#6854)
* Add note about changing private IP in admin.conf. When I run kubespray, a load balancer is created which should be used instead of the ip of the controller node. * Procedure to find load balancer and update admin.conf When I run kubespray, a load balancer is used instead of the private ip of the controller.
This commit is contained in:
parent
c25d624524
commit
102fb94524
2 changed files with 36 additions and 0 deletions
|
@ -49,7 +49,10 @@ ansible-playbook -i ./inventory/hosts ./cluster.yml -e ansible_user=ubuntu -b --
|
||||||
If you want to use another distribution than Ubuntu 18.04 (Bionic) LTS, you can modify the search filters of the 'data "aws_ami" "distro"' in variables.tf.
|
If you want to use another distribution than Ubuntu 18.04 (Bionic) LTS, you can modify the search filters of the 'data "aws_ami" "distro"' in variables.tf.
|
||||||
|
|
||||||
For example, to use:
|
For example, to use:
|
||||||
|
|
||||||
- Debian Jessie, replace 'data "aws_ami" "distro"' in variables.tf with
|
- Debian Jessie, replace 'data "aws_ami" "distro"' in variables.tf with
|
||||||
|
|
||||||
|
```
|
||||||
data "aws_ami" "distro" {
|
data "aws_ami" "distro" {
|
||||||
most_recent = true
|
most_recent = true
|
||||||
|
|
||||||
|
@ -65,8 +68,11 @@ data "aws_ami" "distro" {
|
||||||
|
|
||||||
owners = ["379101102735"]
|
owners = ["379101102735"]
|
||||||
}
|
}
|
||||||
|
```
|
||||||
|
|
||||||
- Ubuntu 16.04, replace 'data "aws_ami" "distro"' in variables.tf with
|
- Ubuntu 16.04, replace 'data "aws_ami" "distro"' in variables.tf with
|
||||||
|
|
||||||
|
```
|
||||||
data "aws_ami" "distro" {
|
data "aws_ami" "distro" {
|
||||||
most_recent = true
|
most_recent = true
|
||||||
|
|
||||||
|
@ -82,8 +88,11 @@ data "aws_ami" "distro" {
|
||||||
|
|
||||||
owners = ["099720109477"]
|
owners = ["099720109477"]
|
||||||
}
|
}
|
||||||
|
```
|
||||||
|
|
||||||
- Centos 7, replace 'data "aws_ami" "distro"' in variables.tf with
|
- Centos 7, replace 'data "aws_ami" "distro"' in variables.tf with
|
||||||
|
|
||||||
|
```
|
||||||
data "aws_ami" "distro" {
|
data "aws_ami" "distro" {
|
||||||
most_recent = true
|
most_recent = true
|
||||||
|
|
||||||
|
@ -99,6 +108,31 @@ data "aws_ami" "distro" {
|
||||||
|
|
||||||
owners = ["688023202711"]
|
owners = ["688023202711"]
|
||||||
}
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
## Connecting to Kubernetes
|
||||||
|
|
||||||
|
You can use the following set of commands to get the kubeconfig file from your newly created cluster. Before running the commands, make sure you are in the project's root folder.
|
||||||
|
|
||||||
|
```
|
||||||
|
# Get the controller's IP address.
|
||||||
|
CONTROLLER_HOST_NAME=$(cat ./inventory/hosts | grep "\[kube-master\]" -A 1 | tail -n 1)
|
||||||
|
CONTROLLER_IP=$(cat ./inventory/hosts | grep $CONTROLLER_HOST_NAME | grep ansible_host | cut -d'=' -f2)
|
||||||
|
|
||||||
|
# Get the hostname of the load balancer.
|
||||||
|
LB_HOST=$(cat inventory/hosts | grep apiserver_loadbalancer_domain_name | cut -d'"' -f2)
|
||||||
|
|
||||||
|
# Get the controller's SSH fingerprint.
|
||||||
|
ssh-keygen -R $CONTROLLER_IP > /dev/null 2>&1
|
||||||
|
ssh-keyscan -H $CONTROLLER_IP >> ~/.ssh/known_hosts 2>/dev/null
|
||||||
|
|
||||||
|
# Get the kubeconfig from the controller.
|
||||||
|
mkdir -p ~/.kube
|
||||||
|
ssh -F ssh-bastion.conf centos@$CONTROLLER_IP "sudo chmod 644 /etc/kubernetes/admin.conf"
|
||||||
|
scp -F ssh-bastion.conf centos@$CONTROLLER_IP:/etc/kubernetes/admin.conf ~/.kube/config
|
||||||
|
sed -i "s^server:.*^server: https://$LB_HOST:6443^" ~/.kube/config
|
||||||
|
kubectl get nodes
|
||||||
|
```
|
||||||
|
|
||||||
**Troubleshooting**
|
**Troubleshooting**
|
||||||
|
|
||||||
|
|
|
@ -127,6 +127,8 @@ host and can optionally be configured on your ansible host by setting
|
||||||
- If `kubeconfig_localhost` enabled `admin.conf` will appear in the `inventory/mycluster/artifacts/` directory after deployment.
|
- If `kubeconfig_localhost` enabled `admin.conf` will appear in the `inventory/mycluster/artifacts/` directory after deployment.
|
||||||
- The location where these files are downloaded to can be configured via the `artifacts_dir` variable.
|
- The location where these files are downloaded to can be configured via the `artifacts_dir` variable.
|
||||||
|
|
||||||
|
NOTE: The controller host name in the admin.conf file might be a private IP. If so, change it to use the controller's public IP or the cluster's load balancer.
|
||||||
|
|
||||||
You can see a list of nodes by running the following commands:
|
You can see a list of nodes by running the following commands:
|
||||||
|
|
||||||
```ShellSession
|
```ShellSession
|
||||||
|
|
Loading…
Reference in a new issue