We have deployed our application on Gardener K8 cluster. Exposed one port xxxx for external traffic through Service Type LoadBalancer. Currently cloud provider is assigning 'external ip' to service, which keeps changing with every build/deployment. To solve this problem, I created dnsEntry as abc.xyz.somedomain.com and added configuration to said service under annotations field. While trying to access this service through postman as http://abc.xyz.somedomain.com:xxxx//*apiname", I am getting timed out error which works otherwise with external ip of service. Do I need to do some other configuration here before using dns name instead of external ip? Help is really appreciated.
Asked
Active
Viewed 63 times
0
-
1Can you provide yaml files of deployment and service ? – Malgorzata Mar 10 '21 at 13:13
-
@Malgorzata thanks for quick reply. Meanwhile I realized that I was trying to assign dnsrecord which was already assigned to other resource. Now I am able to access the service using dns name. – Nanda K S Mar 10 '21 at 13:24
-
1Please paste file in proper format into post, also paste deployment yaml. If problem is already solved post solution as an answer to be more visible for community. – Malgorzata Mar 10 '21 at 13:40
1 Answers
1
Basically there are two ways to create dns record in cluster one with service and another with dnsentry resource type. I was trying to use both the options without realizing it, so it was complaining as dns record which I am trying to access second time is already assigned and busy. Now I have removed duplicate and its working fine.
Nanda K S
- 21
- 1