Skip to content

Commit 7404073

Browse files
dramasamyminiroy
andauthored
Update articles/operator-nexus/quickstarts-tenant-workload-prerequisites.md
Co-authored-by: miniroy <[email protected]>
1 parent 5dd9f13 commit 7404073

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/operator-nexus/quickstarts-tenant-workload-prerequisites.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,7 @@ To create an Operator Nexus virtual machine (VM) or Operator Nexus Kubernetes cl
189189

190190
While the cloud services network automatically enables access to essential platform endpoints, you need to add others, such as docker.io, if your application requires them. Configuring the cloud services network proxy is a crucial step in ensuring a successful connection to your desired endpoints. To achieve this, you can add the egress endpoints to the cloud services network during the initial creation or as an update, using the `--additional-egress-endpoints` parameter. While wildcards for the URL endpoints might seem convenient, it isn't recommended for security reasons. For example, if you want to configure the proxy to allow image pull from any repository hosted off docker.io, you can specify `.docker.io` as an endpoint.
191191

192-
The egress endpoints must comply with the domain name structures and hostname specifications outlined in RFC 1034, RFC 1035, and RFC 1123. Valid domain names include alphanumeric characters, hyphens (not at the start or end), can start with a dot for wildcard subdomains, and can have subdomains separated by dots. Here are a few examples to demonstrate compliant naming conventions for domain and hostnames.
192+
The egress endpoints must comply with the domain name structures and hostname specifications outlined in RFC 1034, RFC 1035, and RFC 1123. Valid domain names include alphanumeric characters, hyphens (not at the start or end), and can have subdomains separated by dots. The endpoints can be a single FQDN, or a subdomain (domain prefix with a "."). Here are a few examples to demonstrate compliant naming conventions for domain and hostnames.
193193

194194
- `contoso.com`: The base domain, serving as a second-level domain under the .com top-level domain.
195195
- `sales.contoso.com`: A subdomain of contoso.com, serving as a third-level domain under the .com top-level domain.

0 commit comments

Comments
 (0)