4989117cf2
remove AWS support
2017-03-25 14:20:31 -07:00
2d5f895aac
update to Kubernetes 1.6
2017-03-25 12:04:05 -07:00
81cc65cc27
update to Kubernetes 1.6
2017-03-25 11:53:08 -07:00
ebe2845c17
update to Kubernetes 1.6
2017-03-25 11:50:26 -07:00
c01f16bc3e
update to Kubernetes 1.6
2017-03-25 11:45:32 -07:00
f62e9c9777
update to Kubernetes 1.6
2017-03-25 11:41:26 -07:00
e9c25522a4
update to Kubernetes 1.6
2017-03-25 10:07:48 -07:00
53ee78b73e
update to Kubernetes 1.6
2017-03-25 09:58:47 -07:00
7e009610b2
update for 1.6
2017-03-25 09:44:23 -07:00
6827ce575e
make kube-dns work again
2017-03-24 08:31:17 -07:00
c72849f7e3
document the CSR approve flow
2017-03-24 04:24:53 -07:00
f7532568be
document the RBAC role binding process for TLS bootstrapping
2017-03-24 04:16:29 -07:00
94cbe1e683
add docs on using custom kubeconfigs
2017-03-24 04:08:34 -07:00
99d342cc3c
add authentication lab
2017-03-23 23:08:54 -07:00
5a5314f3c9
clean up pod cidr firewall-rule
2017-03-23 19:51:39 -07:00
3b1700d85e
update to Kubernetes 1.6
2017-03-23 19:48:14 -07:00
b7ae204c86
Make the AWS region configurable
2017-03-23 08:49:54 -07:00
68dc4507c2
adding filter to aws describe-instances command to filter by the vpc-id
2017-03-23 08:48:52 -07:00
4ad918e7c6
FIX #72 for LoadBalancer creation on AWS
...
kube-controller-manager and kube-apiserver service unit files are missing
one option --cloud-provider=aws parameter, which is creating problem while
creating ELB on AWS when type: LoadBalancer is provided in service YAML file.
This commit fixes that, issue
2017-03-23 08:48:23 -07:00
e465ee81f1
Node details to run client commands from
...
docs/06.kubectl.md does not instruct from which node those commands must be run.
The previous modules does explain that. For a newbie its helpful to tell them
from which node they must run commands of doc/06-kubectl.md.
This PR has a minor update about that information.
2017-03-23 08:48:23 -07:00
09a5f05eb6
add kubernetes.default to kubernetes-csr.json hosts
2017-03-23 08:44:35 -07:00
d3cd897b08
Add firewall rule to allow pods access to PodCIDR
...
This fixes issue #88 to allow pods access to PodCIDR such as the case of
DNS. When pods come up with an IP address in the cluster CIDR range,
they cannot access kubedns without a firewall rule to enable it. This
would also prevent pods from accessing each other depending on the
application.
2017-03-23 08:44:02 -07:00
a759be0db3
More nuance in etcd isolation recommendation
...
Clarify that while running etcd on a separate set of machine is a good idea, it isn't tested.
2017-03-23 08:43:29 -07:00
f6e72b50db
Updating instance images for Google Cloud Engine
...
Updating to newer images
2017-03-23 08:42:19 -07:00
d53aca31a5
upgrade to Kubernetes v1.5.1 and ETCD v3.0.15
2017-02-25 09:20:51 -08:00
4d7b87927f
TLC => TLS
2017-02-25 09:16:00 -08:00
753e71bac8
Note that all replicas of a component must share the same certificate.
2016-11-18 18:16:00 -08:00
26ff21f9d0
Replaced deprecated flag --health-check with the new equivalent --http-health-check=kube-apiserver-check
2016-11-18 18:15:33 -08:00
e7feed75a3
Update 01-infrastructure-gcp.md
2016-10-03 09:32:17 -04:00
bda65211ee
Update 07-network.md
2016-10-01 08:25:24 -07:00
5d8a0441ac
Add config/zone cmds to the doc
2016-10-01 08:25:11 -07:00
0b5282165a
remove duplication
2016-10-01 08:24:41 -07:00
599f45e2b1
open traffic between same security group
2016-09-27 06:58:21 -07:00
f2370f3578
etcd blocks when using type notify
2016-09-27 05:55:26 -07:00
b748f9d445
install etcd on the controller nodes
2016-09-27 05:50:33 -07:00
6a39adea4e
clean up docs
2016-09-27 05:40:56 -07:00
b3ce3ca14f
streamline deletion of GCE resources
2016-09-27 05:38:09 -07:00
4f3f389468
streamline deletion of GCE resources
2016-09-27 05:37:22 -07:00
f1981dad05
install etcd on the controller nodes
2016-09-27 05:31:57 -07:00
be84590c87
update to Kubernetes 1.4
2016-09-27 05:25:38 -07:00
7fe980da3e
Merge pull request #60 from mydharma/patch-1
...
jq -j is not a valid option. I think the author meant jq -r
2016-09-15 20:25:32 -07:00
720cdab53c
Fix typo
2016-09-14 22:41:42 -07:00
8ec636271d
jq -j is not a valid option. I think the author meant jq -r
2016-09-14 19:37:20 -07:00
b239d709f7
clean up docs
2016-09-11 08:22:09 -07:00
87ae2e1578
update ssh login info
2016-09-11 08:20:43 -07:00
d922910910
document assumptions
2016-09-11 07:59:53 -07:00
bd07c5e29d
warn users about GCP free trial limitations
2016-09-11 07:42:23 -07:00
4f86a72faa
add details regarding the auth token
2016-09-11 07:33:12 -07:00
b614d3b222
add details regarding the auth token
2016-09-11 07:31:04 -07:00
ce7eef3210
explain how pods get their subnets
2016-09-11 07:18:44 -07:00
Kelsey Hightower