Containers Kubernetes Worker

  • Canonical Kubernetes
Channel Revision Published Runs on
latest/stable 838 16 Dec 2021
Ubuntu 20.04 Ubuntu 18.04 Ubuntu 16.04
latest/candidate 816 26 Oct 2021
Ubuntu 20.04 Ubuntu 18.04 Ubuntu 16.04
latest/beta 838 15 Dec 2021
Ubuntu 20.04 Ubuntu 18.04 Ubuntu 16.04
latest/edge 851 01 Feb 2022
Ubuntu 20.04 Ubuntu 18.04 Ubuntu 16.04
juju deploy containers-kubernetes-worker
Show information

Platform:

Ubuntu
20.04 18.04 16.04

Learn about actions >

  • cis-benchmark

    Run the CIS Kubernetes Benchmark against snap-based components.

    Params
    • apply string

      Apply remediations to address benchmark failures. The default, 'none', will not attempt to fix any reported failures. Set to 'conservative' to resolve simple failures. Set to 'dangerous' to attempt to resolve all failures.

      Note: Applying any remediation may result in an unusable cluster.

    • config string

      Archive containing configuration files to use when running kube-bench. The default value is known to be compatible with snap components. When using a custom URL, append '#<hash_type>=<checksum>' to verify the archive integrity when downloaded.

    • release string

      Archive containing the 'kube-bench' binary to run. The default value points to a stable upstream release. When using a custom URL, append '#<hash_type>=<checksum>' to verify the archive integrity when downloaded.

      This may also be set to the special keyword 'upstream'. In this case, the action will compile and use a local kube-bench binary built from the master branch of the upstream repository: https://github.com/aquasecurity/kube-bench

  • debug

    Collect debug data

  • microbot

    Launch microbot containers

    Params
    • delete boolean

      Remove a microbots deployment, service, and ingress if True.

    • registry string

      Registry to use for the microbot image.

    • replicas integer

      Number of microbots to launch in Kubernetes.

  • pause

    Mark the node as unschedulable to prevent new pods from arriving, and evict existing pods.

    Params
    • delete-local-data boolean

      Continue even if there are pods using emptyDir (local data that will be deleted when the node is drained).

    • force boolean

      Continue even if there are pods not managed by a ReplicationController, ReplicaSet, Job, DaemonSet or StatefulSet.

  • resume

    Mark node as schedulable.

  • upgrade

    Upgrade the kubernetes snaps