https://github.com/blackducksoftware/opssight-connector

OpsSight Connector documentation
https://github.com/blackducksoftware/opssight-connector

cloud-native kubernetes ops pod security

Last synced: 3 months ago
JSON representation

OpsSight Connector documentation

• Host: GitHub
• URL: https://github.com/blackducksoftware/opssight-connector
• Owner: blackducksoftware
• License: apache-2.0
• Created: 2018-03-12T20:26:53.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2021-09-09T18:53:27.000Z (about 3 years ago)
• Last Synced: 2024-05-30T06:04:47.428Z (5 months ago)
• Topics: cloud-native, kubernetes, ops, pod, security
• Language: Go
• Homepage: https://github.com/blackducksoftware/opssight-connector/wiki
• Size: 127 MB
• Stars: 16
• Watchers: 8
• Forks: 9
• Open Issues: 12
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
## Overview

The Black Duck OpsSight Connector provides software composition analysis of open-source components of containers in OpenShift v3.x and Kubernetes clusters.

Pre-existing images and pods are automatically discovered, scanned and monitored. When a new image or pod is discovered, the OpsSight Connector kicks off a scan engine container to perform the scan and upload the results to your Black Duck instance.

For more information, click the [Wiki tab](https://github.com/blackducksoftware/opssight-connector/wiki).

## Getting involved

We expect most upstream contributions to come to the blackducksoftware perceptor/perceiver/perceptor-scan/perceptor-protoform projects.

This project is under active development. We welcome all contributions, most of which will probably be to the aforementioned upstream repositories.

## Release Status

Click the [releases tab](https://github.com/blackducksoftware/opssight-connector/releases) for the latest OpsSight releases. Alternatively, check out the [Release Notes](https://github.com/blackducksoftware/opssight-connector/wiki/Release-Notes).

## Developer notes

### Drafting a point release

How to draft a new OpsSight release, for the developers, using OpsSight 2.0.3 as an example:

- Tag branches in perceptor, perceiver, perceptor-scanner, perceptor-protoform ... which are changing (i.e. tag your perceptor branch you want to merge as release-2.0.3).

- Clone this repo

- Checkout the `release-2.0.x` opssight-connector branch

- Edit the opssight-connector `Gopkg.toml` file to point to the branch in the corresponding repo which was just updated.

- Run `dep ensure -update`

- Push your changes to the `release-2.0.x` opssight-connector branch.

- Now, the `build.properties` file should be something like 2.0.3-SNAPSHOT, and will automatically be updated once the downstream jenkins build is completed.

## License

Apache License 2.0