Update netlify request guidelines to reference new netlify tld

Netlify has switched their hosted site domain from .com to .app.
Example:
  kubernetes-foo.netlify.com -> kubernetes-foo.netlify.app
This commit is contained in:
Bob Killen 2020-05-11 19:36:07 -04:00
parent 8e2f86565b
commit 1aed792f32
No known key found for this signature in database
GPG Key ID: 850FEB9A6356D2F6
1 changed files with 4 additions and 4 deletions

View File

@ -41,7 +41,7 @@ based framework. It's used for the Kubernetes website and several subprojects.
follow up with any questions in the issue.
- Once Netlify has been configured, you can preview the site using the Netlify
URL (example: `kubernetes-sigs-foo.netlify.com`). After this looks good to you,
URL (example: `kubernetes-sigs-foo.netlify.app`). After this looks good to you,
[request a subproject domain](#subproject-domain-request) and reference the
issue you created.
@ -105,7 +105,7 @@ k8s.io
# https://github.com/kubernetes-sigs/foo (@bar)
foo.sigs:
type: CNAME
value: kubernetes-sigs-foo.netlify.com
value: kubernetes-sigs-foo.netlify.app
```
### Reason for update:
The sig-foo subproject has requested a netlify site to host its documentation. ref #0000, #0000.
@ -141,8 +141,8 @@ Netlify admin to follow the procedure.
updated, HTTPS will be enabled automatically.
- Follow up with the requestor in the issue and let them know the site has been
deployed and give them the Netlify site url (site name + `netlify.com`).
Example `kubernetes-sigs-foo.netlify.com`. They may use this address for
deployed and give them the Netlify site url (site name + `netlify.app`).
Example `kubernetes-sigs-foo.netlify.app`. They may use this address for
testing and use before their DNS Request has been processed.
Once complete, the rest of the Netlify site configuration can be handled by the