Support log retrieval on MultiKueue

[rochaporto]

What would you like to be added:

We would like to be able to retrieve logs from MultiKueue workloads, directly from the master cluster.

Why is this needed:

Multiple tools running on top of Kubernetes rely on the log retrieval API to give live feedback to users.

Examples include:

• The GitLab CI Kubernetes executor (https://docs.gitlab.com/runner/executors/kubernetes/) relies on the logs functionality to provide CI job logs to the users
• The Kubeflow jobs also integrate with log retrieval to display live feedback to users in the different dashboards ()

Completion requirements:

This enhancement requires the following artifacts:

• Design doc
• API change
• Docs update

The artifacts should be linked in subsequent comments.

[Horiodino]

/assign

[tenzen-y]

Note that this needs for KEP, first.

[rochaporto]

Note that this needs for KEP, first.

Should i help with this? Happy to join a meeting and discuss the use case in more detail if needed.

[Horiodino]

Hii ,Please let me know if there's an opportunity for me to assist or join any discussions related to this enhancement.

[asaiacai]

likewise, i am interested in this feature/enhancement.

[tenzen-y]

My first key question is the interface where we expose Worker clusters logs in the Management cluster. kubectl logs? dedicated Web console? or cli tools?

[Horiodino]

i believe we should expose a centralized API endpoint in the management cluster . This would allow tools like GitLab CI or Kubeflow to integrate easily without requiring direct access to worker clusters. Additionally, this approach would make it reliable and flexible for others to add a web console or CLI tools for log retrieval and interaction as needed. What you think !

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[tenzen-y]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale