Skip to content

Conversation

@rm3l
Copy link
Member

@rm3l rm3l commented Jan 14, 2026

Description of the change

This is to check if this fixes the failures we've been seeing.

Which issue(s) does this PR fix or relate to

https://github.com/redhat-developer/rhdh-chart/actions/runs/20803020591/job/60086142931?pr=291#step:15:5693

How to test changes / Special notes to the reviewer

Checklist

  • For each Chart updated, version bumped in the corresponding Chart.yaml according to Semantic Versioning.
  • For each Chart updated, variables are documented in the values.yaml and added to the corresponding README.md. The pre-commit utility can be used to generate the necessary content. Use pre-commit run -a to apply changes. The pre-commit Workflow will do this automatically for you if needed.
  • JSON Schema template updated and re-generated the raw schema via the pre-commit hook.
  • Tests pass using the Chart Testing tool and the ct lint command.
  • If you updated the orchestrator-infra chart, make sure the versions of the Knative CRDs are aligned with the versions of the CRDs installed by the OpenShift Serverless operators declared in the values.yaml file. See Installing Knative Eventing and Knative Serving CRDs for more details.

@rhdh-qodo-merge
Copy link

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🔒 Security concerns

Supply chain risk:
The workflow applies a remote Kubernetes manifest directly from a GitHub URL (kubectl create -f https://...sonataflow-operator.yaml) without integrity verification (checksum/signature) or vendoring. If the upstream asset is compromised or the download is intercepted, CI could apply malicious cluster-admin resources. Consider pinning by digest where possible, verifying signatures/checksums, or storing the manifest in-repo.

⚡ Recommended focus areas for review

📄 References
  1. redhat-developer/rhdh-chart/charts/orchestrator-infra/ci/upstream-olm-values.yaml [1-13]
  2. redhat-developer/rhdh-chart/charts/orchestrator-software-templates-infra/ci/upstream-values.yaml [1-27]
  3. redhat-developer/rhdh-chart/charts/backstage/templates/sonataflows.yaml [0-2]
  4. redhat-developer/rhdh-chart/charts/orchestrator-infra/templates/serverless/operator-group.yaml [0-2]
  5. redhat-developer/rhdh-operator/dist/rhdh/install.yaml [2310-2326]
  6. redhat-developer/rhdh-operator/dist/rhdh/install.yaml [1675-1730]
  7. redhat-developer/rhdh-chart/charts/backstage/ci/with-test-pod-disabled-values.yaml [1-12]
  8. redhat-developer/rhdh-chart/charts/backstage/ci/with-custom-dynamic-pvc-claim-spec-values.yaml [0-2]

@sonarqubecloud
Copy link

@rhdh-qodo-merge rhdh-qodo-merge bot added the enhancement New feature or request label Jan 14, 2026
@rhdh-qodo-merge
Copy link

PR Type

Enhancement


Description

  • Update SonataFlow Operator installation to use new release location

  • Change kubectl apply to kubectl create for CRD installation

  • Update operator version from 1.43.1 to 10.1.0


File Walkthrough

Relevant files
Configuration changes
test.yaml
Update SonataFlow Operator source and kubectl command       

.github/workflows/test.yaml

  • Replace deprecated SonataFlow Operator release URL with new location
    from apache/incubator-kie-tools
  • Update operator version from v1.43.1 to 10.1.0
  • Change kubectl apply to kubectl create for CRD installation commands
  • Maintain existing CRD installation loop for orchestrator-infra charts
+2/-2     

@rhdh-qodo-merge
Copy link

PR Code Suggestions ✨

Explore these optional code suggestions:

CategorySuggestion                                                                                                                                    Impact
Possible issue
Use idempotent kubectl command for robustness

Replace kubectl create with the idempotent kubectl apply command. This will
prevent potential CI failures on reruns if the resources already exist, making
the script more robust.

.github/workflows/test.yaml [145-149]

 run: |
   for crdDir in charts/orchestrator-infra/crds/*; do
-    kubectl create -f "${crdDir}"
+    kubectl apply -f "${crdDir}"
   done
-  kubectl create -f https://github.com/apache/incubator-kie-tools/releases/download/10.1.0/apache-kie-10.1.0-incubating-sonataflow-operator.yaml
+  kubectl apply -f https://github.com/apache/incubator-kie-tools/releases/download/10.1.0/apache-kie-10.1.0-incubating-sonataflow-operator.yaml
  • Apply / Chat
Suggestion importance[1-10]: 7

__

Why: The suggestion correctly points out that using kubectl create is not idempotent and could cause CI failures on reruns, proposing to revert to kubectl apply which improves the robustness of the workflow.

Medium
General
Wait for CRDs readiness

Add a kubectl wait command after creating CRDs. This ensures the CRDs are fully
established before the operator installation begins, preventing potential race
conditions.

.github/workflows/test.yaml [146-148]

 for crdDir in charts/orchestrator-infra/crds/*; do
   kubectl create -f "${crdDir}"
 done
+kubectl wait --for=condition=established --all crd --timeout=60s
  • Apply / Chat
Suggestion importance[1-10]: 6

__

Why: The suggestion correctly identifies a potential race condition and proposes adding a kubectl wait command to ensure CRDs are established before installing the operator, which improves the reliability of the CI workflow.

Low
  • More

@rm3l rm3l merged commit de0dfce into redhat-developer:main Jan 14, 2026
6 of 7 checks passed
@rm3l rm3l deleted the ci/use_new_location_of_sonataflow_operator_in_ci branch January 14, 2026 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant