Before upgrading to Kubernetes 1.13, you must keep the following in mind:

- kube-apiserver

### Storage Capacity and Volume Expansion Are Generally Available

[Storage capacity tracking](https://github.com/kubernetes/enhancements/issues/1472)
supports exposing currently available storage capacity via [CSIStorageCapacity objects](https://kubernetes.io/docs/concepts/storage/storage-capacity/#api)
and enhances scheduling of pods that use CSI volumes with late binding.

### SIG Storage

[SIG Storage][] is responsible for storage and volume plugin components.

For the 1.8 release, SIG Storage extended the Kubernetes storage API. In addition to providing simple
volume availability, the API now enables volume resizing and snapshotting. These features are in alpha.
The SIG also focused on providing more control over storage: the ability to set requests and

import jcifs.internal.smb2.Smb2Constants;
import jcifs.internal.util.SMBUtil;

/**
 * SMB2 Flush request message.
 *
 * This command is used to flush buffered data to the
 * underlying storage device for a given file handle.
 *
 * @author mbechler
 */
public class Smb2FlushRequest extends ServerMessageBlock2Request<Smb2FlushResponse> implements RequestWithFileId {

    private byte[] fileId;

    /**

     */
    protected boolean isFileSystemPath(final String url) {
        return url.startsWith("file:") || url.startsWith("smb:") || url.startsWith("smb1:") || url.startsWith("ftp:")
                || url.startsWith("storage:");
    }

- Fixed a storage bug around multipath. iSCSI and Fibre Channel devices attached to nodes via multipath now resolve correctly if partitioned. ([#129183](https://github.com/kubernetes/kubernetes/pull/129183), [@RomanBednar](https://github.com/RomanBednar)) [SIG Storage]

import org.apache.maven.api.annotations.Provider;
import org.apache.maven.api.annotations.ThreadSafe;

/**
 * A container for data that is specific to a session.
 * All components may use this storage to associate arbitrary data with a session.
 * <p>
 * Unlike a cache, this session data is not subject to purging. For this same reason, session data should also not be

        return fileAuthenticationBhv.selectByPK(id);
    }

    /**
     * Stores a file authentication configuration.
     * The parameters are encrypted before storage for security.
     *
     * @param fileAuthentication the file authentication configuration to store
     */
    public void store(final FileAuthentication fileAuthentication) {

            "The TID specified was invalid.", "The handle is invalid.", "The network name cannot be found.",
            "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
            "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",

            "The TID specified was invalid.", "The handle is invalid.", "The network name cannot be found.",
            "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
            "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",