OSDOCS-16614: Documented VIP optional with user-managed LB feature #104065
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
dfitzmau marked this conversation as resolved.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,56 @@ | ||||||
| // Module included in the following assemblies: | ||||||
| // | ||||||
| // * installing/installing_bare_metal/upi/installing-bare-metal-network-customizations.adoc | ||||||
| // * installing/installing_bare_metal/upi/installing-bare-metal.adoc | ||||||
| // * installing/installing_bare_metal/upi/installing-restricted-networks-bare-metal.adoc | ||||||
|
|
||||||
| :_mod-docs-content-type: CONCEPT | ||||||
|
Contributor
There was a problem hiding this comment. This needs to be changed to PROCEDURE |
||||||
| [id="installation-bare-metal-dns-record-type_{context}"] | ||||||
| = Configuring the dnsRecordsType parameter | ||||||
|
|
||||||
| [role="_abstract"] | ||||||
| During cluster installation, you can specify the `dnsRecordsType` parameter in the `install-config.yaml` file to set if the internal DNS service or an external source provides the necessary records for `api`, `api-int`, and `ingress` DNS records. | ||||||
|
|
||||||
| :FeatureName: Configuring the dnsRecordsType parameter | ||||||
| include::snippets/technology-preview.adoc[] | ||||||
|
|
||||||
| The `dnsRecordsType` parameter supports the following values: | ||||||
|
|
||||||
| * `Internal`: The default value. Setting this value causes the cluster infrastructure to automatically create and maintain the necessary DNS records. | ||||||
| * `External`: You can use this value only if you set the `loadBalancer.type` parameter to `UserManaged`. The cluster does not manage the DNS records. You must manually configure DNS records on an external DNS server. | ||||||
|
|
||||||
| .Prerequisites | ||||||
|
dfitzmau marked this conversation as resolved.
|
||||||
|
|
||||||
| * You created DNS records, such as `api`, `api-int`, or `\*.apps`. | ||||||
|
There was a problem hiding this comment.
Contributor
Author
There was a problem hiding this comment. I'll remove. I sometimes need to add the escape character () to prevent build errors.
Contributor
There was a problem hiding this comment. I'm also curious about this line. Do you want the backslash to be visible? |
||||||
| * You configured a user-managed load balancer for your cluster. | ||||||
| * If you intend on setting `dnsRecordsType.External` in the `infrastructure.config.openshift.io` CR , you must initially configure cluster nodes to use the specific external server for DNS resolution. | ||||||
|
|
||||||
| .Procedure | ||||||
|
dfitzmau marked this conversation as resolved.
|
||||||
|
|
||||||
| * During cluster installation, specify `TechPreviewNoUpgrade` for the `featureSet` parameter and specify `External` for the `dnsRecordsType` parameter in the `install-config.yaml` file: | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
Just a suggestion. It's a good practice to tell the user where they need to do something before you tell them what they need to do. |
||||||
| + | ||||||
| [source,yaml] | ||||||
| ---- | ||||||
| apiVersion: v1 | ||||||
| baseDomain: example.com | ||||||
| metadata: | ||||||
| name: dev-cluster | ||||||
| # ... | ||||||
| platform: | ||||||
| baremetal: | ||||||
| # ... | ||||||
| loadBalancer: | ||||||
| type: UserManaged | ||||||
| dnsRecordsType: External | ||||||
| # ... | ||||||
| featureSet: TechPreviewNoUpgrade | ||||||
| pullSecret: '{"auths":{"<local_registry>": {"auth": "<credentials>","email": "you@example.com"}}}' | ||||||
| sshKey: 'ssh-ed25519 AAAA...' | ||||||
| # ... | ||||||
| ---- | ||||||
| + | ||||||
| where: | ||||||
| + | ||||||
| `type.UserManaged`:: Specifies an external load balancer for your cluster. | ||||||
| `dnsRecordsType.External`:: Specifies that the cluster does not create internal DNS records for the core infrastructure. | ||||||
| `featureSet.TechPreviewNoUpgrade`:: Specifies the enablement of non-default features for your cluster. | ||||||
|
dfitzmau marked this conversation as resolved.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -139,6 +139,11 @@ The following example shows a default situation that stores DNS values globally: | |||||
|
|
||||||
| * Configure a static DNS without a network interface. Note that when updating the `/etc/resolv.conf` file on a host node, you do not need to specify an interface, IPv4 or IPv6, in the `NodeNetworkConfigurationPolicy` (NNCP) manifest. | ||||||
| + | ||||||
| [IMPORTANT] | ||||||
| ==== | ||||||
| During pod creation, Kubernetes uses the `/etc/resolv.conf` file that exists on a node. If you modify the `/etc/resolv.conf` file on a host node, the changes do not propagate to the `/etc/resolv.conf` file that exists in a container. You must recreate the container for changes to take effect. | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
| ==== | ||||||
| + | ||||||
| Example of a DNS configuration for a network interface that globally stores DNS values: | ||||||
| + | ||||||
| [source,yaml] | ||||||
|
|
||||||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.