This repository has been archived by the owner on Oct 9, 2024. It is now read-only.
INT-2121 - Fetch kube_bench findings #31
Open
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
eXtremeX
force-pushed
the
feature/kube-bench-findings
branch
from
7808c36
to
5558eef
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is a work in progress, currently, this code change handles the
kube_benchoutputresult.jsonfile that contains the findings.For this to be feature complete we also require the
.ymlfile to correctly tie both containers (graph_integrationandkube_bench) preferably usingkubexitwith correct order - but there's some issue with that currently - the.ymlidea I have experimented with can be found at./configs/k8s/cronjobClusterKubeBench.yml.@austinkelleher