Handle resource already exists in Apply

[pierDipi]

We're getting already exists errors when applying the same resource in parallel tests.

    logger.go:146: 2024-09-20T11:05:08.890Z	FATAL	environment/magic.go:243	failed to install CA certificates and issuer: failed to create resource certificates.cert-manager.io "selfsigned-ca" already exists - Resource:
        apiVersion: cert-manager.io/v1
        kind: Certificate
        metadata:
          name: selfsigned-ca
          namespace: serverless-tests
        spec:
          commonName: selfsigned-ca
          isCA: true
          issuerRef:
            group: cert-manager.io
            kind: Issuer
            name: selfsigned-issuer
          privateKey:
            algorithm: ECDSA
            size: 256
          secretName: eventshub-ca
        	{"test": "TestPingSourceTLS"}

[knative-prow]

@pierDipi: The label(s) kind/<kind> cannot be applied, because the repository doesn't have them.

In response to this:

We're getting already exists errors when applying the same resource in parallel tests.

   logger.go:146: 2024-09-20T11:05:08.890Z	FATAL	environment/magic.go:243	failed to install CA certificates and issuer: failed to create resource certificates.cert-manager.io "selfsigned-ca" already exists - Resource:
       apiVersion: cert-manager.io/v1
       kind: Certificate
       metadata:
         name: selfsigned-ca
         namespace: serverless-tests
       spec:
         commonName: selfsigned-ca
         isCA: true
         issuerRef:
           group: cert-manager.io
           kind: Issuer
           name: selfsigned-issuer
         privateKey:
           algorithm: ECDSA
           size: 256
         secretName: eventshub-ca
       	{"test": "TestPingSourceTLS"}

Changes

/kind

Fixes #

Release Note

Docs

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-sigs/prow repository.

[pierDipi]

/cherry-pick release-1.15

[knative-prow-robot]

@pierDipi: once the present PR merges, I will cherry-pick it on top of release-1.15 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.15

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-sigs/prow repository.

[pierDipi]

/cherry-pick release-1.14

[knative-prow-robot]

@pierDipi: once the present PR merges, I will cherry-pick it on top of release-1.14 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.14

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-sigs/prow repository.

[cardil]

/lgtm

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cardil, pierDipi

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:

• OWNERS [cardil,pierDipi]

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]

@pierDipi: new pull request created: #760

In response to this:

/cherry-pick release-1.15

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-sigs/prow repository.

[knative-prow-robot]

@pierDipi: new pull request created: #761

In response to this:

/cherry-pick release-1.14

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-sigs/prow repository.