48035e3a7e
* Drop CI jobs related to canal According to the canal github[1] the repo is not maintained over 5 years. In addition, the README says Originally, we thought we might more deeply integrate the two projects (possibly even going as far as a rebranding!). However, over time it became clear that that wasn't really necessary to fulfil our goal of making them work well together. Ultimately, we decided to focus on adding features to both projects rather than doing work just to combine them. So we don't need to run CI jobs related to the canal at this situation. [1]: https://github.com/projectcalico/canal * Update ci.md |
||
---|---|---|
.. | ||
cloud_playbooks | ||
common | ||
files | ||
local_inventory | ||
scripts | ||
support | ||
templates | ||
testcases | ||
Makefile | ||
README.md | ||
ansible.cfg | ||
requirements-2.11.txt | ||
requirements-2.12.txt | ||
requirements.txt | ||
run-tests.sh | ||
shebang-unit |
README.md
Kubespray cloud deployment tests
Amazon Web Service
Calico | Flannel | Weave | |
---|---|---|---|
Debian Jessie | |||
Ubuntu Trusty | |||
RHEL 7.2 | |||
CentOS 7 |
Test environment variables
Common
Variable | Description | Required | Default |
---|---|---|---|
TEST_ID |
A unique execution ID for this test | Yes | |
KUBE_NETWORK_PLUGIN |
The network plugin (calico or flannel) | Yes | |
PRIVATE_KEY_FILE |
The path to the SSH private key file | No |
AWS Tests
Variable | Description | Required | Default |
---|---|---|---|
AWS_ACCESS_KEY |
The Amazon Access Key ID | Yes | |
AWS_SECRET_KEY |
The Amazon Secret Access Key | Yes | |
AWS_AMI_ID |
The AMI ID to deploy | Yes | |
AWS_KEY_PAIR_NAME |
The name of the EC2 key pair to use | Yes | |
AWS_SECURITY_GROUP |
The EC2 Security Group to use | No | default |
AWS_REGION |
The EC2 region | No | eu-central-1 |
Use private ssh key
Key
openssl pkcs12 -in gce-secure.p12 -passin pass:notasecret -nodes -nocerts | openssl rsa -out gce-secure.pem
cat gce-secure.pem |base64 -w0 > GCE_PEM_FILE`