Releases: kubescape/operator
v0.2.4
Release v0.1.39
Release v0.1.25
Overview
Ticket: https://cyberarmor-io.atlassian.net/browse/SUB-1443
This PR adds support for scanning images from container registries which require authentication.
Up until now, this was only possible for scanning images at the registry, but not for image scanning within a cluster.
Before sending the scan command, we look for all registry scan secrets (those which start with kubescape-registry-scan
) and look for a match with the ImageTag (a strings.Contains
comparison). In such case, we add the credentials to the websocket command for kubevuln.
The documentation describes how to create such secret if it does not exist - https://hub.armosec.io/docs/registry-vulnerability-scan
A secret for example:
kind: Secret
apiVersion: v1
metadata:
name: kubescape-registry-scan-my-acr-secret
namespace: kubescape
type: Opaque
stringData:
registriesAuth: |
[
{
"registry": "myrepo.azurecr.io",
"username": "<username/clientID>",
"password": "<password/secret>",
"auth_method": "credentials"
}
]
Release v0.1.24
What this PR changes
This is a hacky way of using instance ID slugs more consistently.
This PR:
- uses slugs to store which instance IDs we manage
- properly passes the instance ID slug to Kubevuln
- adds logging for filtered SBOMs
Please notice the TODOs and missing error handling someplaces. This should be done at some point anyway.
Overview
Release v0.1.23
Overview
Fix typo in a TODO, trigger image build 🙄
Release v0.1.21
Overview
- Update go version
- Update packages
- Remove relevancy workflow
- Remove the master branch workflow
Release v0.1.18
Overview
Release v0.1.16
Overview
Release v0.1.14
Overview
On startup, trigger Kubescape with allcontrols
, nsa
, mitre
frameworks
Release v0.1.13
<!-- Please provide a brief overview of the changes made in this pull request. e.g. current behavior/future behavior --> <!-- ## Additional Information > Any additional information that may be useful for reviewers to know --> <!-- ## How to Test > Please provide instructions on how to test the changes made in this pull request --> <!-- ## Examples/Screenshots > Here you add related screenshots --> <!-- ## Related issues/PRs: Here you add related issues and PRs. If this resolved an issue, write "Resolved #<issue number> e.g. If this PR resolves issues 1 and 2, it should look as follows: * Resolved #1 * Resolved #2 --> <!-- ## Checklist before requesting a review put an [x] in the box to get it checked - [ ] My code follows the style guidelines of this project - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have performed a self-review of my code - [ ] If it is a core feature, I have added thorough tests. - [ ] New and existing unit tests pass locally with my changes **Please open the PR against the `dev` branch (Unless the PR contains only documentation changes)** -->