Project pod name as env var in our deployments

[pierDipi]

• Inject the pod name into logger when provided in the envvars pkg#1714

Proposed Changes

• Project pod name as env var in our deployments

[knative-test-reporter-robot]

The following jobs failed:

Test name	Triggers	Retries
pull-knative-eventing-conformance-tests		0/3

Failed non-flaky tests preventing automatic retry of pull-knative-eventing-conformance-tests:

test/conformance.TestBrokerV1Beta1DataPlaneConsumer/MTChannelBasedBroker-eventing.knative.dev/v1beta1/Events_are_filtered
test/conformance.TestBrokerV1Beta1DataPlaneConsumer/MTChannelBasedBroker-eventing.knative.dev/v1beta1
test/conformance.TestBrokerV1Beta1DataPlaneConsumer

[aliok]

/retest

[pierDipi]

    operation.go:73: Object that did not become ready {pod v1}-first-filtered-event-sender when dumping error state: &{TypeMeta:{Kind:Pod APIVersion:v1} ObjectMeta:{Name:first-filtered-event-sender GenerateName: Namespace:test-broker-v1-beta1-data-plane-consumer-pb42g SelfLink:/api/v1/namespaces/test-broker-v1-beta1-data-plane-consumer-pb42g/pods/first-filtered-event-sender UID:3bc9420d-df90-40a5-81e3-a51c4050553c ResourceVersion:12487 Generation:0 CreationTimestamp:2020-09-18 08:35:05 +0000 UTC DeletionTimestamp:<nil> DeletionGracePeriodSeconds:<nil> Labels:map[] Annotations:map[] OwnerReferences:[] Finalizers:[] ClusterName: ManagedFields:[]} Status:{ObservedGeneration:0 Conditions:[{Type:Initialized Status:True Severity: LastTransitionTime:{Inner:2020-09-18 08:35:05 +0000 UTC} Reason:PodCompleted Message:} {Type:Ready Status:False Severity: LastTransitionTime:{Inner:2020-09-18 08:35:17 +0000 UTC} Reason:PodCompleted Message:} {Type:ContainersReady Status:False Severity: LastTransitionTime:{Inner:2020-09-18 08:35:17 +0000 UTC} Reason:PodCompleted Message:} {Type:PodScheduled Status:True Severity: LastTransitionTime:{Inner:2020-09-18 08:35:05 +0000 UTC} Reason: Message:}] Annotations:map[]}}
    operation.go:75: Failed to get {pod v1}-first-filtered-event-sender ready: <nil>

I know how to fix this! 🎉
/retest

[aliok]

/lgtm
/approve

Can we have the same for the things in eventing-contrib?

[pierDipi]

I think there is a code freeze in eventing-contrib or people are moving code to sandbox, to keep track of this I would open an issue in each sandbox repository, WDYT?

[aliok]

I think there is a code freeze in eventing-contrib or people are moving code to sandbox, to keep track of this I would open an issue in each sandbox repository, WDYT?

I think that would be the approach. Let me create some tickets.

[matzew]

/lgtm
/approve

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aliok, matzew, pierDipi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [matzew]

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