Age | Commit message (Collapse) | Author | Files | Lines |
|
So far Molecule framework setup allowed full rke cluster deployment
in testing env but since rke cluster often fails to deploy in resource
constrained CI environment this change switches testing strategy to
only simulate 'rke up' operation.
Change-Id: Ia221da6666d558e086cd24155f5bd81237d82388
Issue-ID: OOM-2665
Signed-off-by: Bartek Grzybowski <b.grzybowski@partner.samsung.com>
|
|
Number of kubernetes nodes created by rke role tests
was limited to 1 - higher number caused resource exhaustion
in CI worker (8gb memory limit).
Verifier timeout was increased in routine where pod
readiness is checked.
Change-Id: I2c30aa999b92c4ceddccf682c4f918e953da2621
Signed-off-by: Bartek Grzybowski <b.grzybowski@partner.samsung.com>
Issue-ID: OOM-2257
|
|
Etcd cluster is now placed in members of kubernetes-etcd group instead
of kubernetes-node.
Due to defaults, it means infra is the only etcd
by default.
Change-Id: Iae05a42442849e4a248d73c2d78f5e2b0eae7255
Issue-ID: OOM-1778
Signed-off-by: Michal Zegan <m.zegan@samsung.com>
|
|
Rke playbook/role is modified to take advantage of the new group structure.
Namely, all members of kubernetes group are treated as cluster members
independent of their role.
The role itself is selected in cluster.yml.j2 template
based on actual membership in either kubernetes-node
or kubernetes-control-plane group.
Change-Id: I9a5bbfd090aff17018a610a01d6f88d848fc26c4
Issue-ID: OOM-1778
Signed-off-by: Michal Zegan <m.zegan@samsung.com>
|
|
This change adds molecule tests for the rke role, and
modifies the rke role itself to be more idempotent/to
pass linter.
Note that this molecule test case uses a separate
role to install docker in containers, that runs
docker daemon inside of them instead of using host docker.
Issue-ID: OOM-1778
Change-Id: I875f3ff2ab961e5428acee5a02287a8d2d6e9969
Signed-off-by: Michal Zegan <m.zegan@samsung.com>
|