kubescape/kubescape
### [`v2.0.180`](https://togithub.com/kubescape/kubescape/releases/tag/v2.0.180)
[Compare Source](https://togithub.com/kubescape/kubescape/compare/v2.0.179...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](https://togithub.com/kubescape/kubescape/issues/997)
#### This PR fixes:
- Resolved [#980](https://togithub.com/kubescape/kubescape/issues/980)
- Resolved [#981](https://togithub.com/kubescape/kubescape/issues/981)
### [`v2.0.179`](https://togithub.com/kubescape/kubescape/releases/tag/v2.0.179)
[Compare Source](https://togithub.com/kubescape/kubescape/compare/v2.0.178...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](https://togithub.com/kubescape/github-action) or running Kubescape as a microservice.
**The output summary table will always be displayed**
#### This releas fixes:
- Resolved [#953](https://togithub.com/kubescape/kubescape/issues/953)
Configuration
📅 Schedule: Branch creation - "before 2am" in timezone Etc/UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
v2.0.178->v2.0.180Release Notes
kubescape/kubescape
### [`v2.0.180`](https://togithub.com/kubescape/kubescape/releases/tag/v2.0.180) [Compare Source](https://togithub.com/kubescape/kubescape/compare/v2.0.179...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](https://togithub.com/kubescape/kubescape/issues/997) #### This PR fixes: - Resolved [#980](https://togithub.com/kubescape/kubescape/issues/980) - Resolved [#981](https://togithub.com/kubescape/kubescape/issues/981) ### [`v2.0.179`](https://togithub.com/kubescape/kubescape/releases/tag/v2.0.179) [Compare Source](https://togithub.com/kubescape/kubescape/compare/v2.0.178...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](https://togithub.com/kubescape/github-action) or running Kubescape as a microservice. **The output summary table will always be displayed** #### This releas fixes: - Resolved [#953](https://togithub.com/kubescape/kubescape/issues/953)Configuration
📅 Schedule: Branch creation - "before 2am" in timezone Etc/UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.