RANCHER

  • Linux
Please feel free to contact us
Go

About

Rancher is a comprehensive container management platform engineered to streamline the complexities of deploying and administering containerized applications across diverse infrastructure landscapes. Equipped with support for leading container orchestration engines such as Kubernetes, Docker Swarm, and Apache Mesos, Rancher offers a cohesive interface for provisioning, scaling, and updating containerized workloads. Its versatility extends across on-premises servers, cloud environments, and hybrid setups, ensuring a unified management experience regardless of the underlying infrastructure. By providing robust tools and features, Rancher empowers organizations to efficiently manage containerized applications, facilitating the seamless adoption of containerization and microservices architectures.

  1. Type virtual machines in the search.
  2. Under Services, select Virtual machines.
  3. In the Virtual machines page, select Add. The Create a virtual machine page opens.
  4. In the Basics tab, under Project details, make sure the correct subscription is selected and then choose to Create new resource group. Type myResourceGroup for the name.*.
  5. Under Instance details, type myVM for the Virtual machine name, choose East US for your Region, and choose Ubuntu 18.04 LTS for your Image. Leave the other defaults.
  6. Under Administrator account, select SSH public key, type your user name, then paste in your public key. Remove any leading or trailing white space in your public key.
  7. Under Inbound port rules > Public inbound ports, choose Allow selected ports and then select SSH (22) and HTTP (80) from the drop-down.
  8. Leave the remaining defaults and then select the Review + create button at the bottom of the page.
  9. On the Create a virtual machine page, you can see the details about the VM you are about to create. When you are ready, select Create.

It will take a few minutes for your VM to be deployed. When the deployment is finished, move on to the next section.

Connect to virtual machine

Create an SSH connection with the VM.

  1. Select the Connect button on the overview page for your VM.
  2. In the Connect to virtual machine page, keep the default options to connect by IP address over port 22. In Login using VM local account a connection command is shown. Select the button to copy the command. The following example shows what the SSH connection command looks like:

bashCopy

