-
**Why is this needed**:
There is many places in synopsysctl where we expose parameters that a customer should not worry about changing. Currently, there are `43 flags` for `synopsysctl create …
-
- [x] Pass in JSON but make the path configurable
- [ ] The config maps still have names corresponding to the old names like perceptor, perceivers, etc. These need to be updated to correspond to the…
-
> time="2018-03-13T15:44:29Z" level=error msg="unable to update annotations/labels for pod default:sti-ruby-1-build: pods \"sti-ruby-1-build\" is forbidden: unable to validate against any security con…
-
**What would you like to be added**: #1000 Commands & resource to deploy the new perceivers
**Why is this needed**: Customers use Quay and Artifactory for storing their images
-
**What happened**:
OpsSight service that are exposed using NODEPORT is not working
**What you expected to happen**:
Need to access the prometheus metrics and opssight model using NODEPORT
**Ho…
-
**Is your feature request related to a problem? Please describe.**
Currently only 1 deployment method is supported for OpsSight. Move it to same structure as blackduck and alert
rrati updated
5 years ago
-
**What would you like to be added**:
Update the image download scripts to support newer versions of hub, opssight, alert
**Why is this needed**:
To a user who wants to load images into a private …
rrati updated
5 years ago
-
One you deploy the operator, there is no easy way for customers to determine:
* what scope Operator was deployed with
* what products (black duck, alert, opssight) were enabled when Operator was dep…
-
**What would you like to be added**:
When desired state is stop, scaled down everything to 0 as well as don't delete the PVC for both blackduck and alert.
Related to PR #357
**Why is thi…
-
**What happened**:
Internally, alert creation fails the first time due to namespace not being there in the cr's `namespace` for crudupdater
**How to reproduce it (as minimally and precisely …