Version 2020.3.0

New features

• Added support for deploy BDBA standalone with synopsysctl (#1320)

Version 2020.2.2

New features

• Added support for Alert 5.3.0 (#1312)
• Added support for Alert 5.0.3 (#1311)

Resolved issues

• Resolved a functionality issue with Black Duck upload cache. (#1306)

Version 2020.2.1

New features

• Added support for Black Duck 2020.2.1 (#1279)
• Added support for Alert 5.2.3 (#1277)

Version 2020.2.0

New features

• Added support for Black Duck 2020.2.0 (#1207)
• Added support for Alert 5.0.2, 5.2.1, and 5.2.2
• Added support for Polaris on premise reporting

Version 2019.12.2

New features

• Added support for Black Duck 2019.12.1 (#1200)
• Added support for Alert 5.2.0 (#1221)
• Enabled SAML signature verification by default (#1227)

Version 2019.12.1

New features

• Added support for Black Duck 2019.10.3 ( #1220 )

Version 2019.12.0

New features

• Added support for Black Duck 2019.12.0 (#972)
• Added support for Black Duck 2019.10.2
• Added support for arbitrary security contexts for GID, UID, and fsGroup in Kubernetes (#936)
• Added the --security-context-file-path parameter which points to the security context file.
• Added support for running Black Duck images using non-root user IDs/Group IDs in YAML configuration files for Kubernetes.

Important information about upgrading to Black Duck version 2019.12.0

• When you upgrade to Black Duck version 2019.12.0 a migration script is run to purge rows that are no longer used in the audit_event table, which cleans the audit table. Before the upgrade, you must disable the liveness check (--liveness-probes false), do the upgrade and wait for the user interface to appear. When the user interface is up, you re-enable the liveness check. The migration might take a long time, for example, a migration process for a 350 GB audit_event table took 20 minutes. You must know the size of the audit_event table, both for the migration and for running the VACUUM command after the migration. You can check the size of the audit_event table by running a command in the bds_hub database or get the size in the Black Duck user interface.
• Refer to the upgrade section for more important information about upgrading Black Duck 2019.12.0

Resolved issues

• The alert deployment type is changed to recreate. (#1160)
  When you upgrade to Synopsys operator 2019.12.0 the Alert pods will restart.

Version 2019.11.1

New features

• Added support for Alert 5.1.0 (#1144)
• Added support for updating the master key at Black Duck instance level. (#682)
• Removed the option to update the master key for all Black Duck instances simultaneously.
• Added --seal-key parameter to synopsysctl, which is used to encrypt the master key when Source code upload is enabled. The seal key must consist of 32 characters.
• The --seal-key parameter is mandatory when you use synopsysctl create blackduck native commands.

Resolved issues

• Resolved issue with pods crashing because of out-of-memory issues by configuring memory limits using Mebibyte (Mi) instead of Megabyte (M). (#1087)
• Resolved an issue with resizing Black Duck instances during upgrades where existing pods retained their original memory settings and new pods were configured as expected. (#1072)
• Resolved an issue where the TLS secret was not created when installing Synopsys Operator by using the OLM Operator. (#1068)

Improvements

• Improved update logic by converting replication controllers to deployments for Black Duck and Alert. (#1130)

Notices

• Synopsysctl native commands are no longer available to use with the synopsysctl update command. (#1140)
  When you upgrade to Synopsys Operator version 11.1, all pods are restarted, which will cause some downtime.
  • This restart is required because of by the following changes in version 11.1:
    • Converting a replication controller to deployment.
    • Modifying the memory settings from M to Mi.

Version 2019.11.0

New features

• Added support for Black Duck 2019.10.1 and Alert 5.0.1 (#1096)
• Updated RBAC permissions with regards to Kubernetes API changes. (#1079)

Resolved issues

• Resolved issue where synopsysctl didn’t check $KUBECONFIG and only checked "~/.kube/config". (#1046)
• Resolved issue where a PVC was being created for Solr in Black Duck versions later than 2019.8.0 (#1052)
• Resolved issue where sysnopsysctl returned a nil pointer exception when running an update or delete where a namespace or secret didn’t exist. (#953)

Version 2019.10.0

New features

• Added support for Black Duck 10.0 (#967)
• Added support for synopsysctl to print the PVC default values in mock mode. (#999)

Resolved issues

• Fixed issue where namespace patch labels were not working. (#1018)
• Fixed issue where the exposed OpsSight service did not work using NodePort. (#970)
• Fixed issue where logs falsely indicated that the user interface was available when expose-ui was run and Black Duck was not enabled. (#771)
• Fixed permission issue of Synopsys operator for namespaced scope (#1031)
• Fixed issue that was caused when users created a Black Duck instance by specifying the --enable-binary-analysis flag and include --environs options, the binary analysis was not enabled because the --environs flag overrode the --enable-binary-analysis flag. (#1033)

Notifications

• The script ./operator-images.sh --push -r <DOCKER_REGISTRY> -p <DOCKER_PROJECT> -u <DOCKER_USER> that was used to push downloaded images to a secure registry is no longer available. Customers can request the images from the support team. (#441)