-
Notifications
You must be signed in to change notification settings - Fork 337
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
CPO: Unittest and fix eventhandling of HCP controller #1605
CPO: Unittest and fix eventhandling of HCP controller #1605
Conversation
/retest |
1 similar comment
/retest |
/retest-required |
@alvaroaleman this lgtm |
6e8d885
to
1bbdbc0
Compare
@csrwng yeah I was trying to come up with an elegant way to do this in support/upsert but couldn't think of one. Rebased it. |
This change: * Adds a unittest to the CPO that verifies that all objects it creates for a given HCP trigger a reconciliation of that HCP * Updates the HCP controller to use a CreateOrUpdate wrapper that inserts a HCP ownerRef into all objects, similiar to what we already do in the hostedcluster controller
1bbdbc0
to
f5824ab
Compare
@csrwng could you have another look, please? |
/retest-required |
1 similar comment
/retest-required |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman, csrwng The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@alvaroaleman: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest-required |
This change:
for a given HCP trigger a reconciliation of that HCP
inserts a HCP ownerRef into all objects, similiar to what we already
do in the hostedcluster controller
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story:Fixes #
Checklist