labels.search_related_queries=Gerelateerde zoekopdrachten:
labels.search_result_select_sort=-  Sorteren  -
labels.search_result_select_num=- Aantal resultaten -
labels.search_result_sort_score_desc=Op score
labels.search_result_sort_filename_asc=Bestandsnaam (oplopend)
labels.search_result_sort_filename_desc=Bestandsnaam (aflopend)
labels.search_result_sort_created_asc=Datum (oplopend)

- Client-go: default informer behavior now updates store state with all the objects in a list or relist, before calling handler OnDelete/OnAdd/OnUpdate methods for individual items which were deleted/added/removed. This ensures that the store state which can be inspected by handlers actually corresponds to a set of objects that existed at a particular resource version on the server. This behavior...

        map.put(FieldNames.ROLES, new String[] {});
        map.put(FieldNames.LANGUAGES, new String[] {});
        map.put(FieldNames.KINDS, new String[] {});
        map.put(FieldNames.SCORE, 1.0F);
        map.put(FieldNames.QUERY_FREQ, 0L);
        map.put(FieldNames.DOC_FREQ, 0L);
        map.put(FieldNames.USER_BOOST, 1.0F);

labels.search_popular_word_word=Mots populaires :
labels.search_related_queries=Mots associés :
labels.search_result_select_sort=- Trier -
labels.search_result_select_num=- Nombre d'affichages -
labels.search_result_sort_score_desc=par score
labels.search_result_sort_filename_asc=par nom de fichier (asc)
labels.search_result_sort_filename_desc=par nom de fichier (desc)
labels.search_result_sort_created_asc=par date (asc)

					<la:select property="sort" styleId="sortSearchOption" styleClass="form-control">
						<option value="">
							<la:message key="labels.search_result_select_sort" />
						</option>
						<la:option value="score.desc">
							<la:message key="labels.search_result_sort_score_desc" />
						</la:option>
						<la:option value="filename.asc">
							<la:message key="labels.search_result_sort_filename_asc" />
						</la:option>

					<la:select property="sort" styleId="sortSearchOption" styleClass="form-control">
						<option value="">
							<la:message key="labels.search_result_select_sort" />
						</option>
						<la:option value="score.desc">
							<la:message key="labels.search_result_sort_score_desc" />
						</la:option>
						<la:option value="filename.asc">
							<la:message key="labels.search_result_sort_filename_asc" />
						</la:option>

        assertEquals(25L, source.get(FieldNames.DOC_FREQ));
        assertEquals(2.0f, source.get(FieldNames.USER_BOOST));
        assertEquals(150.0f, source.get(FieldNames.SCORE)); // (50 + 25) * 2.0 = 150

        assertNotNull(source.get(FieldNames.READING_PREFIX + "0"));
        assertNotNull(source.get(FieldNames.READING_PREFIX + "1"));

        }

    }

    private static class MockSearchRequestParams extends SearchRequestParams {
        private String query = "test query";
        private String[] languages;
        private String sort = "score.desc";
        private int pageSize = 10;
        private int startPosition = 0;
        private SearchRequestType type = SearchRequestType.SEARCH;
        private Locale locale = Locale.ENGLISH;

        @Override

    * Function is disabled by default and can be enabled via scheduler policy config file.
    * If no parametrization is specified in config file it defaults to one which gives score 10 to utilization 0 and score 0 to utilization 100.

- Pod Affinity/AntiAffinity label selectors are now validated in the pod affinity score plugin ([#93758](https://github.com/kubernetes/kubernetes/pull/93758), [@damemi](https://github.com/damemi)) [SIG Scheduling]