Use VMware Harbor registry for flow-aggregator Docker image #1650
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
antoninbas
force-pushed
the
feature/flow-aggregator
branch
from
0cab885
to
a3f0042
Compare
antoninbas
force-pushed
the
use-vmware-harbor-registry-for-flow-aggregator-image
branch
from
85d6737
to
65893e8
Compare
Codecov Report
@@ Coverage Diff @@
## feature/flow-aggregator #1650 +/- ##
==========================================================
Coverage ? 62.00%
==========================================================
Files ? 181
Lines ? 15411
Branches ? 0
==========================================================
Hits ? 9556
Misses ? 4836
Partials ? 1019
Flags with carried forward coverage won't be shown. Click here to find out more. |
Changes are the same as in antrea-io#1617 but for the antrea/flow-aggregator Docker image. There was also a typo in the flow-aggregator YAML: the image key didn't match the one used in generate-manifest-flow-aggregator.sh when invoking kustomize.
antoninbas
force-pushed
the
use-vmware-harbor-registry-for-flow-aggregator-image
branch
from
65893e8
to
3fc6580
Compare
antoninbas
deleted the
use-vmware-harbor-registry-for-flow-aggregator-image
branch
srikartati
pushed a commit
to srikartati/antrea
that referenced
this pull request
Dec 17, 2020
…o#1650) Changes are the same as in antrea-io#1617 but for the antrea/flow-aggregator Docker image. There was also a typo in the flow-aggregator YAML: the image key didn't match the one used in generate-manifest-flow-aggregator.sh when invoking kustomize.
srikartati
pushed a commit
to srikartati/antrea
that referenced
this pull request
Dec 19, 2020
…o#1650) Changes are the same as in antrea-io#1617 but for the antrea/flow-aggregator Docker image. There was also a typo in the flow-aggregator YAML: the image key didn't match the one used in generate-manifest-flow-aggregator.sh when invoking kustomize.
srikartati
pushed a commit
to srikartati/antrea
that referenced
this pull request
Dec 21, 2020
…o#1650) Changes are the same as in antrea-io#1617 but for the antrea/flow-aggregator Docker image. There was also a typo in the flow-aggregator YAML: the image key didn't match the one used in generate-manifest-flow-aggregator.sh when invoking kustomize.
srikartati
pushed a commit
to srikartati/antrea
that referenced
this pull request
Dec 21, 2020
…o#1650) Changes are the same as in antrea-io#1617 but for the antrea/flow-aggregator Docker image. There was also a typo in the flow-aggregator YAML: the image key didn't match the one used in generate-manifest-flow-aggregator.sh when invoking kustomize.
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.
Changes are the same as in
#1617 but for the
antrea/flow-aggregator Docker image.
There was also a typo in the flow-aggregator YAML: the image key didn't
match the one used in generate-manifest-flow-aggregator.sh when invoking
kustomize.