kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
12,228 Commits 116 Branches 250 Tags 531 MiB
Commit Graph

43 Commits

Author SHA1 Message Date
Ciprian Hacman 61708eae6b Rename kops to kOps in the docs 2020-10-29 19:40:53 +02:00
John Gardiner Myers 402bcbbea2 Update shared-VPC documentation 2020-08-11 22:49:13 -07:00
Peter Rifel 1873b45e8b
remove creationTimestamp fields from manifest examples 2020-07-19 16:32:33 -05:00
Peter Rifel 9f67420120
Cleanup syntax highlighting and misc markdown cleanup 2020-06-08 22:12:32 -05:00
GuyTempleton 4b41eb2435
Docs: More List fixes 2019-12-11 09:30:33 +00:00
Moustafa Baiou cd95ebc11c
add documentation for external egress management 2019-01-27 15:53:22 -05:00
Sean Johnson 737a7a2cb8 5700: Add command line flag for disabling Subnet ELB tags 2018-10-10 12:48:06 +11:00
Byungjin Park 4f1f2b07af
Fix mis-typings in docs 2018-10-05 17:13:41 +09:00
Aurel Canciu 8fbdddbc4a
Update docs regarding shared NAT Instances setup 2018-05-12 23:17:45 +03:00
Thomas Peitz d9ec15ec3b
Add SubnetType tags to run_in_existing_vpc docs 2018-05-02 21:20:26 +02:00
Anton Antonov 3c88a7fc27 Clarify few things in Running an existing VPC 2018-02-26 18:11:57 +02:00
Thomas Peitz 16d9ded25f Improve formatting of run_in_existing_vpc.md 2017-12-21 20:53:25 +01:00
Thomas Peitz cd8d5f7bec Improve explanation of KubernetesCluster tag 2017-12-20 22:51:06 +01:00
Thomas Peitz 1eb1fdf163 Improve formatting of run_in_existing_vpc.md 2017-12-20 22:48:29 +01:00
Thomas Peitz 91fc6a83ba Move tagging infos of vpc into proper section 2017-12-20 22:46:35 +01:00
Thomas Peitz bf7e072f16 Improve formatting of shared resource tag docs 2017-12-20 22:41:31 +01:00
Thomas Peitz 56e82faedb Update shared resource tag infos regarding kops 1.8 2017-12-20 22:36:13 +01:00
Kubernetes Submit Queue e88496a248
Merge pull request #4061 from meringu/create-subnets 
Automatic merge from submit-queue.

Add --subnets and --utility-subnets to kops create cluster

This change adds two new options to `kops create cluster`

When specifying `--vpc`, `--subnets` can be specified as an unordered array of subnet ids. Kops will then look up the zones of the subnets to find which zone to add the subnet id to.

If `--topology private` is also specified, `--utility-subnets` can similarly be specified.

~If a zone was specified but a subnet wasn't given that matches the zone, then the subnet will be allocated a CIDR with the current behaviour.~ This case fails validation here 7bd0a6a703/pkg/apis/kops/validation/validation.go (L151)

I can add unit tests and docs changes if required, but I am keen to get feedback before I proceed much further.

I have only added support for AWS.

I have tested this by running a command similar to this:

```bash
kops create cluster \
  --zones=us-east-1a,us-east-1b,us-east-1c \
  --topology private \
  --master-zones=us-east-1a,us-east-1b,us-east-1c  \
  --vpc $vpc_id \
  --subnets subnet-111111,subnet-222222,subnet-333333 \
  --utility-subnets subnet-444444,subnet-555555,subnet-666666 \
  $cluster_hosted_zone_name
```

And the cluster spec was as expected.
 2017-12-18 21:12:59 -08:00
Henry Muru Paenga 9f3382f072
Add docs for create cluster --subnets option 2017-12-18 12:33:06 +13:00
Kubernetes Submit Queue 7bd0a6a703
Merge pull request #3898 from rdrgmnzs/additional_cidr 
Automatic merge from submit-queue.

Add additionalNetworkCIDRs to support VPCs with multiple CIDRs in AWS

Add additionalNetworkCIDRs to support VPCs with multiple CIDRs in AWS.

@justinsb I cannot find anywhere that does a check on an existing VPC to see if the networkCIDR matches what is on the VPC defined, I was looking for that so I can add a similar check for this. Am I missing something or is there really no check like that?
 2017-12-13 18:25:41 -08:00
Rodrigo Menezes be85dfc438 Fix typo 2017-12-13 15:48:14 -08:00
Peter Rifel 2400091a0e Remove now-unnecessary note about spurious resource renaming 2017-12-06 16:36:42 -08:00
Rodrigo Menezes f908dcb3bf Check and docs 2017-11-26 20:37:16 -08:00
Derek VerLee ffa95b8112 Add support for cluster using http forward proxy 2017-08-07 14:30:42 -04:00
Justin Nauman c794e139de Update run_in_existing_vpc.md 
Fixing broken links for Topology and Networking
 2017-03-15 14:05:11 -05:00
yissachar b6a954476d Fix broken link 2017-03-15 00:57:26 -04:00
mshenhera 459e669d9e fixed link to topology.md file 2017-01-31 14:51:31 +02:00
Chris Love 58b92bc390 Merge pull request #1615 from geojaz/patch-1 
Update run_in_existing_vpc.md note for tagging shared subnets
 2017-01-28 21:56:30 -07:00
Eric Hole ff9936fe8b Update run_in_existing_vpc.md for shared subnets tags 2017-01-24 22:02:18 -05:00
Justin Santa Barbara 5f956433b9 Document existing-subnet requirements 2017-01-24 10:42:23 -05:00
Justin Santa Barbara 30ae86bb86 Automatically infer VPC & Subnet CIDRs 
Issue #1492
 2017-01-20 02:04:36 -05:00
Eric Hole 1e3d94392c Major redo/squash of the work to get egress added to the API and hooked up. 
One commit from the always incredible @kris-nova was incorporated here, it was to
check for tags in `kutil/delete_cluster.go`. She was a major driver and instrumental in getting
this to where we aere now!
 2017-01-19 16:57:42 -05:00
Eric Hole 3de7bfb93f First pass at Shared NGW docs. 2017-01-08 09:35:56 -05:00
Chris Love 2aa3a6ce03 Merge pull request #766 from vendrov/patch-2 
elaborate "external networking"
 2016-12-24 13:20:15 -07:00
vendrov 43a9170ca9 Changed 2016-12-24 18:06:22 +02:00
yissachar 99305a57e4 Fix link 2016-12-01 00:59:12 -05:00
yissachar 19d183112d Add documentation about incorrect VPC diffing 2016-12-01 00:31:39 -05:00
keglevich3 200d7e20e6 elaborate "external networking" 
Giving example for external netowrking
 2016-10-31 23:20:48 +02:00
keglevich3 574dd9904f typo 
typo
 2016-10-31 22:46:38 +02:00
Yissachar Radcliffe 5217bd432d Add support for shared subnets 2016-09-16 12:17:44 -04:00
Justin Santa Barbara 360c82b0f6 Remove lingering reference to --dryrun mode 
Issue #16
 2016-08-03 01:29:47 -04:00
Justin Santa Barbara 2fa3bcc952 UX: Split create command into `create` and `update` 
We separate out the `create cluster` operation from the `update cluster`
operation.  Now create cluster only creates the spec (unless you pass
--yes), and is only for new clusters.

`update cluster` works on new or existing clusters, and should be called
to apply changes.

`update` is not the best name, because it means something different in
kubectl, but I think it's a good start.
 2016-07-21 11:54:09 -04:00
Justin Santa Barbara 3886c03efe Cleanup: move docs to top-level, add .gitignore 
Rearranging for the new repo
 2016-06-30 10:31:18 -04:00