Skip to content
This repository was archived by the owner on Nov 9, 2022. It is now read-only.
This repository is currently being migrated. It's locked while the migration is in progress.

e2e: Run operator locally with go run #178

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

darkowlzz
Copy link
Contributor

@darkowlzz darkowlzz commented Oct 5, 2019

This runs the e2e operator-sdk tests (non-OLM) with go run, instead of
running in a container.
Container image is built only for OLM based test setup.
Also, uses the new kind load command to upload the container image from
host to a KinD environment.

This runs the e2e operator-sdk tests (non-OLM) with go run, instead of
running as a container.
Container image is built only for OLM bases test setup.
Also, uses the new kind load command to upload the container image from
host to a KinD environment.
@darkowlzz
Copy link
Contributor Author

There may be an issue when running the operator locally which results in the node-controller failing to update the node labels.

@croomes
Copy link
Contributor

croomes commented Oct 7, 2019

LGTM but failing test?

@darkowlzz
Copy link
Contributor Author

When the operator is run this way, it's operating from outside the KinD environment. The operator controllers cannot connect to the storageos server running inside the KinD environment. This works fine for openshift test job as openshift is deployed directly on the host. A workaround for this would be to create a proxy to storageos server inside KinD from the host. We already do something similar in the e2e test for node controller tests. We can move the proxy creation before running any test.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants