Skip to content

Recover integration test for owner reference #994

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 27, 2025

Conversation

Zerpet
Copy link
Member

@Zerpet Zerpet commented May 26, 2025

Note to reviewers: remember to look at the commits in this PR and consider if they can be squashed
Note to contributors: remember to re-generate client set if there are any API changes

Summary Of Changes

  • Recover owner reference test for User
  • Tweak kubebuilder-assets target

As part of abc5737, we chopped the test related to owner references. The system tests verify that objects are garbage collected, and that proves that an owner reference is set. However, the system tests do not explicitly verify that the object does not block the owner deletion. This is required for OpenShift compatibility.

This PR recovers the owner reference test for User generated secret.

Zerpet added 2 commits May 26, 2025 12:59
As part of abc5737, we chopped the test
related to owner references. The system tests verify that objects are
garbage collected, and that proves that an owner reference is set.
However, the system tests do not explicitly verify that the object does
not block the owner deletion. This is required for OpenShift
compatibility.

This commit recovers the owner reference test for User generated secret.
Now it is possible to shell eval the output of this target, like so:

```
eval "$(gmake kubebuilder-assets)"
```

This is helpful to run `ginkgo` commands directly, without Make
@Zerpet Zerpet added this to the v1.17.1 milestone May 26, 2025
@Zerpet Zerpet self-assigned this May 26, 2025
@Zerpet Zerpet requested review from mkuratczyk and MirahImage May 26, 2025 12:04
This can cause test pollution with other suites that do not expect to
set user limits, and consequently don't prepare the fake HTTP client to
respond to user limit creation.
@Zerpet Zerpet force-pushed the tweak-owner-reference-behaviour branch from e579d1c to ce4b4d6 Compare May 26, 2025 15:26
@Zerpet
Copy link
Member Author

Zerpet commented May 26, 2025

ce4b4d6 should fix the last remains of flakes in the integration tests. I had done this for vhosts, I overlooked user limits in my previous PR 😢

@MirahImage MirahImage merged commit d5e8d86 into main May 27, 2025
7 checks passed
@MirahImage MirahImage deleted the tweak-owner-reference-behaviour branch May 27, 2025 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants