to be FIPS 140-2 compliant with the use of the BouncyCastle FIPS approved Security Provider.
FIPS 140-2 imposes certain requirements that affect how our tests should be set up or what
can be tested. This section summarizes what one needs to take into consideration so that
tests won't fail when run in fips mode.

=== Muting tests in FIPS 140-2 mode

     * omitting the middle section, and appends source titles.
     *
     * @param msg the assistant chat message
     * @param maxChars the maximum characters for the summary
     * @return the summarized content with source titles
     */
    protected String buildSmartSummaryContent(final ChatMessage msg, final int maxChars) {
        final String content = msg.getContent();
        if (content == null) {

* Support struct,array,slice types when sorting kubectl output ([#25022](https://github.com/kubernetes/kubernetes/pull/25022), [@zhouhaibing089](https://github.com/zhouhaibing089))
* federated api servers: Adding a discovery summarizer server ([#20358](https://github.com/kubernetes/kubernetes/pull/20358), [@nikhiljindal](https://github.com/nikhiljindal))

    to control the order of logical devices (GPU only).

*   `tf.keras`:

    *   Changed the TensorBoard tag names produced by the
        `tf.keras.callbacks.TensorBoard` callback, so that summaries logged
        automatically for model weights now include either a `/histogram` or
        `/image` suffix in their tag names, in order to prevent tag name
        collisions across summary types.

* Make discovery summarizer call servers in parallel ([#26705](https://github.com/kubernetes/kubernetes/pull/26705), [@nebril](https://github.com/nebril))

- Kube-scheduler now logs plugin scoring summaries at --v=4 ([#99411](https://github.com/kubernetes/kubernetes/pull/99411), [@damemi](https://github.com/damemi)) [SIG Scheduling]