uyuni/docs installation-and-upgrade-manager-4.3-MU-4.3.11 — Chinese (China) (zh

Translation

English type: delimited block -

Chinese (China) (zh_CN)

Needs editing

Only reviewers can change approved strings, please add a suggestion if you think the string should be changed.

Skip

	English	Chinese (China) (zh_CN)	Actions
	The rest of the process is the same as for any non-public-cloud client and consists of synchronizing channels, automatic bootstrap script creation, activation key creation and starting the registration.	该过程的其余步骤与非公有云客户端的步骤相同，包括同步通道、自动创建引导脚本、创建激活密钥，以及启动注册。
	For more about registering clients, see xref:client-configuration:registration-overview.adoc[].	有关注册客户端的详细信息，请参见 xref:client-configuration:registration-overview.adoc[]。
	Troubleshooting	查错
	Checking the credentials	检查身份凭证
	If the script fails to collect the credentials, it should provide a proper error message in the logs and in the {webui}.	如果脚本无法收集身份凭证，将会在日志和 {webui} 中提供正确的错误消息。
	If the credentials are not working, [literal]``reposync`` should show the proper error.	如果身份凭证无法工作，[literal]``reposync`` 应该会显示正确的错误消息。
	Using [literal]``registercloudguest``	使用 [literal]``registercloudguest``
	Refreshing or changing the [literal]``registercloudguest`` connection to the public cloud update infrastructure should not interfere with the credentials usage.	刷新或更改 [literal]``registercloudguest`` 与公有云更新基础架构的连接不应影响身份凭证的使用。
	Running [literal]```registercloudguest --clean`` will cause problems if no new cloud connection is registered with the cloud guest command.	如果未使用 cloud guest 命令注册新的云连接，运行 [literal]``registercloudguest --clean`` 将会导致发生问题。
	Containerized proxy deployment using internal registry	使用内部注册表部署容器化代理
	It is possible to deploy containerized images in an environment without an internet connection. In such case, the images can be copied from {suse} registry to an internal registry, or saved to a [literal]``tar`` file.	您可以在未连接互联网的环境中部署容器化映像。在这种情况下，可以将映像从 {suse} 注册表复制到内部注册表，或保存到 [literal]``tar`` 文件。
	Image copying from {suse} registry to internal registry	将映像从 {suse} 注册表复制到内部注册表
	This example illustrates deployment of {salt} proxies only.	下面的示例仅说明 {salt} 代理的部署过程。
	Procedure: Deploying {salt} Proxy from an internal image registry	过程：从内部映像注册表部署 {salt} 代理
	On a machine with access to [literal]``registry.suse.com`` install [literal]``skopeo``:	在可访问 [literal]``registry.suse.com`` 的计算机上安装 [literal]``skopeo``：
	zypper in skopeo	zypper in skopeo
	This can be {productname} Server.	这可以是 {productname} 服务器。
	Copy images between registries:	在不同注册表之间复制映像：
	for image in httpd salt-broker squid ssh tftpd; do skopeo copy docker://registry.suse.com/suse/manager/4.3/proxy-$image:latest docker://<your_server>/registry.suse.com/suse/manager/4.3/proxy-$image done skopeo copy docker://k8s.gcr.io/pause:latest docker://<your_server>/k8s.gcr.io/pause:latest	for image in httpd salt-broker squid ssh tftpd; do skopeo copy docker://registry.suse.com/suse/manager/4.3/proxy-$image:latest docker://<your_server>/registry.suse.com/suse/manager/4.3/proxy-$image done skopeo copy docker://k8s.gcr.io/pause:latest docker://<your_server>/k8s.gcr.io/pause:latest
	For every [literal]``skopeo`` command add [literal]``--dest-tls-verify=false`` if the registry is not secured.	如果注册表不安全，请在每条 [literal]``skopeo`` 命令中添加 [literal]``--dest-tls-verify=false``。
	If the registry is unsecured, for example not configured with SSL, add the registry domain to the section [literal]``registries.insecure`` on the containerized proxy virtual machine by editing:	如果注册表不安全（例如未配置 SSL），请编辑容器化代理虚拟机上的如下文件，在 [literal]``registries.insecure`` 部分添加注册表域：
	/etc/containers/registries.conf	/etc/containers/registries.conf
	Before starting the pod, point the Podman where to get the [literal]``pause`` image from on the internal registry:	启动 pod 前，将 Podman 指向获取内部注册表中的 [literal]``pause`` 映像的位置：
	echo -e '[engine]\ninfra_image = "<your_server>/pause:latest"'>>/etc/containers/containers.conf	echo -e '[engine]\ninfra_image = "<your_server>/pause:latest"'>>/etc/containers/containers.conf
	To start using the images from the internal registry please adapt the [literal]``NAMESPACE`` value in file `/etc/sysconfig/uyuni-proxy-systemd-services.config`.	要开始使用内部注册表中的映像，请修改 `/etc/sysconfig/uyuni-proxy-systemd-services.config` 文件中的 [literal]``NAMESPACE`` 值。
	For the k3s deployment, add [literal]``--set repository=<your_server>`` to the helm install command line.	要进行 k3s 部署，请在 helm 安装命令行中添加 [literal]``--set repository=<your_server>``。
	Air-gapped solution for Podman	Podman 的物理隔离解决方案
	This example illustrates deployment of containerized image on a machine with no access to internet.	下面的示例说明在无法连接互联网的计算机上部署容器化映像的过程。
	Procedure: Deploying air-gapped proxy	过程：部署物理隔离的代理
	This command does not work on SLE 15 SP3 and earlier container hosts.	此命令在 SLE 15 SP3 和更低版本的容器主机上不适用。
	On a machine with internet access run:	在连接到互联网的计算机上，运行以下命令：

Loading…

graceyu

Translation approved

English

Chinese (China) (zh_CN) 0 characters edited Current translation

4 months ago

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Chinese (China) (zh_CN)
No related strings found in the glossary.

String information

Source string description

type: delimited block -

Flags

no-wrap

Source string location

modules/installation-and-upgrade/pages/containerized-proxy-deployment.adoc:7

String age

4 months ago

Last updated

2 weeks ago

Source string age

4 months ago

Translation file

l10n-weblate/installation-and-upgrade/zh_CN.po, string 158