Correctly dump logs from init containers names on CI failure

[turbaszek]

------- webserver init container logs - init -------
error: container init is not valid for pod airflow-594f8b87d-6ph6k

---

Make sure to mark the boxes below before creating PR: [x]

• Description above provides context of the change
• Unit tests coverage for changes (not needed for documentation changes)
• Target Github ISSUE in description if exists
• Commits follow "How to write a good git commit message"
• Relevant documentation is updated including usage instructions.
• I will engage committers as explained in Contribution Workflow Example.

---

In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.

[potiuk]

Indeed. good catch. - just one left-over with commented lines.

[turbaszek]

Hi @dimberman @potiuk it seems we have a problem with k8s ci builds:

psycopg2.OperationalError: could not translate host name "postgres-airflow" to address: Temporary failure in name resolution

[dimberman]

@potiuk could this have to do with moving to host?

[turbaszek]

This seems to be not related change but looking at commit history this problem persists since
#9207

[dimberman]

@turbaszek please let me know if this is the solution. cc: @mik-laj.

[turbaszek]

@dimberman as expected, this wasn't an issue. I've rebased to the first commit. Any ideas about what could have happened?

[ashb]

I think with #9230 this isn't needed anymore

[turbaszek]

@ashb do those artifacts include logs from pods' containers including inits?

[potiuk]

Yep. Those are done with kind logs export (we had them before they were just not called after the recent refactor). 'kind export logs' export EVERYTHING. It's the debug feature of kind which is on its own debug version of Kubernetes cluster :)