# negation (prefixed with !). Only one pattern per line.
.DS_Store
# Common VCS dirs
.git/
.gitignore
.bzr/
.bzrignore
.hg/
.hgignore
.svn/
# Common backup files
*.swp
*.bak
*.tmp
*~
# Various IDEs
.project
.idea/
*.tmproj
# OWNERS file for Kubernetes

  }

  @Synchronized
  @Throws(IOException::class)
  fun initialize() {
    this.assertThreadHoldsLock()

    if (initialized) {
      return // Already initialized.
    }

    // If a bkp file exists, use it instead.
    if (fileSystem.exists(journalFileBackup)) {
      // If journal file also exists just delete backup file.

irreversible.**  To rollback, you must restore from a backup made before the
protobuf/etcd3 switch, and any changes since the backup will be lost.  As 1.5
does not support protobuf encoding, if you roll back to 1.5 after upgrading to
protobuf you will be forced to restore from backup, and you will lose any changes
since you converted to protobuf.  After conversion to protobuf, you should

pkg syscall (windows-386), const FILE_BEGIN = 0
pkg syscall (windows-386), const FILE_CURRENT = 1
pkg syscall (windows-386), const FILE_END = 2
pkg syscall (windows-386), const FILE_FLAG_BACKUP_SEMANTICS = 33554432
pkg syscall (windows-386), const FILE_FLAG_OVERLAPPED = 1073741824
pkg syscall (windows-386), const FILE_LIST_DIRECTORY = 1
pkg syscall (windows-386), const FILE_MAP_COPY = 1

  - The deprecated `--etcd-quorum-read` flag has been removed. Quorum reads are now always enabled when fetching data from etcd. Remove the `--etcd-quorum-read` flag from kube-apiserver invocations before upgrading....

pkg syscall (windows-386), const FILE_BEGIN ideal-int
pkg syscall (windows-386), const FILE_CURRENT ideal-int
pkg syscall (windows-386), const FILE_END ideal-int
pkg syscall (windows-386), const FILE_FLAG_BACKUP_SEMANTICS ideal-int
pkg syscall (windows-386), const FILE_FLAG_OVERLAPPED ideal-int
pkg syscall (windows-386), const FILE_LIST_DIRECTORY ideal-int
pkg syscall (windows-386), const FILE_MAP_COPY ideal-int

- Kubeadm now includes CoreDNS version 1.6.7 ([#86260](https://github.com/kubernetes/kubernetes/pull/86260), [@rajansandeep](https://github.com/rajansandeep)) [SIG Cluster Lifecycle]
- Kubeadm upgrades always persist the etcd backup for stacked ([#86861](https://github.com/kubernetes/kubernetes/pull/86861), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle]

- `kubeadm`: `crictl pull` should use `-i` to set the image service endpoint. ([#117835](https://github.com/kubernetes/kubernetes/pull/117835), [@pacoxu](https://github.com/pacoxu))
- `kubeadm`: fixed a bug where file copy(backup) could not be executed correctly
  on Windows platform during upgrade. ([#117861](https://github.com/kubernetes/kubernetes/pull/117861), [@SataQiu](https://github.com/SataQiu))

### Create a backup job

#### Backup Virtual Machines with Veeam Backup and Replication

    // Cause the rebuild action to fail.
    filesystem.setFaultyRename(cacheDir / DiskLruCache.JOURNAL_FILE_BACKUP, true)
    taskFaker.runNextTask()
    assertThat(cache.remove("a")).isTrue()
    assertAbsent("a")

    // Let the rebuild complete successfully.
    filesystem.setFaultyRename(cacheDir / DiskLruCache.JOURNAL_FILE_BACKUP, false)
    taskFaker.runNextTask()
    assertJournalEquals("CLEAN b 1 1")
  }