Navigation Menu

Skip to content
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

Use spec.Namespace to prevent collisions rather than ownerRef #10503

Merged
merged 3 commits into from Jan 8, 2021

Conversation

julz
Copy link
Member

@julz julz commented Jan 7, 2021

Fixes #10477.

Proposed Changes

  • bumps deps
  • uses the new spec.Namespace field in ClusterDomainClaim to prevent collisions rather than IsControlledBy (which was never actually supported cross-namespace 🙊).
  • cleans up manually via FinalizeKind instead

Release Note

Changes how ClusterDomainClaims are cleaned up when DomainMappings are removed.

/assign @tcnghia @mattmoor

@google-cla google-cla bot added the cla: yes Indicates the PR's author has signed the CLA. label Jan 7, 2021
@knative-prow-robot knative-prow-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 7, 2021
@knative-prow-robot knative-prow-robot added the area/API API objects and controllers label Jan 7, 2021
@codecov
Copy link

codecov bot commented Jan 7, 2021

Codecov Report

Merging #10503 (d3151a8) into master (edf5ae0) will increase coverage by 0.02%.
The diff coverage is 92.85%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #10503      +/-   ##
==========================================
+ Coverage   88.06%   88.08%   +0.02%     
==========================================
  Files         187      187              
  Lines        8855     8865      +10     
==========================================
+ Hits         7798     7809      +11     
  Misses        817      817              
+ Partials      240      239       -1     
Impacted Files Coverage Δ
pkg/reconciler/domainmapping/reconciler.go 92.80% <90.00%> (-0.37%) ⬇️
.../reconciler/domainmapping/resources/domainclaim.go 100.00% <100.00%> (ø)
pkg/autoscaler/scaling/multiscaler.go 87.71% <0.00%> (-1.76%) ⬇️
pkg/reconciler/autoscaling/kpa/scaler.go 88.57% <0.00%> (-1.43%) ⬇️
pkg/activator/net/revision_backends.go 91.32% <0.00%> (+0.91%) ⬆️
pkg/autoscaler/statforwarder/leases.go 78.41% <0.00%> (+1.43%) ⬆️
pkg/reconciler/configuration/configuration.go 88.28% <0.00%> (+1.56%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update edf5ae0...e084813. Read the comment docs.

@julz
Copy link
Member Author

julz commented Jan 7, 2021

/test pull-knative-serving-istio-stable-no-mesh

@mattmoor
Copy link
Member

mattmoor commented Jan 7, 2021

/lgtm
/approve

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 7, 2021
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: julz, mattmoor

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 7, 2021
@julz
Copy link
Member Author

julz commented Jan 8, 2021

/retest

@knative-prow-robot knative-prow-robot merged commit be44108 into knative:master Jan 8, 2021
nak3 pushed a commit to nak3/serving that referenced this pull request Jan 21, 2021
…e#10503)

* Bump deps

* Use spec.Namespace to prevent collisions rather than ownerRef

* one import path to rule them all
nak3 pushed a commit to nak3/serving that referenced this pull request Jan 21, 2021
…e#10503)

* Bump deps

* Use spec.Namespace to prevent collisions rather than ownerRef

* one import path to rule them all
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/API API objects and controllers cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DomainMapping -> DomainClaim relationship doesn't play nice with new behaviour in k8s 1.20+
4 participants