LearnITGuide.net

This post shows you how to access or connect your linux server remotely from windows. SSH is the network protocol works on Port 22 that helps us to take the remote connection over the network either from linux to linux or windows to linux. But anyway linux would be your target server and windows server would be your source server from which you try to connect your target linux server.
So Target Linux server must have running SSH service and also it should allow port 22 in firewall if firewall is running else firewall will block us to take the remote.


By default, SSH Command is available in Linux server, So we can use SSH command directly to take remote from Linux to Linux Machine. But If you want to take remote connection from Windows server to Linux server, You have to install PuTTY on Windows server. PuTTY is available for installation also it is available as a executable file which can be used without installation.

Lets get started.

Step 1: Download PuTTY 

Download the respective 32-bit or 64-bit version based on your server type from this link - https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

Direct Link:
32-bit: putty-0.71-installer.msi
64-bit: putty-64bit-0.71-installer.msi

Step 2: Install PuTTY on Windows

Once PuTTY software is downloaded, double click and run the software for installation.



Click Next.


Click Next.



Click Install.


Installation will finish quickly. At the final screen, untick "View README file" and Click "Finish".

Step 3: Start Putty Software

[ads-post]

Once installation is completed, Open your installed Putty software from your Programs.



Enter the IP Address of your target linux server you wish to connect from windows machine over the network. Make sure port number "22" and connection type "SSH" are specified in the box. Click "Open".


If everything is ok, you will be asked to enter the correct username and password. Provide your details and start accessing your linux server remotely from windows server.

Hope this post helps you to access linux server from windows remotely by installing putty software.
Support Us: Share with your friends and groups.

Stay connected with us on social networking sites, Thank you.
YouTube | Facebook | Twitter | Pinterest | Rss
Incoming Searches : accessing linux server, access linux server from windows, connect linux server, connecting linux server from windows, connect linux remotely, access linux remotely from windows, linux remote server, putty for windows, connect linux server using putty, download putty, install putty on windows, download putty for windows, access linux remotely

This post gives you an set of Ansible Playbook that would help you to build a Complete Multinode Kubernetes Cluster in an automated way to deploy an containerized application. In the previous post, we have given you the step by step procedure to install and configure kubernetes cluster manually on linux servers using kubeadm and kubectl commands.

You can also refer these below mentioned related links to understand this topic from basics.
What is Kubernetes - Learn Kubernetes from Basics
Create Kubernetes Deployment, Services & Pods Using Kubectl
Create Kubernetes YAML for Deployment, Service & Pods
What is Docker - Get Started from Basics - Docker Tutorial
What is Container, What is Docker on Container - Get Started
How to Install Docker on CentOS 7 / RHEL 7
Docker Images Explained with Examples - Docker Tutorial
How to Run Docker Containers - Explained with Examples

These playbooks will work on any physical servers, virtual machines, aws cloud, google cloud or any other cloud servers. This has been tested and verified on Centos 7.3 64 bit operating systems.



Let's get started.

We have created these ansible playbooks and stored in our github repository.

List of Files Available in this repository

ansible.cfg - Ansible configuration file created locally.
hosts - Ansible Inventory File
env_variables - Main environment variable file where we have to specify based on our environment.
settingup_kubernetes_cluster.yml - Ansible Playbook to perform prerequisites ready, setting up nodes, configure master node.
configure_worker_nodes.yml - Ansible Playbook to join worker nodes with master node.
clear_k8s_setup.yml - Delete entire configurations from all nodes.
playbooks - Its a directory holds all playbooks.

How to use this ansible playbooks: (Setup Instructions)

Once your servers are ready (one master node and multiple worker nodes), follow these below instructions.

1. Make an entry of your each hosts in /etc/hosts file for name resolution.

cat /etc/hosts
192.168.2.1 kubernetes-master.learnitguide.net kubernetes-master
192.168.2.2 kubernetes-worker1.learnitguide.net kubernetes-worker1
192.168.2.3 kubernetes-worker2.learnitguide.net kubernetes-worker2

2. Make sure kubernetes master node and other worker nodes are reachable between each other.

3. Internet connection must be enabled in all nodes, required packages will be downloaded from kubernetes official yum repository.

4. Clone this repository into your master node.

git clone https://github.com/learnitguide/kubernetes-and-ansible.git

once it is cloned, get into the directory.

cd kubernetes-and-ansible/centos

5. Edit a file "hosts" available in "centos" directory, Just make your entries of your all kubernetes nodes along with respective ip address.

Master Node Entries

[kubernetes-master-nodes]
kubernetes-master.learnitguide.net ansible_host=192.168.2.1

Worker Node Entries

[kubernetes-worker-nodes]
kubernetes-worker1.learnitguide.net ansible_host=192.168.2.2
kubernetes-worker2.learnitguide.net ansible_host=192.168.2.3

