Releases: blackducksoftware/opssight-connector
Releases · blackducksoftware/opssight-connector
2.2.5
2.2.4
Version 2.2.4
July 2019
- Support for Black Duck 2019.6.0 and later
2.2.3
Version 2.2.3
April 2019
- Supports Kubernetes 1.14
- Supports OpenShift 3.11
- Moves the storage of private Docker registry credentials from config map to Kubernetes secrets
- Adds support for adding Black Duck credentials for each Black Duck instance
2.2.2
2.2.1
Version 2.2.1
- Improved login handling for Black Duck instance in OpsSight core
2.2.0
Version 2.2.0
- Improved testing coverage through "skyfire" automated testing
- Moved Synopsys Operator out of OpsSight Connector and into an independent repo
- Improved documentation
2.1.0
Version 2.1.0
- Introduced namespace scanning filter, which limits scanning to namespaces with specified labels
- Introduced Black Duck Operator, which leverages Custom Resource Definitions (CRDs) to simplify deployment and management of Black Duck components
- Ability to distribute OpsSight data across multiple Black Duck instances for improved scalability
- Added support for Black Duck 5.0
- Fixed an issue in which images added by SHA (rather than by Tag) are scanned duplicately
2.1.0-alpha
rename blackduck-protoform to blackduck-operator
2.1.0-beta
Update README.md
2.0.3
Version 2.0.3
- Added support for Red Hat OpenShift 3.10
- Introduced the following installation command-line parameter:
-a,--annotation-interval-seconds option
This parameter determines how often the OpsSight Connector polls for new annotation data. The default value is 30 seconds. If you would like less latency in the emergence of updated annotations and labels, you can reduce this value, at the expense of slightly greater resource usage. - Built with latest container updates for improved security rating in Red Hat Container Catalog.
- Fixed bug that caused the OpsSight Connector to be unable to pull images from a registry, causing the OpsSight Connector to stop scanning new images.