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
images: drop the kvstoremesh dockerfile #28961
Merged
Merged
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
Now that kvstoremesh got merged into the clustermesh-apiserver, and the CI changes got applied, let's also drop the kvstoremesh dockerfile. Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
giorio94
added
kind/cleanup
This includes no functional changes.
area/clustermesh
Relates to multi-cluster routing functionality in Cilium.
release-note/misc
This PR makes changes that have no direct user impact.
area/build
Anything to do with the build, more general then area/CI
labels
Nov 3, 2023
/test |
1 similar comment
/test |
jibi
approved these changes
Nov 10, 2023
maintainer-s-little-helper
bot
added
the
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
label
Nov 10, 2023
mhofstetter
added a commit
to mhofstetter/cilium
that referenced
this pull request
Dec 15, 2023
Currently, vulnerability scanning fails because kvstoremesh no longer exists on v1.15. It has been removed with cilium#28961 There are already kvstoremesh exclusions for v1.12 & v1.13. This commit inverts the exclusion to an inclusion for v1.14, as this is the only branch that contains the kvstoremesh. Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
julianwiedmann
pushed a commit
that referenced
this pull request
Dec 18, 2023
Currently, vulnerability scanning fails because kvstoremesh no longer exists on v1.15. It has been removed with #28961 There are already kvstoremesh exclusions for v1.12 & v1.13. This commit inverts the exclusion to an inclusion for v1.14, as this is the only branch that contains the kvstoremesh. Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
ldelossa
pushed a commit
to ldelossa/cilium
that referenced
this pull request
Feb 29, 2024
[ upstream commit 7661353 ] Currently, vulnerability scanning fails because kvstoremesh no longer exists on v1.15. It has been removed with cilium#28961 There are already kvstoremesh exclusions for v1.12 & v1.13. This commit inverts the exclusion to an inclusion for v1.14, as this is the only branch that contains the kvstoremesh. Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/build
Anything to do with the build, more general then area/CI
area/clustermesh
Relates to multi-cluster routing functionality in Cilium.
kind/cleanup
This includes no functional changes.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/misc
This PR makes changes that have no direct user impact.
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.
Now that kvstoremesh got merged into the clustermesh-apiserver, and the CI changes got applied, let's also drop the kvstoremesh dockerfile.