Release notes for Red Hat Advanced Developer Suite - software supply chain 1.7
Explore new features in this release and learn about known issues.
Abstract
Preface Copy linkLink copied to clipboard!
The release notes for Red Hat Advanced Developer Suite - software supply chain summarize new features and enhancements, notable technical changes, features in Technology Preview, bug fixes, known issues, and other related advisories or information.
Chapter 1. About this release Copy linkLink copied to clipboard!
Red Hat Advanced Developer Suite - software supply chain 1.7 is now generally available. RHADS - SSC was previously known as Red Hat Trusted Application Pipeline. Starting with version 1.6, it became part of a new Red Hat offering Red Hat Advanced Developer Suite.
To learn more about support for all versions, refer to the RHADS - SSC life cycle policy.
To upgrade RHADS - SSC, you must upgrade each product in its stack separately. The Trusted Software Supply Chain (TSSC) installation program is not a manager: it generates your first deployment of RHADS - SSC but it does not support upgrades.
- To learn more about RHADS - SSC, refer to the About RHADS - SSC product overview.
- To install RHADS - SSC, refer to Installing RHADS - SSC.
The products that the TSSC installation program deploys are sized for a proof of concept or a very small team. For larger teams, manual reconfiguration of the products is most likely necessary and should be done by following procedures documented for each individual product.
Chapter 2. New features and enhancements Copy linkLink copied to clipboard!
Red Hat Advanced Developer Suite - software supply chain 1.7 adds the following new features and improvements of some existing features.
- Application templates are refreshed
This enhancement updates the application templates by placing them in the
tssc-sample-templates/templatesdirectory, shortening each template name, removing extraneous scripts, removing the devfile, and simplifying the templates so that they are easier to understand.Expand Table 2.1. Renamed application templates Old Name New Name devfile-sample-code-with-quarkus-dance
java-quarkus
devfile-sample-dotnet60-dance
dotnet
devfile-sample-go-dance
go
devfile-sample-java-springboot-dance
java-springboot
devfile-sample-nodejs-dance
nodejs
devfile-sample-python-dance
python
- Refactored the
config.yamlfile -
In this release, we updated the installation config.yaml file to use
- name:as a key-value structure for components instead of camel case notation. This change enhances readability by adopting a more explicit, human-readable syntax aligned with YAML best practices, facilitating easier maintenance and integration with tools such as OpenShift and Helm. This refactoring preserves full compatibility with existing installations and does not impact core functionality. - Added an
authProviderparameter to the Red Hat Developer Hub configuration With this release, RHADS can support multiple identity and access management (IAM) providers. This enhancement means that you must explicitly choose the IAM provider in the
config.yamlfile under the RHDH component. For example:- name: Developer Hub authProvider: <github|gitlab>- name: Developer Hub authProvider: <github|gitlab>Copy to Clipboard Copied! Toggle word wrap Toggle overflow
- Added support for GitLab as an IAM provider
- With this release, RHADS supports GitLab as an identity and access management (IAM) provider.
- Improved RBAC support for RHDH IAM providers
-
With this release, users can configure Red Hat Advanced Developer Suite to use GitLab as the
authProviderin the config.yaml file, enabling role-based access control (RBAC). This enhancement provides greater flexibility in source control system integration, improving the security and customization options for users, aligning with the growing preference for GitLab as a source control system.
Chapter 3. Compatibility and support matrix Copy linkLink copied to clipboard!
3.1. Products and versions Copy linkLink copied to clipboard!
The TSSC installer deploys the following products, which form the RHADS subscription:
| Product | Version |
|---|---|
| Red Hat Developer Hub | 1.7 |
| Red Hat Trusted Artifact Signer | 1.2 |
| Red Hat Trusted Profile Analyzer | 2.1 |
| Conforma | 0.6 |
RHADS - SSC installs on OpenShift Container Platform. During installation, the TSSC installer automatically deploys several products, which are available through the OCP subscriptions. RHADS - SSC relies on these products, and they integrate seamlessly with RHADS - SSC and its software templates. However, note that these products are not included with RHADS - SSC.
| Product | Version | Subscription |
|---|---|---|
| OpenShift Container Platform | 4.17, 4.18, 4.19 | |
| Red Hat OpenShift Pipelines | 1.19 | Available through the OpenShift Container Platform subscription. |
| Red Hat OpenShift GitOps | 1.17 | Available through the OpenShift Container Platform subscription. |
| Red Hat Advanced Cluster Security | 4.8 | Available through the OpenShift Platform Plus subscription. |
3.2. Red Hat Developer Hub plugins Copy linkLink copied to clipboard!
RHADS - SSC enables a selection of RHDH dynamic plugins to support creation and monitoring of trusted software supply chain applications. Some of the plugins enabled by RHADS - SSC are fully supported, however some are Technology Preview plugins that might not be functionally complete.
Regardless of the plugins' level of support, the RHADS - SSC software templates use the features of Red Hat Trusted Artifact Signer, Red Hat Trusted Profile Analyzer, and Conforma to produce secure pipelines.
| Name | Path |
|---|---|
| Argo CD |
|
| GitHub |
|
| GitHub Org |
|
| Kubernetes |
|
| RBAC |
|
| Tekton |
|
| Topology |
|
| Name | Path |
|---|---|
| Argo CD |
|
| Argo CD (Red Hat) |
|
| Azure DevOps |
|
| Azure DevOps |
|
| Bitbucket Cloud |
|
| GitHub Actions |
|
| GitLab |
|
| GitLab |
|
| GitLab |
|
| Jenkins |
|
| Jenkins |
|
| JFrog Artifactory |
|
| Kubernetes |
|
| Nexus Repository Manager |
|
Note that Red Hat Developer Hub automatically enables a selection of plugins too. Refer to Preinstalled dynamic plugins for a list.
To learn more about the individual dynamic plugins, including their supported versions, refer to the Dynamic plugins reference in the RHDH docs.
Chapter 4. Fixed issues Copy linkLink copied to clipboard!
Red Hat Advanced Developer Suite - software supply chain 1.7 provides the following bug fixes and resolved issues:
- Installation failed due to autogenerated TektonConfig
During installation in version 1.6 and earlier releases, an autogenerated TektonConfig resource named
configin the default namespace could prevent the Trusted Software Supply Chain (TSSC) infrastructure subscription from applying successfully. This occurred because the resource lacked the required Helm ownership metadata, such as theapp.kubernetes.io/managed-bylabel andmeta.helm.sh/release-nameandmeta.helm.sh/release-namespaceannotations.The error message during installation was similar to the following:
W0610 00:08:01.710201 65643 warnings.go:70] unknown field "spec.template.spec.containers[0].resources.ephemeral-storage" Error: install failed: Unable to continue with install: TektonConfig "config" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "tssc-infrastructure"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "tssc"
W0610 00:08:01.710201 65643 warnings.go:70] unknown field "spec.template.spec.containers[0].resources.ephemeral-storage" Error: install failed: Unable to continue with install: TektonConfig "config" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "tssc-infrastructure"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "tssc"Copy to Clipboard Copied! Toggle word wrap Toggle overflow This issue has been observed intermittently across testing cycles in version 1.6 and earlier and has been fixed in version 1.7.
Chapter 5. Known issues Copy linkLink copied to clipboard!
Red Hat Advanced Developer Suite - software supply chain 1.7 is affected by the following newly identified and previously known issues. If you encounter an issue that is not listed in this section, report it.
- RHDH cannot push content to the GitOps repository on GitHub
- When you create an application, RHADS - SSC automatically creates a GitOps repository on GitHub. However, in some cases, RHDH fails to push content into this repository. As a result, a pipeline for this application fails with an error. To work around, restart the application creation process.
- RHDH doesn’t display the Image Registry tab if RHADS - SSC cannot detect your registry type
- The Red Hat Developer Hub UI doesn’t display the Image Registry tab on the component’s page if RHADS - SSC is unable to detect which container image registry you’re using. RHADS - SSC analyzes your registry URL to annotate your components, and if that annotation is missing, the tab will not appear in the RHDH UI. To work around this issue, you can manually enable the Image Registry tab.
- GitHub details are missing for Jenkins pipeline runs
- After a Jenkins pipeline run for a component is complete, the Projects/Run view in the CI tab might display empty fields for Message, Author, and GitHub, even though the GitHub Commit ID is correctly displayed. This issue occurs because the current version of the RHDH Jenkins plugin doesn’t retrieve all required information. Currently, there is no workaround.
- The CI tab displays GitLab CI information for Tekton and Jenkins
- When you host source code for your component in GitLab and choose Tekton or Jenkins as a CI provider, the CI tab in the RHDH UI might incorrectly display information about GitLab pipelines together with the Tekton or Jenkins pipelines. Note that if you choose Tekton or Jenkins, RHADS - SSC only runs Tekton or Jenkins pipelines, and the CI tab section about GitLab pipelines should be ignored.
- RHDH doesn’t display the Image Check tab if you use GitLab CI
- If you use GitLab CI as a CI provider, the CI page in the RHDH UI might not display the Image Check tab and the component’s container image URL. However, the Image Scan and Deployment Check tabs are displayed correctly. Currently, there is no workaround.
- RHADS - SSC doesn’t support some environments
- RHADS - SSC 1.7 does not support the following environments: any air-gapped environment, IBM Power Platform, IBM Z Platform, ARM64, and Federal Information Processing Standards (FIPS) mode for OpenShift Container Platform.
- Uninstallation of RHADS - SSC is not supported
-
Uninstallation of RHADS - SSC is not currently supported, but it can be done by removing all
tsscnamespaces from the cluster.
Chapter 6. Deprecated and removed features Copy linkLink copied to clipboard!
This section lists features that have been deprecated or removed from RHADS - SSC. Deprecated functionalities remain fully supported, which means we continue to test and maintain them. However, deprecated features will be removed in future releases of RHADS - SSC, and they are not recommended for new deployments.
- The installation program no longer installs Quay
- The TSSC installation program no longer installs Quay. You can still integrate Quay with RHADS. See Integrating Quay for additional details.
- The installation program no longer supports Microsoft authentication
- In this release, when integrating Azure Pipelines you can no longer use Microsoft authentication. Use one of the supported Identity and Access Management (IAM) providers instead. See (Optional) Integrating Azure Pipelines for additional details.
- Removed the list of dependencies from the installation
config.yamlfile -
In this release, the
config.yamlomits the list of dependencies, simplifying the configuration.
Revised on 2025-11-05 05:28:28 UTC