Releases: kubescape/kubescape
Release v2.1.3
Overview
- Fixes for krew plugin submission
- Remove the host scanner from the excluded namespaces list
- Update the list of default frameworks to AllControls, NSA. MITRE
Additional Information
Remove the host scanner from the excluded namespaces list
From now on, the host scanner will be scanned but excluded
Update the list of default frameworks to AllControls, NSA. MITRE
In the current behavior, when running lubescape scan
, Kubescape will fetch all of the available frameworks.
In this PR will are changing the behavior so Kubescape will fetch a specific list of chosen frameworks.
e.g.
Kubescape will scan the AllControls
, NSA
. MITRE
frameworks when running
kubescape scan --logger debug
Release v2.1.2
Release v2.1.1
Renaming the files (#1079) * Renaming the files Signed-off-by: David Wertenteil <dwertent@armosec.io> * Removing un-used code Signed-off-by: David Wertenteil <dwertent@armosec.io> --------- Signed-off-by: David Wertenteil <dwertent@armosec.io>
Release v2.1.0
Release v2.0.183
Overview
- Supporting
kubescape fix
command - Supporting scanning Azure remote repositories
- Supporting scanning Bitbucket repositories
- Fixed many minor and blocking issues
- Supporting
--create-account
flag - This will be submitting data to the ARMO platform without pre-registering in the platform
Examples
Fix command
- Run the scan command on a local directory:
kubescape scan <local directory> --format=json --format-version=v2 --output=results
- Run the
fix
command:kubescape fix results.json
You can find here some more information
Scanning a Bitbucket repo
kubescape scan git@bitbucket.org:matthyx/ks-testing-public.git
Scanning an Azure repo
kubescape scan git@ssh.dev.azure.com:v3/dwertent/ks-testing-public/ks-testing-public
This PR fixes:
Release v2.0.182
Merge pull request #1027 from kubescape/hot-fix-v2.0.181 setCloudMetadata only when scanning a cluster
Release v2.0.181
Hot-fix for windows URL path parsing.
Release v2.0.180
Overview
- Updated go version to
1.19
- Recognizing AKS cluster
- Alpha - Adding support for prioritizing the failed resources based on attack vectors (
--print-attack-tree
) - Enabled golangci linter in CI
Screenshots
A screenshot for prioritizing the failed resources can be seen in #997
This PR fixes:
Release v2.0.179
Overview
- Deprecating support for scanning by control name - from now the
kubescape scan control
will support only control IDs - Codebase cosmetic changes
- CLI output cosmetic changes
- Support output in multiple formats to multiple files
- Update maintainers
- Adopt CNCF Code of Conduct
Details
GitLab scanning remote repository support
Kubescape will support scanning gitlab repositories without the need of pre-cloning
e.g.
kubescape scan https://gitlab.com/dwertent/testing.git
Set the
GITLAB_TOKEN
environment for scanning private repositories
Deprecating support for scanning by control name
From now on, we will not support scanning control by it's name, you must use the control ID.
Please contact us if you think we should revise this decision.
You can list all of the controls and IDs using the list
command:
kubescape list controls
Support output in multiple formats to multiple files
Scan and save the results in multipule formats:
kubescape scan -f html,junit -o results
This will come in handy when using the Kubescape GitHub actions or running Kubescape as a microservice.
The output summary table will always be displayed
This releas fixes:
- Resolved #953
Release v2.0.178
Merge pull request #961 from kubescape/dev change linux runner to 20.04 instead of ubuntu-latest (#960)