and is deleted after 24 hours by default to limit the exposure of the
 valuable credential. You can create a new Bootstrap Token with
 `kubeadm token create` or make the default token permanently valid by specifying
 `--token-ttl 0` to `kubeadm init`. The default token can later be deleted with
 `kubeadm token delete`.

                    logger.warn("Thumbnail File is empty. ID is {}", thumbnailId);
                    if (outputFile.delete()) {
                        logger.info("Deleted: {}", outputFile.getAbsolutePath());
                    }
                    updateThumbnailField(thumbnailId, StringUtil.EMPTY);
                    return false;
                }

                if (logger.isDebugEnabled()) {

     * Before upgrading to 1.2, <strong>delete all DaemonSet alpha-version resources</strong>. If you do not want to disrupt the pods, use kubectl delete daemonset <name>
--cascade=false. Then create DaemonSet Beta resources after upgrading to 1.2.
     * Client (kubectl) and server versions must match (both 1.1 or both 1.2) for any
DaemonSet-related operations.
     * Behavior change:

    cache.close()
    createNewCache()

    // The journal will have no record that 'a' was removed. It will have an entry for 'a', but when
    // it tries to read the cache files, it will find they were deleted. Once it encounters an entry
    // with missing cache files, it should remove it from the cache entirely.
    assertThat(cache.size()).isEqualTo(4)
    assertThat(cache["a"]).isNull()

  - The `Node` authorization mode no longer allows kubelets to delete their Node API objects (prior to 1.11, in rare circumstances related to cloudprovider node ID changes, kubelets would attempt to delete/recreate their Node object at startup) ([#71021](https://github.com/kubernetes/kubernetes/pull/71021), [@liggitt](https://github.com/liggitt))

...

- To avoid soft-deleted pods incorrectly affecting scale up replica count calculations, the HPA controller will stop counting soft-deleted pods for scaling purposes. ([#67067](https://github.com/kubernetes/kubernetes/pull/67067), [@moonek](https://github.com/moonek))

# five framework-embedded messages (don't change key names)
# - - - - - - - - - -/
errors.login.failure = Inloggen mislukt.
errors.app.illegal.transition = Illegale overgang. Probeer het opnieuw.
errors.app.db.already.deleted = Mogelijk is het al verwijderd door een ander proces. Probeer de bewerking opnieuw.
errors.app.db.already.updated = Mogelijk is het al bijgewerkt door een ander proces. Probeer de bewerking opnieuw.

# five framework-embedded messages (don't change key names)
# - - - - - - - - - -/
errors.login.failure = Ошибка входа.
errors.app.illegal.transition = Недопустимый переход. Пожалуйста, попробуйте еще раз.
errors.app.db.already.deleted = Возможно, он был удален другим процессом. Пожалуйста, попробуйте еще раз.
errors.app.db.already.updated = Возможно, он был обновлен другим процессом. Пожалуйста, попробуйте еще раз.

# five framework-embedded messages (don't change key names)
# - - - - - - - - - -/
errors.login.failure = 로그인에 실패했습니다.
errors.app.illegal.transition = 잘못된 전환입니다. 다시 시도하십시오.
errors.app.db.already.deleted = 다른 프로세스에 의해 삭제되었을 수 있습니다. 다시 시도하십시오.
errors.app.db.already.updated = 다른 프로세스에 의해 업데이트되었을 수 있습니다. 다시 시도하십시오.
errors.app.db.already.exists = 데이터가 이미 존재합니다. 다시 시도하십시오.