Chapter 7. Known issues
Chapter 7. Known issues This section lists known issues in Red Hat Developer Hub 1.4. 7.1. Multi-Attached error for Volume (PVC) Currently, when deploying Developer Hub using the Helm Chart, two replicas cannot run on different cluster nodes. This might also affect the upgrade from 1.3 to 1.4.0 if the new pod is scheduled on a different node. A possible workaround for the upgrade is to manually scale down the number of replicas to 0 before upgrading your Helm release. Or manually remove the old Developer Hub pod after upgrading the Helm release. However, this would imply some application downtime. You can also leverage a Pod Affinity rule to force the cluster scheduler to run your Developer Hub pods on the same node. Additional resources RHIDP-5344 7.2. Topology plugin permission is not displayed in the RBAC front-end UI Permissions associated only with front-end plugins do not appear in the UI because they require a backend plugin to expose the permission framework's well-known endpoint. As a workaround, you can apply these permissions by using a CSV file or directly calling the REST API of the RBAC backend plugin. Affected plugins include Topology ( topology.view.read ), Tekton ( tekton.view.read ), ArgoCD ( argocd.view.read ), and Quay ( quay.view.read ). Additional resources RHIDP-3396