ssh azureuser@10.111.12.123

  1. Using the same bash shell you used to create your SSH key pair (you can reopen the Cloud Shell by selecting >_ again or going to https://shell.azure.com/bash), paste the SSH connection command into the shell to create an SSH session.

 

Usage/Deployment Instructions

Step 1:  Access the Rancher in Azure Marketplace and click on Get it now button.

A screenshot of a computer

Description automatically generated A screenshot of a computer error

Description automatically generated

Click on Continue and then click on Create.

Step 2: Now to create a virtual machine, enter or select appropriate values for zone, machine type, resource group and so on as per your choice.

A screenshot of a computer

Description automatically generated

Graphical user interface, text, application, email

Description automatically generatedGraphical user interface, text, application, email

Description automatically generated

Graphical user interface, text, application, email

Description automatically generatedGraphical user interface, text, application, email

Description automatically generated

Graphical user interface, text, application, email

Description automatically generatedGraphical user interface, text, application, email

Description automatically generated

Click on Review + create.

Step 3:  The below window confirms that VM was deployed.

Graphical user interface, text, application, email

Description automatically generated

 

Step 4:  Open port 8080 in security group by going to resource group –

  1. Select your network security group.
  2. Select Inbound security rules from the left menu, then select Add.
  3. You can limit the Source as needed or leave the default of Any.
  4. You can limit the Destination as needed or leave the default of Any.
  5. Choose a common Service from the drop-down menu, TCP. You can also select Custom if you want to provide a specific port to use like Port_4000.
  6. Optionally, change the Priority or Name. The priority affects the order in which rules are applied: the lower the numerical value, the earlier the rule is applied.
  7. Select Add to create the rule.
  8. Limit the Source port range as 8080. 

Graphical user interface, text, application, email

Description automatically generated

 

Step 5: Open putty and connect with your machine. Add IP address of the running virtual machine.

Step 6: Login with user name and password that you provided during machine creation.

Once your Deployment is successful , follow the following Steps;

Step 1: Please open the following Security Ports in the instance:

 To access the Rancher user interface, open a web browser and type the server IP number and port in the URL bar following the syntax:

https://[server_ip]:[port]

 

Launch Rancher on Ubuntu.

Configure Rancher

Once you have accessed the platform, Rancher instructs you to set up the Admin user (one that has full control over Rancher).

1. Open the ADMIN drop-down menu and click Access Control.

Navigate to Access Control to configure Rancher.

2. Click the LOCAL button in the menu to move to the Local Authentication window.

Select LOCAL configuration from the access control menu.

 Provide the required information to set up an Admin user and click Enable Local Auth to confirm.

Set up an Admin User for Rancher.

Create a Custom Cluster

When creating a custom Kubernetes cluster on Rancher, you need to provision a Linux host (an on-premise virtual machine, a cloud-host VM or a bare metal server). Then, you can create your custom Kubernetes cluster.

Provision a Host

1. Open the INFRASTRUCTURE drop-down menu and select HOSTS.

Open Host menu on Rancher.

2.The instructions inform you that the host needs to have a supported version of Docker and allowed traffic to and from hosts on ports 500 and 4500. Start up the machine making sure it has all the specified prerequisites.

3. Rancher gives you an option to add a label to the host.

4. Provide the IP address that should be registered for this host.

Provide the IP address of the custom host you want to set up on Rancher.

 

5. Doing so generated a unique command which should be run on the specified host.

Copy the command that should be run on the host.

 

6. Copy and paste the command in the terminal window.

Pasting the host registration command in terminal.

 

7. Click Close and wait for the new host to appear on the Host screen.

Create a Custom Kubernetes Cluster

With the Linux host assigned, move on to creating a custom cluster.

1. Navigate to the Clusters page and click Add Cluster.

Adding a new cluster in Rancher.

2. Select Existing Nodes.

Selecting cluster type in Rancher.

3. Type a Cluster Name, and click Next.

Naming a cluster in Rancher.

4. Under Node Options, choose what roles you want the nodes to have (etcd, Control Plane, and/or Worker).

Customizing node options in Rancher.

5. In Cluster Options, chose the Kubernetes Version and the Network Provider:

Customizing the cluster options in Rancher.

6. Choose the cloud provider. If you do not have one, select None.

Selecting a cloud provider in Rancher.

7. Copy and paste the generated command on each worker node machine and wait for the cluster to start up.

Copying the command to register worker nodes in Rancher.

 

 

 

 

 

Submit Your Request

Captcha

Until now, small developers did not have the capital to acquire massive compute resources and ensure they had the capacity they needed to handle unexpected spikes in load. Amazon EC2 enables any developer to leverage Amazon’s own benefits of massive scale with no up-front investment or performance compromises. Developers are now free to innovate knowing that no matter how successful their businesses become, it will be inexpensive and simple to ensure they have the compute capacity they need to meet their business requirements.

The “Elastic” nature of the service allows developers to instantly scale to meet spikes in traffic or demand. When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.

 

Traditional hosting services generally provide a pre-configured resource for a fixed amount of time and at a predetermined cost. Amazon EC2 differs fundamentally in the flexibility, control and significant cost savings it offers developers, allowing them to treat Amazon EC2 as their own personal data center with the benefit of Amazon.com’s robust infrastructure.

When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.

Secondly, many hosting services don’t provide full control over the compute resources being provided. Using Amazon EC2, developers can choose not only to initiate or shut down instances at any time, they can completely customize the configuration of their instances to suit their needs – and change it at any time. Most hosting services cater more towards groups of users with similar system requirements, and so offer limited ability to change these.

Finally, with Amazon EC2 developers enjoy the benefit of paying only for their actual resource consumption – and at very low rates. Most hosting services require users to pay a fixed, up-front fee irrespective of their actual computing power used, and so users risk overbuying resources to compensate for the inability to quickly scale up resources within a short time frame.

 

You have complete control over the visibility of your systems. The Amazon EC2 security systems allow you to place your running instances into arbitrary groups of your choice. Using the web services interface, you can then specify which groups may communicate with which other groups, and also which IP subnets on the Internet may talk to which groups. This allows you to control access to your instances in our highly dynamic environment. Of course, you should also secure your instance as you would any other server.

 

Highlights

  • Multi-Cluster Management.
  • Support for Multiple Orchestration Engines.
  • Infrastructure Agnostic.
  • Application Catalog.
  • Scalability and High Availability.
  • Community and Support.

Application Installed