Normal Description of problem:
When creating a ProjectHelmChartRepository (namespace-scoped), the CA Certificate and TLS Client Config dropdowns incorrectly list ConfigMaps/Secrets from the hardcoded openshift-config namespace instead of the repository's namespace. This prevents users from selecting resources they created in their project namespace.
The backend correctly uses the repository's namespace, but the UI has hardcoded 'openshift-config'.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create a ConfigMap with CA certificate in a project namespace:
oc create configmap helm-repo-ca --from-literal=ca-bundle.crt="test" -n helm-test
2. Navigate to: Helm → Helm Repositories → Create ProjectHelmChartRepository
3. Select namespace: helm-test
4. Open "Show advanced options"
5. Click the CA Certificate dropdown
6. Observe: helm-repo-ca ConfigMap is NOT listed (only shows ConfigMaps from openshift-config)
Actual results:
CA Certificate and TLS Client Config dropdowns only show resources from openshift-config namespace, regardless of which namespace the ProjectHelmChartRepository is being created in.
Expected results:
For ProjectHelmChartRepository (namespace-scoped):
- CA Certificate dropdown should list ConfigMaps from the repository's namespace
- TLS Client Config dropdown should list Secrets from the repository's namespace
For HelmChartRepository (cluster-scoped):
- Both dropdowns should list from openshift-config (current behavior is correct)
Additional info:
Affected file: frontend/packages/helm-plugin/src/components/forms/HelmChartRepository/CreateHelmChartRepositoryFormEditor.tsx
