diff options
| author |  TimYin <shiguangyin@inspur.com>
| 2021-01-27 00:21:38 +0800 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2021-01-26 17:21:38 +0100 |
| commit | 1bc84e61f9740d9d980a9e591ec99f00d276658c (patch) | |
| tree | 040a3a0d460422e3221ff8caf13c4cf5951be3a1 | |
| parent | 6ff19342d3b6d354daebbbe131514f2d6514a905 (diff) | |
| download | coredns-1bc84e61f9740d9d980a9e591ec99f00d276658c.tar.gz coredns-1bc84e61f9740d9d980a9e591ec99f00d276658c.tar.zst coredns-1bc84e61f9740d9d980a9e591ec99f00d276658c.zip | |
modify the error url of hualala (#4426)
| -rw-r--r-- | ADOPTERS.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ADOPTERS.md b/ADOPTERS.md index 22abc9aef..652259ae7 100644 --- a/ADOPTERS.md +++ b/ADOPTERS.md @@ -25,6 +25,6 @@ * [AdGuard](https://adguard.com/) uses CoreDNS in [AdGuard Home](https://github.com/AdguardTeam/AdGuardHome) and, therefore, in production public AdGuard DNS servers. * [Skyscanner](https://www.skyscanner.net) uses CoreDNS within Kubernetes in production with the configuration tuned to use the Autopath plugin. * [Zinza Technology](https://zinza.com.vn) uses CoreDNS within Kubernetes in production, with standard configuration. -* [Hualala](https://www.hualala.com/home) uses CoreDNS in Kubernetes using default configuration, in its Lab. Expected to be in production soon. +* [Hualala](https://www.hualala.com) uses CoreDNS in Kubernetes using default configuration, in its Lab. Expected to be in production soon. * [Hellofresh](https://www.hellofresh.com/) uses CoreDNS in multiple Kubernetes clusters, with Forward plugin. * [Render](https://render.com) uses CoreDNS in production across all its Kubernetes clusters. |