Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix pause/resume actions #2

Merged
merged 1 commit into from
Apr 12, 2019
Merged

Fix pause/resume actions #2

merged 1 commit into from
Apr 12, 2019

Conversation

tvansteenburgh
Copy link
Contributor

Fixes
lp:1824428

  1. Rewrite actions to python so we can used get_host_name() from
    kubernetes_common. Using get_host_name() fixes the issue reported
    in the bug by returning the fqdn if a cloud integrator is being used.
  2. Remove the kubectl cordon call from the pause action as it's
    redundant - kubectl drain does a cordon first.
  3. Add --ignore-daemonsets as a default arg to kubectl drain. DS pods
    can't be drained as they would be immediately rescheduled by the DS
    controller, which ignores 'unschedulable' taints on the node.
  4. Update action descriptions to more closely match upstream docs.

Fixes
[lp:1824428](https://bugs.launchpad.net/charm-kubernetes-worker/+bug/1824428)

1. Rewrite actions to python so we can used get_host_name() from
   kubernetes_common. Using get_host_name() fixes the issue reported
   in the bug by returning the fqdn if a cloud integrator is being used.
2. Remove the `kubectl cordon` call from the pause action as it's
   redundant - `kubectl drain` *does* a cordon first.
3. Add --ignore-daemonsets as a default arg to `kubectl drain`. DS pods
   can't be drained as they would be immediately rescheduled by the DS
   controller, which ignores 'unschedulable' taints on the node.
4. Update action descriptions to more closely match upstream docs.
@Cynerva
Copy link
Contributor

Cynerva commented Apr 12, 2019

LGTM 👍

@Cynerva Cynerva merged commit 15e9933 into master Apr 12, 2019
@Cynerva Cynerva deleted the lp-1824428 branch April 12, 2019 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants