• Jan Chaloupka's avatar
    Extend the current secrets mounting to volume implementation with key to path mapping. · ebe56f5f
    Jan Chaloupka authored
    The key to path mapping allows pod to specify different name (thus location) of each secret.
    At the same time refactor the volume plugin to use AtomicWritter to project secrets to files in a volume.
    
    Update e2e Secrets test, the secret file permission has changed from 0444 to 0644
    Remove TestPluginIdempotent as the AtomicWritter is responsible for secret creation
    ebe56f5f
secrets.go 4.28 KB