Migrate image to fluentd.image and sumologic.setup.job.image #1148
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pmalek-sumo
requested review from
andrzej-stencel,
frankreno,
kkujawa-sumo,
perk-sumo and
sumo-drosiek
as code owners
pmalek-sumo
force-pushed
the
separate-setup-and-fluentd-images
branch
from
3048a93
to
0f8a917
Compare
|
Remove |
pmalek-sumo
force-pushed
the
separate-setup-and-fluentd-images
branch
from
0f8a917
to
04630a4
Compare
pmalek-sumo
force-pushed
the
separate-setup-and-fluentd-images
branch
from
04630a4
to
caa9b9b
Compare
tests/upgrade_script/static/prometheus_service_monitors.input.yaml
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
imagetosumologic.setup.job.imageand tofluentd.image(for now use the same image but prepare a separate image for setup job in a different PR)yqarguments which changed in 3.4.0 and now need to be provided differently - we might actually end up remove this script as it's only relevant to 1.x branchesyqin vagrant and on CI to 3.4.1Testing performed