I took this feedback and updated the PR upstream. The new action descriptions will go out with the next publication of the charm.
https://github.com/kubernetes/kubernetes/pull/31202 If there are any further feedback items about the action descriptions it would be great to capture them on the bug so we can settle on crisp messaging to the end user what exactly is happening. I moved the longer descriptions to the README, so the full text wasn't lost and it's very clear to the end user what the actions are doing on their behalf. All the best, Charles On Tue, Aug 23, 2016 at 7:03 AM Mark Shuttleworth <[email protected]> wrote: > > Working with the Kubernetes charms today (thanks Chuck & friends) I saw > this: > > > $ juju list-actions kubernetes > ACTION DESCRIPTION > clean-containers Garbage collect non-running containers > clean-images Garbage collect non-running images > guestbook-example Launch the guestbook example in your k8s cluster > microbot Launch microbot containers > pause Cordon the unit, pausing all future workload > scheduling on this unit, > and drains active workloads > resume UnCordon the unit, enabling workload scheduling. Workloads > will automatically balance into the unit > > > The fact that we have a bunch of useful operational actions crowdsources > for Kubernetes is brilliant, but the way that list gets wonky towards > the end with overrunning text lines is a niggle. Should we just > hard-truncate such descriptions in a single line, so reinforce the > social contract around keeping those summaries one-line friendly? > > > Mark > > > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Juju Charmer Canonical Group Ltd. Ubuntu - Linux for human beings | www.ubuntu.com Juju - The fastest way to model your service | www.jujucharms.com
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
