Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PR] Test end-to-end with the real cluster (minikube) #54

Closed
kopf-archiver bot opened this issue Aug 18, 2020 · 0 comments
Closed

[PR] Test end-to-end with the real cluster (minikube) #54

kopf-archiver bot opened this issue Aug 18, 2020 · 0 comments
Labels
archive automation CI/CD: testing, linting, releasing automatically

Comments

@kopf-archiver
Copy link

kopf-archiver bot commented Aug 18, 2020

A pull request by nolar at 2019-05-03 13:39:15+00:00
Original URL: zalando-incubator/kopf#54
Merged by nolar at 2019-05-22 11:53:10+00:00

Issue : #52

With this, the framework is tested for the very basic things, which can be missed in the unit-test: that it starts and works at all, and communicates with the Kubernetes API normally: both for watching and for patching.

Previously, we had an internal incident when the operator failed to start since the RBAC permissions were missing, but the unit-tests were all green. Now, such things should be detected.

The e2e tests are executed at the end, since they are usually slow (tens of seconds), and want the regular unit-tests to provide the results fast.

More e2e tests will be added in separate PRs. Currently, it is only a supporting infrastructure for this kind of tests, and a demo with the "./examples/" (also to check that the examples are still valid).


Kubernetes 1.11.x is disabled since Minikube/kubeadm fails on the CRI preflight checks, and neither Kubernetes nor Minikube are our system-under-test — the framework and its examples are the the system-under-test.

Kubernetes 1.10.x is disabled due to conflicting behaviour of spec.version in CRD files: either 1.10 or 1.14 fails, but 1.14 is valuable as the future release, so 1.10 can be sacrificed (to not introduce the legacy on the project start).


This is how it looks in Travis (as an example): https://travis-ci.org/nolar/kopf/builds/527762283

image
image

@kopf-archiver kopf-archiver bot closed this as completed Aug 18, 2020
@kopf-archiver kopf-archiver bot changed the title [archival placeholder] [PR] Test end-to-end with the real cluster (minikube) Aug 19, 2020
@kopf-archiver kopf-archiver bot added the automation CI/CD: testing, linting, releasing automatically label Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
archive automation CI/CD: testing, linting, releasing automatically
Projects
None yet
Development

No branches or pull requests

0 participants