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

Use image overrides when deploying #924

Merged
merged 5 commits into from
Aug 31, 2022
Merged

Use image overrides when deploying #924

merged 5 commits into from
Aug 31, 2022

Conversation

mkolesnik
Copy link
Collaborator

@mkolesnik mkolesnik commented Aug 20, 2022

Use image overrides, based on $PRELOAD_IMAGES, for determining which
exact images to override.

This will allow us to test just the images that we want to test, and use
the default images elsewhere.

A dev can still specify specific images, e.g.
make deploy PRELOAD_IMAGES='submariner-gateway submariner-operator'

Resolves: #915

Signed-off-by: Mike Kolesnik [email protected]

@mkolesnik mkolesnik added the e2e-projects Run E2E tests in each consuming project label Aug 20, 2022
@submariner-bot
Copy link

🤖 Created branch: z_pr924/mkolesnik/join-overrides

@mkolesnik mkolesnik changed the title Use image overrides when deploying with operator Use image overrides when deploying Aug 22, 2022
Use image overrides, based on `$PRELOAD_IMAGES`, for determining which
exact images to override.

This will allow us to test just the images that we want to test, and use
the default images elsewhere.

A dev can still specify specific images, e.g.
`make deploy PRELOAD_IMAGES='submariner-gateway submariner-operator'`

Signed-off-by: Mike Kolesnik <[email protected]>
Similarly to using image overrides in operator based deployments -
use image overrides, based on `$PRELOAD_IMAGES`, for determining which
exact images to override.

Signed-off-by: Mike Kolesnik <[email protected]>
Each project should determine it's own images to preload.
Needed images are still preloaded when using specific deployments, such
as `globalnet` or `lighthouse`.

Signed-off-by: Mike Kolesnik <[email protected]>
@mkolesnik mkolesnik requested a review from skitt August 22, 2022 08:32
@mkolesnik mkolesnik marked this pull request as ready for review August 30, 2022 07:44
@tpantelis tpantelis enabled auto-merge (rebase) August 31, 2022 13:17
@tpantelis tpantelis merged commit 47a76d7 into submariner-io:devel Aug 31, 2022
@submariner-bot
Copy link

🤖 Closed branches: [z_pr924/mkolesnik/join-overrides]

@dfarrell07
Copy link
Member

dfarrell07 commented Aug 31, 2022

This seems to have broken the System Tests workflow in the Operator repo.

To prevent such issues in the future, maybe we should add those tests to the Consuming Projects tests here (maybe under the e2e-projects label).

Deployment (globalnet)

[14:21:34.055] [dir=submariner-operator; cl=cluster1; fn=validate_equals]$ jq -r -M .spec.repository /tmp/submariner.cluster1.json
[cluster1] Expected 'localhost:5000' but got 'quay.io/submariner'

@mkolesnik
Copy link
Collaborator Author

This seems to have broken the System Tests workflow in the Operator repo.

To prevent such issues in the future, maybe we should add those tests to the Consuming Projects tests here (maybe under the e2e-projects label).

Deployment (globalnet)

[14:21:34.055] [dir=submariner-operator; cl=cluster1; fn=validate_equals]$ jq -r -M .spec.repository /tmp/submariner.cluster1.json
[cluster1] Expected 'localhost:5000' but got 'quay.io/submariner'

Yes that might be wise, anyhow I'll fix the tests

@mkolesnik
Copy link
Collaborator Author

Fix for operator system tests - submariner-io/submariner-operator#2222

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2e-projects Run E2E tests in each consuming project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use image overrides when deploying
6 participants