6. Edit a file "env_variables" available in "centos" directory and provide your server details like advertise address ip and cidr range values. Dont edit any other values in this file.

ad_addr: 192.168.2.1
cidr_v: 172.16.0.0/16

7. Deploy the ssh key from master node to other nodes for password less authentication to run ansible playbooks. Generate a SSH Key pair using ssh-keygen as below.

ssh-keygen

Enter the required values or just hit enter to take the default values. Copy the public key to all nodes including your master node and make sure you are able to login into any nodes without password. Refer this link to know How to configure SSH Passwordless Login Authentication (SSH-keygen)

8. Setting up Kubernetes Cluster Nodes using Ansible Playbook.
There is a playbook called "settingup_kubernetes_cluster.yml" to setup all nodes and kubernetes master configuration. Just run this playbook using ansible-playbook command first.

ansible-playbook settingup_kubernetes_cluster.yml

9. Joining Worker Nodes
Run "join_kubernetes_workers_nodes.yml" playbook to join the worker nodes with kubernetes master node once "settingup_kubernetes_cluster.yml" playbook tasks are completed.

ansible-playbook join_kubernetes_workers_nodes.yml

Verify the configuration from master node.

kubectl get nodes

That's it, we have successfully configured our kubernetes cluster setup using ansible playbook. you can now try deploying some applications to make sure everything is working fine.
Refer these links to Create Kubernetes Deployment, Services & Pods Using Kubectl and Create Kubernetes YAML for Deployment, Service & Pods

You can also refer these below mentioned related links to understand this topic from basics.
What is Kubernetes - Learn Kubernetes from Basics
What is Docker - Get Started from Basics - Docker Tutorial
What is Container, What is Docker on Container - Get Started
How to Install Docker on CentOS 7 / RHEL 7
Docker Images Explained with Examples - Docker Tutorial
How to Run Docker Containers - Explained with Examples

Support Us: Share with your friends and groups.

Stay connected with us on social networking sites, Thank you.
YouTube | Facebook | Twitter | Pinterest | Rss 
kubernetes, kubernetes ansible, kubernetes ansible playbooks, kubernets using ansible, install kubernetes with ansible, ansible playbook, deploy kubernetes using ansible, kubernetes ansible deployment, setup kubernets using ansible, install kubernetes cluster using ansible

In this post, we will provide you the step by step procedure of how to create route tables and assign subnets in AWS.
A route table contains a set of rules, called routes, that are used to determine where network traffic is directed.

Each subnet in your VPC must be associated with a route table; the table controls the routing for the subnet. A subnet can only be associated with one route table at a time, but you can associate multiple subnets with the same route table.

To make you understand better, lets have a sample VPC architecture as shown in below image as our requirement.

• 1 VPC (10.0.0.0/16)
• 2 Subnets - Public Subnet (10.0.1.0/24) and Private Subnet (10.0.2.0/24)
• 1 Internet Gateway attached to Public Subnet.

Already we have created VPC, Internet Gateway and Subnets (Public and Private). Refer the previous post (AWS VPC | Create New VPC, Subnets, Internet Gateway ) where we have covered,

1. How to create a New VPC?
2. How to create Internet Gateway and attach to newly created VPC?
3. How to create Public Subnet and Private Subnet?

In this post, we will cover only,

1. How to create Route Tables for Public and Private Subnet?
2. How to edit Route Tables?
3. How to add Internet Gateway route to Public Route Table?
4. How to Associate Public and Private Subnets to respective Route Tables?

Note : In order to create and manage any AWS Services, we must have some valid users created with IAM policy defined. Else you wont have a access to these AWS services.

Login into AWS Management Console.

[ads-post]
I have created my VPC in US East (N. Virginia) region, So, make sure you are in the right region.


Go to "Services", type "VPC" in the search box and select the VPC from the search result.


How to create Route Tables for Public and Private Subnet?

Go to "Route Tables" section from the left side panel.

Create Public Route Table:

By default, one route table is created and attached to VPC. Let's modify the tag name, attach the Internet Gateway to this route table and add the public subnet to it.

Select the route table, pull down "actions" button and select "Add/Edit tags".


Click "Create Tag".


Enter the Key "Name" and Value "Public RT".


Go to "Routes" section and click "Edit routes".


Click "Add Route" and Enter the Destination and Target your VPC as below and "Save Routes".


Again select the "Public RT" route table and go to "Subnet Associations".


Click "Edit Subnet Associations", mark only the correct "Public Subnet" which we have created and click "Save".


Create Private Route Table:

Now click "Create Route Table".

Enter the name and attach the VPC.


Select the Private Route Table now and go to Subnet Association section. Click "Edit Subnet Associations".


Mark the correct private subnet this time and click save.