Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Provision Kubernetes on Citrix XenServer

License

NotificationsYou must be signed in to change notification settings

christus02/kubexen

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

You can now provision a Kubernetes cluster on aCitrix Xenserver using this tool. You can also specify the required CNI, node count and Kubernetes version.This is an Ansible based tool that usedKubeADM to bring up the Kubernetes Cluster.

This tool would create the Nodes in the XenServer for you and then install Kubernetes on them based on the parameters which you specify.

Pre-requisites:

  1. Required Packages
apt install python-pippip install ansiblepip install XenAPIapt install sshpassexport ANSIBLE_HOST_KEY_CHECKING=False
  1. VM Template needs to be created. This is a one time process. This step can be skipped, if you choose not to provision nodes.

A detailed guide on how to create a VM export is givenhere

Note Support for installing nodes from pre-built VM templates is work-in-progress.

Let the tool know your requirements for creating the Kubernetes cluster

Clone this repository and modify thevars/config.yml file according to your needs

https://github.com/christus02/kubexen.gitcd kubexen

Edit the vars/config.yml file. Below are some of the parameters to be changed.

Specify the Xen Server details in the below section

xenserver:  hostname: <IP/Hostname of the XenServer>  username: <Username of the XenServer>  password: <Password of the XenServer>

Provide the Free IPs in the XenServer management range. The Kubernetes nodes would be assigned these IPs after bring up.

The IPs should be specified as CIDR.

The First IP would be assigned to the Master Node

ip_config:  ip:  # Specify the IPs to be assigned for the nodes as CIDR (IP/PREFIX)  - 10.0.0.11/24 # The first IP would be considered as Master  - 10.0.0.12/24 # Worker Node 1  - 10.0.0.13/24 # Worker Node 2  gateway: 10.0.0.1

Choosing CNI:

You can provide the CNI to be installed in the below section.

cluster_configs:  # Possible CNI list:  # TODO  cni: 'flannel'

Choosing the Kubernetes Version:

You can provide the Kubernetes Version to be installed in the below section.

cluster_configs:  # Specify the Kubernetes version you wish to install  version: '1.18.0'

Save thevars/config.yml file and exit.

Create the Kubernetes Cluster

Now that you have updated thevars/config.yml file, run the Ansible playbook to provision VMs and create Kubernetes cluster

ansible-playbook kubexen.yml

Let the playbook run and in few more minutes your cluster would be UP and RUNNING.

Logging in to the Kubernetes Master

Login to the Master IP provided in thevars/config.yml with thevm.template_username andvm.template_password specified in thevars/config.yml file

After logging in, you can execute the usualkubectl commands.

Your Kubernetes cluster is now UP and READY.

Delete a Kubernetes Cluster

Make sure thevars/config.yml is not changed and execute the below command to delete the created Kubernetes cluster

ansible-playbook kubexen.yml -t delete

The Kubernetes cluster can also be deleted by manually deleting the VMs from the XenCenter.

DNS Resolution

All the nodes in the Kubernetes cluster can reach each other using the hostnames. This is made possible as the hostnames are configured asxip.io domain names.

Work-In-Progress:

  1. Support all possible CNI
  2. Option to bring up just Kubernetes without provisioning VMs
  3. Make this tool Docker Ready
  4. Support for importing a VM template from URL

[8]ページ先頭

©2009-2025 Movatter.jp