Add an ansible tag to play only the ETCD Check tasks and document the use of the tag in the "manage-etcd" Doc.

• Explain the technical terms : explain in more detail the technical environments to use to install kuberntes to show the advantages and disadvantages of each choice of technical environment.

Get log rotation working inside ILKE.

Explain what the vagrantfile is for in /labs/all-in-one/ and /labs/multi-nodes/

Today ILKE can't uninstall Kubernetes Clusters ETCD installed by ILKE by itself.
We need to add the possibility to uninstall all ETCD components deployed with ILKE to help users to uninstall Kubernetes and clean their hosts.

We will use a global boolean parameter "ilke.global.uninstall" set to "True" when ILKE must delete/uninstall all K8S/ILKE components.

Delete/Clean on ETCD hosts

• ETCD PKI files
• ETCD Service Definition
• ETCD binaries
• ETCD data-dir

Today ILKE can't delete Storage Data Path used by OpenEBS when we delete/clear our ILKE/K8S cluster installation.
We need to add the possibility to uninstall all OpenEBS/Storage data_path deployed with ILKE to help users to uninstall Kubernetes and clean their hosts.

We will use a global boolean parameter "ilke.global.uninstall" set to "True" when ILKE must delete/uninstall all K8S/ILKE components.

Storage Hosts:

Delete OpenEBS volume "data_path" (Jiva and HostPath)

Add the possibility of removing ILKE components by adding a role to do the overall removal of the distribution ILKE.

Add the monitoring configuration using Grafana and Prometheus (Configure Node Exporter and Grafana Dashboard).

Today ILKE can't uninstall Kubernetes Clusters components installed by ILKE by itself.
We need to add the possibility to uninstall all kubernetes components deployed with ILKE to help users to uninstall Kubernetes and clean their hosts.

We will use a global boolean parameter "ilke.global.uninstall" set to "True" when ILKE must delete/uninstall all K8S/ILKE components.

Delete/Clean on Master, Workers and Storage Hosts

• K8S PKI files
• K8S Services Definitions
• K8S binaries
• K8S logs
• Kubelet Data Directory

correct typos

Add documentation describing how Gatekeeper works.

Describe the bug
Instead of keeping with the standard convention of node-role.kubernetes.io/master=true the masters are now using a different key (NoSchedulabe) which causes upgraded clusters from previous versions to break and manual node edits to fix

"This is a specification for recognizing contributors to an open source project in a way that rewards each and every contribution, not just code."

Note : /all-contributors/all-contributors
https://github.com/all-contributors/all-contributors

Hi,

Is your feature request related to a problem? Please describe.

Actually, ILKE use "compliance-checks" ansible role, located at "./roles/compliance-checks" to validate parameters (located at ".group_vars/all.yaml" file) and K8S infrastructure (located at "hosts" file).

This role is not up-to-date with our new variables and need an major update to help users to validate their variables before ILKE install K8S cluster.

Describe the solution you'd lilke
Please, update "compliance-checks" role to check ILKE parameters/infrastructure set by users according to the documentation file located at https://github.com/ilkilabs/ilke/blob/master/docs/instructions.md#ilke-parameters

Note: The role already exist but need a major update !

Thanks !

Correction of misspellings in instructions.md and more generally in the whole docs.

**Is your feature request related to a problem?
IKE-Core is a set of Ansible playbooks that are used to deploy a Kubernetes Cluster with CNCF ecosystem.
In some cases, Ansible installed by users is broken or doesn't have the required dependences....
Describe the solution you'd like
Deploy Ansible and all its dependencies needed by IKE as "Python Virtual Environment" so it will be easier for IKE users to setup Ansible and required tools without take the risk to break existing Python/Ansible environments

Additional context
Ideally, Ansible and all dependences have to be pre-installed in a pyhton virtual environment and distributed as archive stored in IKE.
We can also juste provide "requirement.txt" file that contains all requirements needed for Ansible/Ike

This issue is used to add contributors to ILKE project

Add gatekeeper installation and pods gatekeeper verification.

• Explain that using the vagrantfile is just a way to test the ilke distribution in a local environment, with a local version only .

@all-contributors please add @bryanILKI for code, maintenance and doc

Reloader - https://github.com/stakater/Reloader

This is an amazing project that wath for Secret/ConfigMap changes and update associated DaemonSet/Deployments/StatefulSet/...

Pls, add it to ILKE and explain how to use in in the doc

Thanks!

Improve the presentation of ReadMe by adding for example: (Center title, Emojies, Gif / video presentation).

• Explain the installation procedure according to the OS for each operating system chosen : explain the required commands specific to each os to be able to install the ilke distribution

Rename AgoraKube to ILKE in /ilke/LOCAL_ENVIRONMENT.md

Hello,

Please Add CII badge to README

Today ILKE can't uninstall Container Engines components installed by ILKE by itself. (And their associated Config files and data)
We need to add the possibility to uninstall all Container Engine components deployed with ILKE to help users to uninstall Kubernetes and clean their hosts.

We will use a global boolean parameter "ilke.global.uninstall" set to "True" when ILKE must delete/uninstall all K8S/ILKE components.

Delete/Clean on Master, Workers and Storage Hosts

• Container Engine binaries (Containerd or Docker)
• Container Engine config files (Containerd or Docker)
• Container Engine logs
• Container Engine Data Directory
• All Container Network interfaces presents on the host

Hello,
Describe the bug
At IKE we use file "group_vars/all.yaml" to configure Kubernetes installation.
In some OS, and for some Python release, variables in dictionaries ending with ". update" are not allowed and produce the following error when they are called:

<built-in method update of dict object at 0x7f4b2dffc940>

This error occurs on Ubuntu 20.04 with Ansible 2.10.5

resolution

Just renaming all dict variables ending with ".update" and their associated calls in IKE code (file /group_vars/all.yaml, and all files in roles/ sub-directories ) by ".upgrade" will resolve this Issue.

Thx for help !

The compliance-checks role is not totaly up-to-date with our new variables and need an major update to help users to validate their variables before ILKE install K8S cluster.

Note: The role already exist but need a major update !

@all-contributors please add @pierreilki for projectManagement, code, mentoring and doc