* Share moved to different node - share mobility event
     */
    SHARE_MOVE(3),

    /**
     * IP address changed - network configuration change
     */
    IP_CHANGE(4),

    /**
     * Share deleted - share removal notification
     */
    SHARE_DELETE(5),

    /**
     * Cluster node unavailable - node down event
     */
    NODE_UNAVAILABLE(6),

    /**
     * Cluster node available - node up event

        It does not affect the behaviour of proxy.golang.org or the go command.
        Instead we recommend using the retract directive which will be processed by all 3 of the above.

        If you have deleted your repo, please recreate it and publish a retraction.

        Retracting a module version involves adding a retract directive to your go.mod file and publishing a new version.

  std::unique_ptr<TensorSliceReader::VarToShapeMap> var_to_shape_map_;
  std::unique_ptr<TensorSliceReader::VarToDataTypeMap> var_to_data_type_map_;

  CheckpointReader(const CheckpointReader&) = delete;
  void operator=(const CheckpointReader&) = delete;
};

}  // namespace checkpoint
}  // namespace tensorflow

- When use kubectl command to delete multiple sts pods, the kubectl command deletes pods and exits normally. ([#135563](https://github.com/kubernetes/kubernetes/pull/135563), [@yangjunmyfm192085](https://github.com/yangjunmyfm192085)) [SIG CLI, Network and Node]

### Other (Cleanup or Flake)

            if (isCommit) {
                try {
                    dictionaryManager.store(KuromojiFile.this, newFile);
                } finally {
                    newFile.delete();
                }
            } else {
                newFile.delete();
            }
        }
    }

If you use ThirdPartyResource objects, they have moved from being namespaced-scoped to be cluster-scoped. Before upgrading to 1.3.0, export and delete any existing ThirdPartyResource objects using a 1.2.x client:

kubectl get thirdpartyresource --all-namespaces -o yaml > tprs.yaml
kubectl delete -f tprs.yaml

After upgrading to 1.3.0, re-register the third party resource objects at the root scope (using a 1.3 server and client):

        entity.asDocMeta().indexOption(opLambda);
        doInsertOrUpdate(entity, null, null);
    }

    public void delete(FileAuthentication entity) {
        doDelete(entity, null);
    }

    public void delete(FileAuthentication entity, RequestOptionCall<DeleteRequestBuilder> opLambda) {
        entity.asDocMeta().deleteOption(opLambda);
        doDelete(entity, null);
    }

containing the secretKey - `users[].policy` - name of the policy to assign to user ## Uninstalling the Chart Assuming your release is named as `my-release`, delete it using the command: ```bash helm delete my-release ``` or ```bash helm uninstall my-release ``` The command removes all the Kubernetes components associated with the chart and deletes the release....

none|download|upload|public - `buckets[].purge` - purge if bucket exists already Uninstalling the Chart ---------- Assuming your release is named as `my-release`, delete it using the command: ```bash helm delete my-release ``` or ```bash helm uninstall my-release ``` The command removes all the Kubernetes components associated with the chart and deletes the release....

none|download|upload|public - `buckets[].purge` - purge if bucket exists already Uninstalling the Chart ---------- Assuming your release is named as `my-release`, delete it using the command: ```bash helm delete my-release ``` or ```bash helm uninstall my-release ``` The command removes all the Kubernetes components associated with the chart and deletes the release....