mirror of https://github.com/kubernetes/kops.git
Replace kubernetes.com with example.com
We should be using example.com in our docs. Fix #2058
This commit is contained in:
parent
f489c15342
commit
e57e747c7f
|
@ -7,7 +7,7 @@ kops create cluster \
|
||||||
--node-count 3 \
|
--node-count 3 \
|
||||||
--zones us-west-2a,us-west-2b,us-west-2c \
|
--zones us-west-2a,us-west-2b,us-west-2c \
|
||||||
--master-zones us-west-2a,us-west-2b,us-west-2c \
|
--master-zones us-west-2a,us-west-2b,us-west-2c \
|
||||||
--dns-zone kubernetes.com \
|
--dns-zone example.com \
|
||||||
--node-size t2.medium \
|
--node-size t2.medium \
|
||||||
--master-size t2.medium \
|
--master-size t2.medium \
|
||||||
--node-security-groups sg-12345678 \
|
--node-security-groups sg-12345678 \
|
||||||
|
|
|
@ -103,7 +103,7 @@ of a domain you host in Route53. This requires creating a second hosted zone
|
||||||
in route53, and then setting up route delegation to the new zone.
|
in route53, and then setting up route delegation to the new zone.
|
||||||
|
|
||||||
In this example you own `example.com` and your records for Kubernetes would
|
In this example you own `example.com` and your records for Kubernetes would
|
||||||
look like `etcd-us-east-1c.internal.clustername.kubernetes.example.com`
|
look like `etcd-us-east-1c.internal.clustername.subdomain.example.com`
|
||||||
|
|
||||||
This is copying the NS servers of your **SUBDOMAIN** up to the **PARENT**
|
This is copying the NS servers of your **SUBDOMAIN** up to the **PARENT**
|
||||||
domain in Route53. To do this you should:
|
domain in Route53. To do this you should:
|
||||||
|
@ -119,7 +119,7 @@ ID=$(uuidgen) && aws route53 create-hosted-zone --name subdomain.example.com --c
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
# Note: This example assumes you have jq installed locally.
|
# Note: This example assumes you have jq installed locally.
|
||||||
aws route53 list-hosted-zones | jq '.HostedZones[] | select(.Name=="example.com.") | .Id'
|
aws route53 list-hosted-zones | jq '.HostedZones[] | select(.Name=="subdomain.example.com.") | .Id'
|
||||||
```
|
```
|
||||||
|
|
||||||
* Create a new JSON file with your values (`subdomain.json`)
|
* Create a new JSON file with your values (`subdomain.json`)
|
||||||
|
@ -164,7 +164,7 @@ aws route53 change-resource-record-sets \
|
||||||
--change-batch file://subdomain.json
|
--change-batch file://subdomain.json
|
||||||
```
|
```
|
||||||
|
|
||||||
Now traffic to `*.example.com` will be routed to the correct subdomain hosted zone in Route53.
|
Now traffic to `*.subdomain.example.com` will be routed to the correct subdomain hosted zone in Route53.
|
||||||
|
|
||||||
### Scenario 2: Setting up Route53 for a domain purchased with another registrar
|
### Scenario 2: Setting up Route53 for a domain purchased with another registrar
|
||||||
|
|
||||||
|
@ -184,7 +184,7 @@ for some of these instructions.
|
||||||
this you can also [get the values](ns.md))
|
this you can also [get the values](ns.md))
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
ID=$(uuidgen) && aws route53 create-hosted-zone --name subdomain.kubernetes.com --caller-reference $ID | jq .DelegationSet.NameServers
|
ID=$(uuidgen) && aws route53 create-hosted-zone --name subdomain.example.com --caller-reference $ID | jq .DelegationSet.NameServers
|
||||||
```
|
```
|
||||||
|
|
||||||
* You will now go to your registrars page and log in. You will need to create a
|
* You will now go to your registrars page and log in. You will need to create a
|
||||||
|
|
|
@ -54,7 +54,7 @@ By default the bastion instance group will create a public CNAME alias that will
|
||||||
The default bastion name is `bastion.$NAME` as in
|
The default bastion name is `bastion.$NAME` as in
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
bastion.example.kubernetes.com
|
bastion.mycluster.example.com
|
||||||
```
|
```
|
||||||
|
|
||||||
Unless a user is using `--dns-zone` which will inherently use the `basion-$ZONE` syntax.
|
Unless a user is using `--dns-zone` which will inherently use the `basion-$ZONE` syntax.
|
||||||
|
@ -65,7 +65,7 @@ You can define a custom bastion CNAME by editing the main cluster config `kops e
|
||||||
spec:
|
spec:
|
||||||
topology:
|
topology:
|
||||||
bastion:
|
bastion:
|
||||||
bastionPublicName: bastion.example.kubernetes.com
|
bastionPublicName: bastion.mycluster.example.com
|
||||||
```
|
```
|
||||||
|
|
||||||
### Using SSH agent to access your bastion
|
### Using SSH agent to access your bastion
|
||||||
|
|
|
@ -3,7 +3,7 @@
|
||||||
- Note your hosted zone ID
|
- Note your hosted zone ID
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
aws route53 list-hosted-zones | jq '.HostedZones[] | select(.Name=="subdomain.kubernetes.com.") | .Id'
|
aws route53 list-hosted-zones | jq '.HostedZones[] | select(.Name=="subdomain.example.com.") | .Id'
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue