remove: Remove deprecated reference to manager_auth_proxy_patch.yaml

[Francisco-xiq]

Summary

Removes a stale reference to ../default/manager_auth_proxy_patch.yaml in config/testing/kustomization.yaml.

This file was deleted in #323 but the reference was left behind, causing kustomize build to fail for anyone using the config/testing directory.

Closes #262

Changes

• config/testing/kustomization.yaml: removed path entry pointing to deleted file ../default/manager_auth_proxy_patch.yaml

Note

make lint was already failing before this change on roles/postgres/ and roles/restore/.

Summary by CodeRabbit

• Chores
  • Updated testing environment configuration to switch manager image reference and enable more verbose debug logging during tests.
  • Removed an obsolete proxy patch to streamline test setup and improve configuration consistency.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 7ac0c5ee-65f4-4803-a227-2552a3755e45

📥 Commits

Reviewing files that changed from the base of the PR and between 3e7d3f1 and 746a39d.

📒 Files selected for processing (1)

• config/testing/kustomization.yaml

💤 Files with no reviewable changes (1)

• config/testing/kustomization.yaml

---

📝 Walkthrough

Walkthrough

Update testing Kustomize to remove the default manager auth-proxy patch and add two test-specific patches: manager_image.yaml and debug_logs_patch.yaml. No other fields (namespace, namePrefix, resources, images) were changed.

Changes

Testing Kustomize Patch Configuration

Layer / File(s)	Summary
Testing environment patch configuration update config/testing/kustomization.yaml	The patches list is modified to remove ../default/manager_auth_proxy_patch.yaml and add manager_image.yaml and debug_logs_patch.yaml.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR removes a stale file reference but does not address the core objective of issue #262: replacing the deprecated gcr.io/kubebuilder/kube-rbac-proxy image.	Verify that the removed patch file was not the only reference to the deprecated kube-rbac-proxy image, and address the image replacement requirement from issue #262.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: removing a deprecated reference to manager_auth_proxy_patch.yaml from the configuration file.
Out of Scope Changes check	✅ Passed	The PR only removes a stale file reference from kustomization.yaml, which is directly related to addressing infrastructure changes mentioned in issue #262.
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

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[ptoscano]

Thanks!

If there is a way to test the configuration in a github workflow, I'd really like to see that, to prevent issues like this.

[ptoscano]

@Francisco-xiq thanks for the fix!

Please note that commits to the ansible organization must have signed commits; check the following documentations:
https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits
https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key

This means you need to amend the current commit to be signed (with either a GPG or a SSH key).

[Francisco-xiq]

Thanks!

If there is a way to test the configuration in a github workflow, I'd really like to see that, to prevent issues like this.

Thanks for the review.
I guess thats totally possible, gonna start working on a design.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 0

[Francisco-xiq]

Thanks!

If there is a way to test the configuration in a github workflow, I'd really like to see that, to prevent issues like this.

I think the main issue is that the configuration points to a non-existent file. If we add a CI step to verify the build before running the tests, it would make debugging much easier (and save us from waiting for the heavier tests to fail).

So, I suggest adding a quick check to the Kustomize build to ensure it runs smoothly and that all paths in the file actually exist. If everything looks good, then we are ok to run the Minikube tests. WDYT?

[ptoscano]

So, I suggest adding a quick check to the Kustomize build to ensure it runs smoothly and that all paths in the file actually exist. If everything looks good, then we are ok to run the Minikube tests. WDYT?

If that can be run easily in a github workflow, sure, it makes sense. Feel free to open a new PR for it.

(note you need to still upload your key to your profile)