entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://cloud.google.com/dns/docs/apis|1|https://cloud.google.com/dns/docs/reference/v1beta2/resourceRecordSets|2|https://cloud.google.com/dns/docs/reference/json-record|blocks|key|5k2j5|text|GCP没有实现这样的资源，但是可以使用可用的Cloud+DNS+1之一自动执行此操作，例如，使用ResourceRecordSets+2将A记录配置到您想要分配给主机的ManagedZone，并在创建入口控制器之后编写此配置脚本。|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|a206|例如，检索分配给发出类似kubectl+describe+ing+<ingress-name>+%7Cgrep+“Address:”+%7Cawk+‘{print+$2}’的命令的入口控制器的IP地址，而不是使用IP信息来构造API体请求3。|style|CODE|9au2^0|W|1|0|1V|1|1|0|C|1Y|37|1|2|0^^$0|$1|$2|3|4|5|6|$7|8]]|9|$2|3|4|5|6|$7|A]]|B|$2|3|4|5|6|$7|C]]]|D|@$E|F|G|H|2|I|J|T|K|@]|L|@$M|U|N|V|E|W]|$M|X|N|Y|E|Z]]|6|$]]|$E|O|G|P|2|I|J|10|K|@$M|11|N|12|Q|R]]|L|@$M|13|N|14|E|15]]|6|$]]|$E|S|G|-4|2|I|J|16|K|@]|L|@]|6|$]]]]

GCP has not implemented resources like that, however this operation could be automated using one of the available Cloud DNS APIs <a href="https://cloud.google.com/dns/docs/apis" rel="nofollow noreferrer">1</a>, as for example the ResourceRecordSets <a href="https://cloud.google.com/dns/docs/reference/v1beta2/resourceRecordSets" rel="nofollow noreferrer">2</a> to configure A records to the ManagedZone you want to assign the host, scripting this configuration after the Ingress controller creation.
Example, retrieving the IP address allocated to the ingress controller issuing the command like <code>kubectl describe ing &lt;ingress-name&gt; |grep “Address:” |awk ‘{print $2}’</code> than using the IP information to construct the API body request <a href="https://cloud.google.com/dns/docs/reference/json-record" rel="nofollow noreferrer">3</a>.

entityMap|blocks|key|88vsq|text|在gke中没有通用的域名选项，所以我必须购买一个域名并根据创建的托管dns区域NS更新NS，当我通过external-dns更新gke中的入口时，它们将自动同步|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|7ucta|我可以说我用这些步骤解决了这个问题，|c2roq|1-创建一个域名属于own的托管区域，并确保它具有从您创建的dns区域访问域的权限。Mean正在为您的dns区域所在的google项目提供访问权限|7dp3|注意:创建群集时，请确保为托管dns区域提供读写权限的作用域|4kcrv|gcloud+container+clusters+create+“external-dns”+\
++++—num-nodes+1+\
++++—scopes+“https://www.googleapis.com/auth/ndev.clouddns.readwrite|code-block|syntax|javascript|7l8ai|创建将包含托管DNS记录的DNS区域。|5816q|$+gcloud+dns+managed-zones+create+“xxx.test-dev”+\
++++—dns-name+“xxx.test.dev.”+\
++++—description+“Automatically+managed+zone+by+kubernetes.io/external-dns+test.dev+domain+name”|fjdnr|2-请将资源部署到名为external-dns的网关引擎上|m5e3|https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke.md#deploy-externaldns|5kfi5|并使用以下命令检查日志|bg2ph|kubectl+logs+$(kubectl+get+pods+--template+'{{range+.items}}{{.metadata.name}}{{"\n"}}{{end}}'+%7C+grep+dns)|r9el|或|3pv1t|kubectl+logs+$(kubectl+get+pods+--no-headers+-o+custom-columns=":metadata.name"+%7C+grep+dns)|ctd9v|如果你看到的东西是一切都很顺利|90cre|time="2021-01-20T11:37:46Z"+level=info+msg="Add+records:+xxx.test.dev.+A+[34.89.xx.xx]+300"
time="2021-01-20T11:37:46Z"+level=info+msg="Add+records:+xxx.test.dev.+TXT+[\"heritage=external-dns,external-dns/owner=my-identifier,external-dns/resource=ingress/default/ingress-test\"]+300"
time="2021-01-20T11:38:47Z"+level=info+msg="All+records+are+already+up+to+date"|4h3ou|备注在A记录旁边创建了TXT记录。TXT记录表示对应的A记录由ExternalDNS管理。这使得ExternalDNS可以安全地在存在通过其他方式管理的其他记录的环境中运行。让我们检查一下是否可以解析此DNS名称。我们将首先询问分配给您的区域的名称服务器。|5cf93|$+dig+%2Bshort+@ns-cloud-e1.googledomains.com.+xxx.test.dev.
104.155.xx.xx|cgj7f|并且您可以检查域名的ip是否正确或有问题|2v53|host+https://xxx.test.dev/++++++++
Host+https://xxx.test.dev/+not+found:+3(NXDOMAIN)|ba99u|它可以被投诉床域一段时间，但然后你会得到正确的回应|bd6ki|host+xxx.test.dev
xxx.test.dev+has+address+35.197.xx.xx|ckhfv^0|1E|C|0|0|0|0|0|0|0|B|C|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|1O|9|@$A|1P|B|1Q|C|D]]|E|@]|F|$]]|$2|G|4|H|6|7|8|1R|9|@]|E|@]|F|$]]|$2|I|4|J|6|7|8|1S|9|@]|E|@]|F|$]]|$2|K|4|L|6|7|8|1T|9|@]|E|@]|F|$]]|$2|M|4|N|6|O|8|1U|9|@]|E|@]|F|$P|Q]]|$2|R|4|S|6|7|8|1V|9|@]|E|@]|F|$]]|$2|T|4|U|6|O|8|1W|9|@]|E|@]|F|$P|Q]]|$2|V|4|W|6|7|8|1X|9|@$A|1Y|B|1Z|C|D]]|E|@]|F|$]]|$2|X|4|Y|6|O|8|20|9|@]|E|@]|F|$P|Q]]|$2|Z|4|10|6|7|8|21|9|@]|E|@]|F|$]]|$2|11|4|12|6|O|8|22|9|@]|E|@]|F|$P|Q]]|$2|13|4|14|6|7|8|23|9|@]|E|@]|F|$]]|$2|15|4|16|6|O|8|24|9|@]|E|@]|F|$P|Q]]|$2|17|4|18|6|7|8|25|9|@]|E|@]|F|$]]|$2|19|4|1A|6|O|8|26|9|@]|E|@]|F|$P|Q]]|$2|1B|4|1C|6|7|8|27|9|@]|E|@]|F|$]]|$2|1D|4|1E|6|O|8|28|9|@]|E|@]|F|$P|Q]]|$2|1F|4|1G|6|7|8|29|9|@]|E|@]|F|$]]|$2|1H|4|1I|6|O|8|2A|9|@]|E|@]|F|$P|Q]]|$2|1J|4|1K|6|7|8|2B|9|@]|E|@]|F|$]]|$2|1L|4|1M|6|O|8|2C|9|@]|E|@]|F|$P|Q]]|$2|1N|4|-4|6|7|8|2D|9|@]|E|@]|F|$]]]]

