-
Notifications
You must be signed in to change notification settings - Fork 197
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
[operator] Cannot create vulnerability report because name is too long #288
Comments
👋 @pcheliniy We're aware of this limitation and actually we plan to change the way we name and store VulnerabilityReports. TL;DR; We're thinking about naming VulnerabilityReports by image digest. By doing that we'll eliminate the problem that you encountered. What's more, we'll store reports in more efficient way in case multiple workloads in the same namespace use the same image digest: |
That's a really good idea. |
Related to #280 |
We do have scan by image digest on our roadmap. However, we can provide a short term solution, which is similar to what we did for configuration auditing. The idea was to fallback to the In the reported case the vulnerability report will look as follows: apiVersion: aquasecurity.github.io/v1alpha1
kind: VulnerabilityReport
metadata:
annotations:
starboard.resource.name: core-competency-matrix-production-prometheus-redis-exporter-6c4765756
creationTimestamp: "2021-10-26T08:22:52Z"
generation: 1
labels:
resource-spec-hash: 55cc76fd7f
starboard.container.name: redis-exporter-dbc86
starboard.resource.kind: ReplicaSet
starboard.resource.name-hash: 7d4f75bb65
starboard.resource.namespace: default
name: replicaset-5f4f96cd55
namespace: default
ownerReferences:
- apiVersion: apps/v1
blockOwnerDeletion: false
controller: true
kind: ReplicaSet
name: core-competency-matrix-production-prometheus-redis-exporter-6c4765756
uid: 933f84ad-d14c-4c84-a1fd-1f4dace4d0e7
resourceVersion: "16301"
uid: 8d066286-f53b-431a-a3db-6a05b638b510
report:
artifact:
repository: oliver006/redis_exporter
tag: v1.29.0
registry:
server: index.docker.io
scanner:
name: Trivy
vendor: Aqua Security
version: 0.20.0
summary:
criticalCount: 0
highCount: 0
lowCount: 0
mediumCount: 0
noneCount: 0
unknownCount: 0
updateTimestamp: "2021-10-26T08:22:52Z"
vulnerabilities: [] |
Resolves: #288 Signed-off-by: Daniel Pacak <pacak.daniel@gmail.com>
What steps did you take and what happened:
We widely use various public helm charts and sometimes helpers in charts can generate very long resource names :)
Unfortunately, it leads to the following problem:
Environment:
The text was updated successfully, but these errors were encountered: