chore(deploy): update api stage image tag to d190ec2df4cb

[red-hat-konflux-kflux-prd-rh02]

Auto-generated by Konflux push pipeline.

Updates newTag in stage kustomization to d190ec2df4cbe0205df2a371703cd2bffc8f40e7.

Summary by CodeRabbit

• Chores
  • Updated staging environment deployment configuration with a new API service version.

[coderabbitai]

Walkthrough

A Docker image tag for the kartograph-api service is updated in the Kustomize stage overlay configuration file. The newTag parameter for quay.io/redhat-user-workloads/kartograph-tenant/kartograph-api is changed from commit hash cafacf8c14136240900e44b4d4ed17618af58677 to d190ec2df4cbe0205df2a371703cd2bffc8f40e7. No other Kustomization fields or image specifications are modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: updating the API stage image tag to a specific commit hash.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/deploy-tag-api-d190ec2df4cb

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@deploy/apps/kartograph/overlays/stage/kustomization.yaml`:
- Line 13: The kustomization overlay sets newTag to a commit SHA that does not
exist in the registry; verify and update the image tag before merging. Confirm
the image
quay.io/redhat-user-workloads/kartograph-tenant/kartograph-api:d190ec2df4cbe0205df2a371703cd2bffc8f40e7
has been built and pushed (or build and push it), then update the newTag value
in the kustomization.yaml (or change to the correct existing tag) so the
deployment references a valid image; if the build is not ready, revert this tag
change until the CI pipeline produces and pushes the image.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e29c3685-0c2a-4ab4-b963-0cf842d1ac6c

📥 Commits

Reviewing files that changed from the base of the PR and between d190ec2 and 08eaa03.

📒 Files selected for processing (1)

• deploy/apps/kartograph/overlays/stage/kustomization.yaml

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify image exists in registry and show commit differences

# Check if the new image exists in the Quay registry
echo "Checking if image exists..."
IMAGE="quay.io/redhat-user-workloads/kartograph-tenant/kartograph-api:d190ec2df4cbe0205df2a371703cd2bffc8f40e7"
if curl -fsL "https://quay.io/api/v1/repository/redhat-user-workloads/kartograph-tenant/kartograph-api/tag/d190ec2df4cbe0205df2a371703cd2bffc8f40e7/images" > /dev/null 2>&1; then
  echo "✓ Image exists at new tag"
else
  echo "✗ Image not found at new tag"
fi

# Check commit differences if this is the kartograph repository
echo -e "\nChecking commit differences..."
OLD_TAG="cafacf8c14136240900e44b4d4ed17618af58677"
NEW_TAG="d190ec2df4cbe0205df2a371703cd2bffc8f40e7"

if git rev-parse --verify "$OLD_TAG" >/dev/null 2>&1 && git rev-parse --verify "$NEW_TAG" >/dev/null 2>&1; then
  echo "Commits between $OLD_TAG and $NEW_TAG:"
  git log --oneline "$OLD_TAG..$NEW_TAG"
  echo -e "\nFiles changed:"
  git diff --name-status "$OLD_TAG" "$NEW_TAG"
else
  echo "Note: Commit SHAs may be from a different repository (kartograph-api)"
fi

Repository: openshift-hyperfleet/kartograph

Length of output: 768

---

Image tag does not exist in the registry — do not merge until image is built and pushed.

The image quay.io/redhat-user-workloads/kartograph-tenant/kartograph-api:d190ec2df4cbe0205df2a371703cd2bffc8f40e7 could not be found in the Quay registry. The new commit includes dependency updates (Apache Age, SpiceDB, UBI9 base images) across the Dockerfile and deployment files. Verify that the image has been successfully built and pushed before merging this change.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@deploy/apps/kartograph/overlays/stage/kustomization.yaml` at line 13, The
kustomization overlay sets newTag to a commit SHA that does not exist in the
registry; verify and update the image tag before merging. Confirm the image
quay.io/redhat-user-workloads/kartograph-tenant/kartograph-api:d190ec2df4cbe0205df2a371703cd2bffc8f40e7
has been built and pushed (or build and push it), then update the newTag value
in the kustomization.yaml (or change to the correct existing tag) so the
deployment references a valid image; if the build is not ready, revert this tag
change until the CI pipeline produces and pushes the image.