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

kata-deploy: Allow setting up snapshotters per runtime handler #8655

Commits on Dec 21, 2023

  1. kata-deploy: Allow setting up snapshotters per runtime handler

    Since containerd 1.7.0 we can easily set a specific snapshotter to be
    used with a runtime handler, and we should take advantage of this,
    mostly as it'll help setting up any runtime using devmapper or nydus
    snapshotters.
    
    This implementation here has a few caveats:
    * The format expected for the SNAPSHOTTER_HANDLER_MAPPING is:
      `shim:snapshotter,shim:snapshotter,...`
    * It only works with containerd 1.7 or newer
    * We **never** change the default containerd snapshotter
    * We don't do any check on our side to verify whether the snapshotter
      required is properly deployed
    * Users will have to add an annotation to their pods, in order to use
      the snapshotter set up per runtime handler
      * Example:
        ```
        metadata:
          ...
          annotations:
            io.containerd.cri.runtime-handler: kata-fc
        ```
    
    Fixes: kata-containers#8615
    
    Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
    fidencio committed Dec 21, 2023
    Configuration menu
    Copy the full SHA
    6cc6ca5 View commit details
    Browse the repository at this point in the history