0.13 release in serving failed due to auto tls test failure

[chaodaiG]

Knative 0.13 release failed due to auto tls test failure, and the root cause is that auto tls test relies on service account for talking to dns server, and it doesn't exist in auto release job. See example failure: https://prow.knative.dev/view/gcs/knative-prow/logs/ci-knative-serving-auto-release/1234880014055378945

The release was done by a hacky way to unblock releasing, by manually mounting the service account to the job, and kicked off manually here: https://prow.knative.dev/view/gcs/knative-prow/logs/ci-knative-serving-auto-release/1234940914212802561

The fix above was a one-time thing, if there is any new release come up it'll fail the same way, so we need a long term fix.

[Note] We don't want 0.13.1 being released just because of this fix, as the binaries being released will be identical to 0.13.0

[chaodaiG]

/kind bug

[knative-prow-robot]

@chaodaiG: The label(s) kind/bug cannot be applied, because the repository doesn't have them

In response to this:

/kind bug

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.

[chaodaiG]

/bug
/assign @nbarthwal

[knative-housekeeping-robot]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle stale.
Stale issues rot after an additional 30 days of inactivity and eventually close.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle stale

[chizhg]

/reopen

[knative-prow-robot]

@chizhg: Reopened this issue.

In response to this:

/reopen

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.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen.Mark the issue as
fresh by adding the comment /remove-lifecycle stale.