* your own escapers, use {@link CharEscaperBuilder}, or extend {@code CharEscaper} or {@code
 * UnicodeEscaper}.
 *
 * @author David Beaumont
 * @since 15.0
 */
@DoNotMock("Use Escapers.nullEscaper() or another methods from the *Escapers classes")
@GwtCompatible
@SuppressWarnings("EscapedEntity") // We do mean for the user to see "<" etc.
public abstract class Escaper {

     */
    @Nonnull
    Optional<Source> getProjectSettingsSource();

    /**
     * Gets the user settings source.
     *
     * @return the user settings source or {@code null} if none
     */
    @Nonnull
    Optional<Source> getUserSettingsSource();

    /**
     * The optional interpolation source used for interpolation.
     *
     * @return the interpolation source for interpolation
     */
    @Nonnull

  /** Returns an unmodifiable iterator across the elements in this collection. */
  @Override
  public abstract UnmodifiableIterator<E> iterator();

  @Override
  @IgnoreJRERequirement // used only from APIs with Java 8 types in them
  // (not used within guava-android as of this writing, but we include it in the jar as a test)
  public Spliterator<E> spliterator() {
    return Spliterators.spliterator(this, SPLITERATOR_CHARACTERISTICS);
  }

    protected String defaultField = Constants.DEFAULT_FIELD;

    /** The analyzer used to analyze query terms */
    protected Analyzer analyzer = new WhitespaceAnalyzer();

    /** Whether to allow leading wildcards in query terms */
    protected boolean allowLeadingWildcard = true;

    /** The default operator to use between query terms */
    protected Operator defaultOperator = Operator.AND;

* `kubectl create rolebinding` and `kubectl create clusterrolebinding` invocations must be updated to  specify multiple subjects as repeated  `--user`, `--group`, or `--serviceaccount` arguments instead of comma-separated arguments to a single `--user`, `--group`, or `--serviceaccount`.  E.g. `--user=x,y` must become `--user x --user y`  ([#43903](https://github.com/kubernetes/kubernetes/pull/43903), [@xilabao](https://github.com/xilabao))


### kubeadm

 * <p>As this interface extends {@code java.util.function.Function}, an instance of this type can be
 * used as a {@code java.util.function.Function} directly. To use a {@code
 * java.util.function.Function} in a context where a {@code com.google.common.base.Function} is
 * needed, use {@code function::apply}.
 *
 * <p>This interface is now a legacy type. Use {@code java.util.function.Function} (or the

 * </ul>
 *
 * <p>Dependencies:</p>
 * <ul>
 *   <li>{@code ArraySettings} - Used to manage the array settings for elevate words.</li>
 *   <li>{@code SuggestSettings} - The suggestion settings.</li>
 *   <li>{@code Client} - The client used for accessing the settings.</li>
 * </ul>
 *
 * <p>Logging:</p>
 * <ul>
 *   <li>Uses {@code Logger} to log debug information when adding, deleting, or deleting all elevate words.</li>

/// note

If you use a response class with no media type, FastAPI will expect your response to have no content, so it will not document the response format in its generated OpenAPI docs.

///

## Use `ORJSONResponse` { #use-orjsonresponse }

  * `--admission-control=...,PodSecurityPolicy,...`
* Use authorization to limit users' ability to use specific PodSecurityPolicy objects

**What is the impact?**

A user that is authorized to create pods can make use of any existing PodSecurityPolicy, even ones they are not authorized to use.

**How can I mitigate this prior to installing 1.5.5?**

    * Generating **automatic errors** returned to the client when the data is invalid.
* **Document** the API using OpenAPI:
    * which is then used by the automatic interactive documentation user interfaces.

This might all sound abstract. Don't worry. You'll see all this in action in the [Tutorial - User Guide](tutorial/index.md){.internal-link target=_blank}.