There is not generic domain options in gke so I have to purchase a domain and update NS according to created managed dns zone NS and they will be automated sync when I update ingress in gke by <code>external-dns</code>
I can say I solve this problem with this steps,
1- Create a managed zone which has domain name belongs own and be sure it has permission to access domain from dns zones which you create. Mean is giving access the google project which your dns zone exist
Note: when you create the cluster be sure giving scopes for readwrite perm for managed dns zone
<pre><code>gcloud container clusters create “external-dns” \
 —num-nodes 1 \
 —scopes “https://www.googleapis.com/auth/ndev.clouddns.readwrite
</code></pre>
Create a DNS zone which will contain the managed DNS records.
<pre><code>$ gcloud dns managed-zones create “xxx.test-dev” \
 —dns-name “xxx.test.dev.” \
 —description “Automatically managed zone by kubernetes.io/external-dns test.dev domain name”
</code></pre>
2- Please deploy the resources to gke which name is <code>external-dns</code>
<pre><code>https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gke.md#deploy-externaldns
</code></pre>
And check the logs with
<pre><code>kubectl logs $(kubectl get pods --template '{{range .items}}{{.metadata.name}}{{&quot;\n&quot;}}{{end}}' | grep dns)
</code></pre>
Or
<pre><code>kubectl logs $(kubectl get pods --no-headers -o custom-columns=&quot;:metadata.name&quot; | grep dns)
</code></pre>
And if you see something like everything is going smoothly
<pre><code>time=&quot;2021-01-20T11:37:46Z&quot; level=info msg=&quot;Add records: xxx.test.dev. A [34.89.xx.xx] 300&quot;
time=&quot;2021-01-20T11:37:46Z&quot; level=info msg=&quot;Add records: xxx.test.dev. TXT [\&quot;heritage=external-dns,external-dns/owner=my-identifier,external-dns/resource=ingress/default/ingress-test\&quot;] 300&quot;
time=&quot;2021-01-20T11:38:47Z&quot; level=info msg=&quot;All records are already up to date&quot;
</code></pre>
Note created TXT record alongside A record. TXT record signifies that the corresponding A record is managed by ExternalDNS. This makes ExternalDNS safe for running in environments where there are other records managed via other means.
Let’s check that we can resolve this DNS name. We’ll ask the nameservers assigned to your zone first.
<pre><code>$ dig +short @ns-cloud-e1.googledomains.com. xxx.test.dev.
104.155.xx.xx
</code></pre>
And you can check the ip of the domain is correct or has a problem
<pre><code>host https://xxx.test.dev/ 
Host https://xxx.test.dev/ not found: 3(NXDOMAIN)
</code></pre>
It can be complained bed domain for a while but then you will get the correct response
<pre><code>host xxx.test.dev
xxx.test.dev has address 35.197.xx.xx
</code></pre>

I need to use a domain for GKE cluster to access ingress into the cluster and applications, similar like azure AKS http add-on which gives a generic-created domain(not a custom domain)
<a href="https://docs.microsoft.com/en-us/azure/aks/http-application-routing" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/azure/aks/http-application-routing</a>
Is there any solution on Google cloud as well?
Our GKE creating/deleting process is a part of IaC tooling and we are automating cluster and our app deployment for dev/test/staging. And the generic domain creation and binding managed dns zone to the cluster resources gives us great flexibility. Otherwise we have to create custom domain and managed dns zone which will be static and bring unnecessary complexity to the provisioning tooling.

gke and auto created domain for enabling http routing

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

 我需要使用GKE集群的域名来访问集群和应用程序的入口，类似于azure AKS http add-on，它提供了一个通用创建的域名(不是自定义域) https://docs.microsoft.com/en-us/azure/aks/http-application-routing在Google cloud上也有什么...

问gke和自动创建的启用http路由的域名
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问gke和自动创建的启用http路由的域名EN