1.2.42

Changelog

• Fixed missing resources and security context in registry pod
• Updated scan result details to include fixAvailable metrics for vulnerabilities
  that have a fix available

Upgrade instructions

Sample upgrade command:

helm upgrade \
  --values overrides.yaml \
  deepsecurity-smartcheck \
  https://github.com/deep-security/smartcheck-helm/archive/1.2.42.tar.gz

IMPORTANT NOTE: If you are upgrading from version 1.2.8, 1.2.9, or 1.2.10, we recommend that you use the --force parameter in the helm upgrade command. There was an error in these releases that could cause upgrading the Deployment resources to fail. Using the --force parameter will tell Helm to re-create the Deployment resources if the initial upgrade attempt fails, and should cause the overall upgrade to be successful.

If you are upgrading from version 1.2.11 or later, you can omit the --force parameter when upgrading.

1.2.41

Changelog

• Raised resource limits for built-in database pod. We do not recommend using the built-in database pod for production. You should use an external database.
• Improved license pod configuration so that it automatically picks up activation code changes
• Improved API documentation

Upgrade instructions

Sample upgrade command:

helm upgrade \
  --values overrides.yaml \
  deepsecurity-smartcheck \
  https://github.com/deep-security/smartcheck-helm/archive/1.2.41.tar.gz

IMPORTANT NOTE: If you are upgrading from version 1.2.8, 1.2.9, or 1.2.10, we recommend that you use the --force parameter in the helm upgrade command. There was an error in these releases that could cause upgrading the Deployment resources to fail. Using the --force parameter will tell Helm to re-create the Deployment resources if the initial upgrade attempt fails, and should cause the overall upgrade to be successful.

If you are upgrading from version 1.2.11 or later, you can omit the --force parameter when upgrading.

1.2.40

Changelog

• Increased storage limits for vulnerability scan pod
• Prioritized pipeline scans (scans requested through the API) over daily registry scans

Upgrade instructions

Sample upgrade command:

helm upgrade \
  --values overrides.yaml \
  deepsecurity-smartcheck \
  https://github.com/deep-security/smartcheck-helm/archive/1.2.40.tar.gz

IMPORTANT NOTE: If you are upgrading from version 1.2.8, 1.2.9, or 1.2.10, we recommend that you use the --force parameter in the helm upgrade command. There was an error in these releases that could cause upgrading the Deployment resources to fail. Using the --force parameter will tell Helm to re-create the Deployment resources if the initial upgrade attempt fails, and should cause the overall upgrade to be successful.

If you are upgrading from version 1.2.11 or later, you can omit the --force parameter when upgrading.

1.2.39

Changelog

• Added explicit resources section to init containers
• Added filter to scan history user interface
• Fixed dashboard repository metrics calculation

Upgrade instructions

Sample upgrade command:

helm upgrade \
  --values overrides.yaml \
  deepsecurity-smartcheck \
  https://github.com/deep-security/smartcheck-helm/archive/1.2.39.tar.gz

IMPORTANT NOTE: If you are upgrading from version 1.2.8, 1.2.9, or 1.2.10, we recommend that you use the --force parameter in the helm upgrade command. There was an error in these releases that could cause upgrading the Deployment resources to fail. Using the --force parameter will tell Helm to re-create the Deployment resources if the initial upgrade attempt fails, and should cause the overall upgrade to be successful.

If you are upgrading from version 1.2.11 or later, you can omit the --force parameter when upgrading.

1.2.38

Changelog

• Fixed integration issue with Shibboleth SAML IDP. You can now use metadataURL or unmodified metadataXML with Shibboleth
• Added user interface for overrides

Upgrade instructions

Sample upgrade command:

helm upgrade \
  --values overrides.yaml \
  deepsecurity-smartcheck \
  https://github.com/deep-security/smartcheck-helm/archive/1.2.38.tar.gz

IMPORTANT NOTE: If you are upgrading from version 1.2.8, 1.2.9, or 1.2.10, we recommend that you use the --force parameter in the helm upgrade command. There was an error in these releases that could cause upgrading the Deployment resources to fail. Using the --force parameter will tell Helm to re-create the Deployment resources if the initial upgrade attempt fails, and should cause the overall upgrade to be successful.

If you are upgrading from version 1.2.11 or later, you can omit the --force parameter when upgrading.

