Skip copying over kubectl.kubernetes.io/last-applied-configuration annotation

[skaslev]

Skip copying over kubectl.kubernetes.io/last-applied-configuration annotation
when creating new Configurations and Routes from Knative Services.

/lint

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[knative-prow-robot]

@skaslev: 0 warnings.

In response to this:

Skip copying over kubectl.kubernetes.io/last-applied-configuration annotation
when creating new Configurations and Routes from Knative Services.

/lint

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.

[knative-prow-robot]

Hi @skaslev. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[markusthoemmes]

Do we need to apply this everywhere where child-resources get created?

[skaslev]

Hm, I think my employer @vmware should have signed the CLA already. I just joined the https://github.com/vmware organization to see if this makes a difference.

@googlebot I signed it!

[dgerd]

/ok-to-test

[vagababov]

Can we have a test?

[skaslev]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[skaslev]

/assign @dprotaso

[dprotaso]

/approve

[markusthoemmes]

I think the test comment is not resolved yet? Can we add a test?

[skaslev]

Sure, I misunderstood @vagababov comment was about this PR needing a test run.

[vagababov]

Stylistic issues.

[dprotaso]

build failed due to some memory issue

/test pull-knative-serving-build-tests

[dprotaso]

/lgtm
/approve

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, skaslev

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:

• pkg/reconciler/OWNERS [dprotaso]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vagababov]

/lgtm

[skaslev]

/retest

[knative-test-reporter-robot]

The following jobs failed due to test flakiness:

Test name	Triggers	Retries
pull-knative-serving-integration-tests	pull-knative-serving-integration-tests pull-knative-serving-integration-tests	2/3

Automatically retrying...
/test pull-knative-serving-integration-tests