• Joel Smith's avatar
    Rework method of updating atomic-updated data volumes · b4e09237
    Joel Smith authored
    This change affects the way that secret, configmap, downwardAPI and projected
    volumes (which all use the same underlying code) implement their data update
    functionality.
    
    * Instead of creating a subdirectory hierarchy that itself
      will contain symlinks to each actual data file, create only
      symlinks to items in the root of the volume, whether they
      be files or directories.
    * Rather than comparing the user-visible data directory
      to see if an update is needed, compare with the current
      version of the data directory.
    * Fix data dir timestamp format year
    * Create ..data symlink even when a data volume has no data so
      consumers can have simplified update watch logic.
    b4e09237
Name
Last commit
Last update
..
api Loading commit data...
apis Loading commit data...
auth Loading commit data...
bootstrap/api Loading commit data...
capabilities Loading commit data...
client Loading commit data...
cloudprovider Loading commit data...
controller Loading commit data...
credentialprovider Loading commit data...
features Loading commit data...
fieldpath Loading commit data...
generated Loading commit data...
kubeapiserver Loading commit data...
kubectl Loading commit data...
kubelet Loading commit data...
kubemark Loading commit data...
master Loading commit data...
printers Loading commit data...
probe Loading commit data...
proxy Loading commit data...
quota Loading commit data...
registry Loading commit data...
routes Loading commit data...
security Loading commit data...
securitycontext Loading commit data...
serviceaccount Loading commit data...
ssh Loading commit data...
util Loading commit data...
version Loading commit data...
volume Loading commit data...
watch Loading commit data...
.import-restrictions Loading commit data...
BUILD Loading commit data...
OWNERS Loading commit data...