1.2.37

Changelog

• Improved Harbor integration; Deep Security Smart Check will now sync private projects
• Updated API definition to OpenAPI v3 format
• Clarified expected format for SAML identity provider metadataXML attribute

Upgrade instructions

Sample upgrade command:

helm upgrade \
  --values overrides.yaml \
  deepsecurity-smartcheck \
  https://github.com/deep-security/smartcheck-helm/archive/1.2.37.tar.gz

IMPORTANT NOTE: If you are upgrading from version 1.2.8, 1.2.9, or 1.2.10, we recommend that you use the --force parameter in the helm upgrade command. There was an error in these releases that could cause upgrading the Deployment resources to fail. Using the --force parameter will tell Helm to re-create the Deployment resources if the initial upgrade attempt fails, and should cause the overall upgrade to be successful.

If you are upgrading from version 1.2.11 or later, you can omit the --force parameter when upgrading.

1.2.36

Changelog

• Added filters for list views
• Improved error reporting for images with an unsupported base OS
  ​

Upgrade instructions

​Sample upgrade command:

helm upgrade \
  --values overrides.yaml \
  deepsecurity-smartcheck \
  https://github.com/deep-security/smartcheck-helm/archive/1.2.36.tar.gz

​
IMPORTANT NOTE: If you are upgrading from version 1.2.8, 1.2.9, or 1.2.10, we recommend that you use the --force parameter in the helm upgrade command. There was an error in these releases that could cause upgrading the Deployment resources to fail. Using the --force parameter will tell Helm to re-create the Deployment resources if the initial upgrade attempt fails, and should cause the overall upgrade to be successful.
​
If you are upgrading from version 1.2.11 or later, you can omit the --force parameter when upgrading.

1.2.35

Changelog

• Added support for loadBalancerSourceRanges to allow configuring the firewall exceptions for access to the service

Upgrade instructions

​Sample upgrade command:

helm upgrade \
  --values overrides.yaml \
  deepsecurity-smartcheck \
  https://github.com/deep-security/smartcheck-helm/archive/1.2.35.tar.gz

​
IMPORTANT NOTE: If you are upgrading from version 1.2.8, 1.2.9, or 1.2.10, we recommend that you use the --force parameter in the helm upgrade command. There was an error in these releases that could cause upgrading the Deployment resources to fail. Using the --force parameter will tell Helm to re-create the Deployment resources if the initial upgrade attempt fails, and should cause the overall upgrade to be successful.
​
If you are upgrading from version 1.2.11 or later, you can omit the --force parameter when upgrading.

1.2.34

Changelog

• Updated chart to automatically restart pods on proxy configuration changes
• Added filter for users list
  ​

Upgrade instructions

​Sample upgrade command:
​

helm upgrade \
  --values overrides.yaml \
  deepsecurity-smartcheck \
  https://github.com/deep-security/smartcheck-helm/archive/1.2.34.tar.gz

​
IMPORTANT NOTE: If you are upgrading from version 1.2.8, 1.2.9, or 1.2.10, we recommend that you use the --force parameter in the helm upgrade command. There was an error in these releases that could cause upgrading the Deployment resources to fail. Using the --force parameter will tell Helm to re-create the Deployment resources if the initial upgrade attempt fails, and should cause the overall upgrade to be successful.
​
If you are upgrading from version 1.2.11 or later, you can omit the --force parameter when upgrading.

1.2.33

Changelog

• Updated recommended Helm version (use 3.0.1+ to avoid issues in 3.0.0)
• Added the ability to cancel a queued scan through the user interface
• Added the ability to provide context data to scan requests through the API
• Improved scan robustness

Upgrade instructions

Sample upgrade command:

helm upgrade \
  --values overrides.yaml \
  deepsecurity-smartcheck \
  https://github.com/deep-security/smartcheck-helm/archive/1.2.33.tar.gz

IMPORTANT NOTE: If you are upgrading from version 1.2.8, 1.2.9, or 1.2.10, we recommend that you use the --force parameter in the helm upgrade command. There was an error in these releases that could cause upgrading the Deployment resources to fail. Using the --force parameter will tell Helm to re-create the Deployment resources if the initial upgrade attempt fails, and should cause the overall upgrade to be successful.

If you are upgrading from version 1.2.11 or later, you can omit the --force parameter when upgrading.