add exec support for k8s

Bug #1876105 reported by Tom Haddon
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Confirmed
Low
Unassigned

Bug Description

The operator framework has some pretty interesting support for debugging code using the new "juju debug-code" command, but it's not currently possible to use it on k8s because there isn't yet support for exec on k8s, AIUI.

As noted in discussions with the operator developers the juju agent looks for special files to decide to run in debug mode, so we should be able to inject those via kubectl.

Revision history for this message
Gustavo Niemeyer (niemeyer) wrote :

We're working on some relevant improvements to the interactions between juju and k8s, which will make that sort of operation easier to handle. I suggest revisiting this issue after that's done.

Revision history for this message
John A Meinel (jameinel) wrote :

related to https://bugs.launchpad.net/juju/+bug/1875422 which is about general ssh/shell access to k8s nodes.

Revision history for this message
Pen Gale (pengale) wrote :

Marking as "confirmed" and "high", as this feature most likely fits in with our plans for k8s over the next few cycles.

Changed in juju:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: High → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.