Repository navigation
feat: migrate to RHDH 2.1 chart with new schema - #461
Conversation
444dd4c to
0b32fe7
Compare
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
3a64bca to
5a352cc
Compare
JslYoon
left a comment
There was a problem hiding this comment.
Generally lgtm, are you also updating rhdh-intelligent-assistant-configs to stop the sync process?
The sync was updated to support the new schema redhat-developer/rhdh-intelligent-assistant-configs#10 but I'm not sure I follow about your comment re: stopping the sync? Are you referring to the rhdh-profile.py? If so I plan on changing that after this PR lands to avoid blocking any syncs while this is in review @JslYoon |
There was a problem hiding this comment.
Do we want to continue with the approach where OKP is hacked in via the rolling demo repo rather than enabling it in rhdh-chart?
There was a problem hiding this comment.
I added this piece to the descripion:
Keep OKP in this repository’s separate subchart and preserve its Lightspeed retrieval configuration and the BYOK data setup
Will handle removing the OKP subchart in favour of the builtin OKP handling via the Chart in a follow up PR
I think it'll be cleaner / easier to review/test if I separate this into a separate PR where it is just removing the old OKP and enabling via the Chart, wdyt @maysunfaisal
5a352cc to
e7f92ff
Compare
|
@Jdubrick and I talked and I would like to do a final validation of this after @HusneShabbir 's PR to enable kserve is merged , we rebase this on top of that, and we can bring up this PR locally and confirm the changes there are good. |
The RHDH 2.1 chart reads openshift.clusterRouterBase under the redhat-developer-hub dependency. The installer still set the legacy global.clusterRouterBase key, so custom router domains were ignored. Update both installer paths to set the value used by the Route and Lightspeed OKP URL. The new chart also applies default-deny egress to the RHDH pod. Its PostgreSQL allowance selects only the chart's same-namespace database, while the feedback-harvester sidecar connects to lightspeed-postgres in a separate namespace. Add an egress allowance restricted to pods labeled app=postgres in that namespace on TCP 5432. Omit it from Kind CI, where that database is absent, and assert the exact selectors and port in the Helm render test. Validated with Helm lint, all three Helm tests, shell syntax checks, and git diff --check.
Keep the KServe test's original LEGACY_SIDECARS identifier and the quoted CI PostgreSQL image tag; neither needs a presentation change for the new chart. Restore concise comments that explain the Backstage name override, Kind's Ingress and Fedora PostgreSQL overrides, and why the vendored OKP image is omitted from Kind. The name override preserves the existing Route, Service, and Deployment names used by setup URLs, OIDC callbacks, and CI references. These edits do not change the rendered workloads or network behavior.
Signed-off-by: Jordan Dubrick <jdubrick@redhat.com>
The upstream sync opens a pull request, where any generated profile change can be reviewed when it arrives. Remove the instruction that made upstream workflow cleanup a prerequisite for accepting migration updates. Signed-off-by: Jordan Dubrick <jdubrick@redhat.com>
The migration replaces the legacy backstage/lightspeed values tree, so rebasing over upstream/development's new sidecar resource limits and notebook chunking settings cannot retain them at their old paths. Apply the same values to intelligentAssistant.core.resources and appConfig.intelligent-assistant.notebooks.chunkingStrategy in the 2.1 chart configuration.
Signed-off-by: Jordan Dubrick <jdubrick@redhat.com>
The RHDH 2.1 chart migration timed out during helm install --wait, but the CI artifact contained only a PodInitializing error from an init container that had not started. Capture pod descriptions, events, and logs for each container so a failed run identifies the blocking pod and container. Reduce the Helm wait from 40 to 15 minutes; the last successful Kind install took about three minutes, and this leaves time for diagnosis within the 45-minute job limit.
The new PostgreSQL subchart enables a read-only root filesystem and runs with group 1001 when the CI container security context is enabled. The Fedora PostgreSQL image used by Kind exits while creating /var/lib/pgsql, leaving the RHDH wait-for-db init container blocked until Helm times out. Restore the writable root filesystem and group 0 from the last successful CI render, and assert those settings in the CI values test.
This reverts commit 99fe081.
e7f92ff to
f61c5db
Compare
The RHDH 2.1 chart consumes postgresql.auth.existingSecret as a literal in the Backstage pod, so values.yaml uses the development secret name. Setup creates a PostgreSQL secret from ARGOCD_APP_NAME, which would not match that value for another release. Pass the matching secret name as an ArgoCD Helm parameter in both install paths. This mirrors the CI Helm override and keeps make install and make install-no-rhoai release-name safe.
Signed-off-by: Jordan Dubrick <jdubrick@redhat.com>
The RHDH chart default-deny policy selects the Backstage pod, while its HTTPS allowance matches only TCP 443. On OpenShift, kubernetes.default.svc:443 forwards to an API endpoint on TCP 6443 and OVN evaluates this egress policy after load balancing. The KServe informer therefore times out before TLS or authorization. Allow TCP 6443 from only the release Backstage pod in non-CI deployments. The connector plugin also starts when rhoai.enabled is false, so the policy must cover lightweight installs as well.
gabemontero
left a comment
There was a problem hiding this comment.
it is working with the k8s egress network policy
undo if needed that okp disablement for the lack of self server certs @Jdubrick and as we discussed you'll add in the f/ups you already have planned the stuff in that space to make it sufficiently configurable etc.
Restore the OKP RAG endpoint configuration and okp retrieval source. The original commit was a temporary test-only change and must not remain in the migration PR. Signed-off-by: Jordan Dubrick <jdubrick@redhat.com>
What does this PR do?
2.1, which is3.4.5nameOverride: backstageto preserve the existing Route, Service, and Deployment names. Setup URLs, OIDC callbacks, and CI references depend on those namesmainafter this PR merges so that it properly updates the new location. If I change it beforehand it will just be broken during this PRs reviewWhich issue(s) does this PR fix
https://redhat.atlassian.net/browse/RHIDP-16650
How to test changes / Special notes to the reviewer