Helm chart upgrade to Rancher Prime v2.13.1 in a cluster utilizing the ingress-nginx ingress controller.
Helm Chart 升级到 Rancher Prime v2.13.1，集群中使用 ingress-nginx 入口控制器。

When performing a Helm chart upgrade of a Rancher instance to Rancher Prime v2.13.1 in a cluster with the ingress-nginx ingress controller, the upgrade fails with an error of the following format:
当在带有 ingress-nginx 入口控制器的集群中对 Rancher 实例进行 Helm 图表升级到 Rancher Prime v2.13.1 时，升级失败，格式如下：

<span style="color:#000000"><span style="background-color:#ffffff"><span style="background-color:#efefef"><code>Error: UPGRADE FAILED: failed to create resource: admission webhook "<a data-cke-saved-href="http://validate.nginx.ingress.kubernetes.io/" href="http://validate.nginx.ingress.kubernetes.io/">validate.nginx.ingress.kubernetes.io</a>" denied the request: host "<rancher-hostname>" and path "/" is already defined in ingress cattle-system/rancher</code></span></span></span>

To resolve this issue, manually delete the existing Rancher Ingress resource in the local cluster and then re-run the Helm upgrade:
要解决这个问题，请手动删除本地集群中的现有 Rancher Ingress 资源，然后重新运行 Helm 升级：

1. Delete the existing ingress: kubectl -n cattle-system delete ingress rancher
   删除现有入口： kubectl -n cattle-system delete ingress rancher
2. Re-run the Helm upgrade command.
   重新运行 Helm 升级命令。

Alternatively, to maintain the existing chart resource names, apply a nameOverride to the chart values, as documented in: Resource naming changes in Rancher Prime v2.13.1 Helm installation.
或者，为了维护现有的图表资源名称，可以对图表值应用 nameOverride，详见：Rancher Prime v2.13.1 Helm 安装中的资源命名变更。

In Rancher Prime v2.13.1, the Helm chart name was changed from rancher to rancher-prime. Because the Rancher Helm chart templates its resource names based on the chart name by default, the upgrade process attempts to create new resources (suffixed with rancher-prime) before the existing resources (named rancher) are fully removed.
在《牧场主 Prime》v2.13.1 中，Helm 排行榜名称由 rancher 改为 rancher-prime。由于牧场主头盔图表默认基于图表名称模板化资源名称，升级过程尝试在现有资源（名为牧场者 ）完全移除之前创建新资源（后缀为牧场主）。

The ingress-nginx validating webhook admission controller blocks the creation of the new rancher-rancher-prime Ingress resource because the existing rancher Ingress resource - containing the identical host and path configuration - still exists in the cluster.
ingress-nginx 验证 webhook 准入控制器阻止了新的 rancher-rancher-prime Ingress 资源的创建，因为现有的 rancher Ingress 资源——包含相同的主机和路径配置——仍然存在于集群中。

访问Rancher-K8S解决方案博主 ：https://blog.csdn.net/lidw2009