-
Feature Request
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
- Proposed title of this feature request:
Support for Search Domains - What is the nature and description of the request?
Support for Search Domains:
- Confirm all hostnames must be be fully qualified
- To add support for the 'search domain' by the Terraform provider.
- Configure additional search domains in ROSA HCP following this example:
https://nmstate.io/kubernetes-nmstate/examples.html
apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: name: dns spec: desiredState: dns-resolver: config: search: <--- - example.com <--- - example.org <--- server: - 8.8.8.8 - 2001:4860:4860::8888 interfaces: - name: eth1 type: ethernet state: up ipv4: auto-dns: false dhcp: true enabled: true ipv6: auto-dns: false dhcp: true enabled: true
- Red Hat update the ROSA product to accept a search domains parameter - no tech date
- Post provisioning job (Ansible) to update /etc/resolv.conf
- VPC updated with domains to be searched
- POD dnsSearch
- OCP ansible operator
- Instance Templates
- Why does the customer need this? (List the business requirements here)
Our customer has a lot of on-prem applications that depend on 3 internal search domains to resolve host names that are not fully qualified e.g. NFS vserver hostnames. When the cluster was provisioned, two internal search domains were not included. We deployed an existing application to the ROSA POC cluster which failed to mount NAS because of the missing search domains. - List any affected packages or components.
Networking
Terraform