• Danielle Lancashire's avatar
    CSI Plugin Registration (#6555) · d296efd2
    Danielle Lancashire authored
    This changeset implements the initial registration and fingerprinting
    of CSI Plugins as part of #5378. At a high level, it introduces the
    following:
    
    * A `csi_plugin` stanza as part of a Nomad task configuration, to
      allow a task to expose that it is a plugin.
    
    * A new task runner hook: `csi_plugin_supervisor`. This hook does two
      things. When the `csi_plugin` stanza is detected, it will
      automatically configure the plugin task to receive bidirectional
      mounts to the CSI intermediary directory. At runtime, it will then
      perform an initial heartbeat of the plugin and handle submitting it to
      the new `dynamicplugins.Registry` for further use by the client, and
      then run a lightweight heartbeat loop that will emit task events
      when health changes.
    
    * The `dynamicplugins.Registry` for handling plugins that run
      as Nomad tasks, in contrast to the existing catalog that requires
      `go-plugin` type plugins and to know the plugin configuration in
      advance.
    
    * The `csimanager` which fingerprints CSI plugins, in a similar way to
      `drivermanager` and `devicemanager`. It currently only fingerprints
      the NodeID from the plugin, and assumes that all plugins are
      monolithic.
    
    Missing features
    
    * We do not use the live updates of the `dynamicplugin` registry in
      the `csimanager` yet.
    
    * We do not deregister the plugins from the client when they shutdown
      yet, they just become indefinitely marked as unhealthy. This is
      deliberate until we figure out how we should manage deploying new
      versions of plugins/transitioning them.
    d296efd2