You could fist upgrade Pydantic to use the latest version 2, and change the imports to use `pydantic.v1` for all your models.

             * resolveCoreExtension method which uses a CoreExtension
             * object instead of a Plugin as this makes no sense.
             */
            Plugin plugin = Plugin.newBuilder()
                    .groupId(interpolator.apply(extension.getGroupId()))
                    .artifactId(interpolator.apply(extension.getArtifactId()))
                    .version(interpolator.apply(extension.getVersion()))
                    .build();

			<arg>"fess_user.user/user"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_user.role/role"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_user.group/group"</arg>
		</postConstruct>
		<!-- fess_log index -->
		<postConstruct name="addIndexConfig">
			<arg>"fess_log.click_log/click_log"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">

    You could have custom internal logic to separate it by colon characters (`:`) or
    similar, and get the two parts `items` and `read`. Many applications do that to
    group and organize permissions, you could do it as well in your application, just
    know that that it is application specific, it's not part of the specification.
    """

    def __init__(
        self,
        *,

		t.Errorf("joins should be ordered, but got %v", stmt.SQL.String())
	}

	iv := DB.Table(`table_invoices`).Select(`seller, SUM(total) as total, SUM(paid) as paid, SUM(balance) as balance`).Group(`seller`)
	stmt = dryDB.Table(`table_employees`).Select(`id, name, iv.total, iv.paid, iv.balance`).Joins(`LEFT JOIN (?) AS iv ON iv.seller = table_employees.id`, iv).Scan(&user).Statement

    /** The key of the message: Geo */
    public static final String LABELS_GEO = "{labels.geo}";

    /** The key of the message: Groups */
    public static final String LABELS_GROUPS = "{labels.groups}";

    /** The key of the message: Hash */
    public static final String LABELS_HASH = "{labels.hash}";

    /** The key of the message: Max Size */

                                    </c:if>
                                </h3>
                                <div class="card-tools">
                                    <div class="btn-group">
                                        <la:link href="/admin/crawlinginfo"
                                                 styleClass="btn btn-primary btn-xs">

                                <la:message key="labels.dict_protwords_list_link"/>
                            </h3>
                            <div class="card-tools">
                                <div class="btn-group">
                                    <la:link href="/admin/dict" styleClass="btn btn-default btn-xs">
                                        <i class="fa fa-book" aria-hidden="true"></i>

										</c:if>
									</c:forEach>
								</p>
							</div>
						</c:if>
						<div class="clearfix searchButtonBox btn-group">
							<button type="submit" name="search" id="searchButton"
								class="btn btn-primary">
								<i class="fa fa-search" aria-hidden="true"></i>
								<la:message key="labels.index_form_search_btn" />

`kubeadm`: a separate "super-admin.conf" file is now deployed. The User in `admin.conf` is now bound to a new RBAC Group `kubeadm:cluster-admins` that has `cluster-admin` `ClusterRole` access. The User in `super-admin.conf` is now bound to the `system:masters` built-in super-powers / break-glass Group that can bypass RBAC. Before this change, the default `admin.conf` was bound to `system:masters` Group, which was undesired. Executing `kubeadm init phase kubeconfig all` or just `kubeadm init` will now generate...