You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/contributing/development-environment.md
+2-28Lines changed: 2 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,32 +135,7 @@ Although writing and executing tests are critical to ensuring code quality, most
135
135
136
136
### Running a Kubernetes Cluster for Development
137
137
138
-
Before proceding further, it is imperative to understand that all Deis components, including the Deis PaaS ([deis/workflow][workflow]) run atop the [Kubernetes][k8s] container orchestration system. Whether for production or development and testing, a healthy Kubernetes cluster (version 1.1 or greater) is the required starting point.
139
-
140
-
All Deis components treat Kubernetes as the lowest common denominator and Deis components make no assumptions about:
141
-
142
-
* Your hosts' underlying operating system(s).
143
-
* The underlying physical or virtual infrastructure. It makes no difference whether your hosts:
144
-
* Are physical machines (i.e. bare metal).
145
-
* Are virtual machines provisioned through a cloud provider.
146
-
* Are virtual machines running locally on your laptop.
147
-
148
-
With Kubernetes used as a uniform interface between Deis components and the infrastructure below, it is also (largely) unimportant to Deis components _how_ your Kubernetes cluster was provisioned. As such, the Deis team is also not strongly opinionated (at this time) about how best to provision a Kubernetes cluster.
149
-
150
-
Any official options listed on Kubernetes own [Getting Started][k8s-getting-started] page should be sufficient.
151
-
152
-
#### DigitalOcean
153
-
154
-
In many cases, testing your changes to Deis components is accomplished most easily and economically on just a few Vagrant VMs - sometimes just one. However, at times, if one wishes to conserve local resources, test changes at scale, or demonstrate changes to others, it is advisable to move these activities into a cloud environment.
155
-
156
-
[DigitalOcean][] is Deis' officially recommended provider for contributors wishing to extend their development and testing into the cloud. See [Provision a new DO cluster](../installing-deis/digitalocean.md) for further details and then continue to follow the instructions below.
157
-
158
-
!!! important
159
-
Are you a new contributor to Deis? Your first [Pull Request][pr] could earn you credit at [DigitalOcean][]! Submit your changes and then email <deis@engineyard.com>. When your PR is merged, the maintainer team will send you a DigitalOcean credit based on the value of your contribution.
160
-
161
-
### Installing Deis Components
162
-
163
-
With a functioning Kubernetes cluster, proceed with Deis installation using [these instructions](../installing-deis/digitalocean.md) and then continue to follow the instructions below.
138
+
To run a Kubernetes cluster locally or elsewhere to support your development activities, refer to Deis installation instructions [here](../installing-deis/quickstart.md).
164
139
165
140
### Using a Development Registry
166
141
@@ -186,7 +161,7 @@ In non-Linux environments:
186
161
export DEIS_REGISTRY=<IP of the docker-deis Docker Machine VM>:5000/
187
162
```
188
163
189
-
If your development cluster runs on a cloud provider such as DigitalOcean, a local registry such as the one above will not be accessible to your Kubernetes nodes. In such cases, a public registry such as [DockerHub][dh] or [quay.io][quay] will suffice.
164
+
If your development cluster runs on a cloud provider such as Google Container Engine, a local registry such as the one above will not be accessible to your Kubernetes nodes. In such cases, a public registry such as [DockerHub][dh] or [quay.io][quay] will suffice.
190
165
191
166
To use DockerHub for this purpose, for instance:
192
167
@@ -275,7 +250,6 @@ things you should do when proposing a change to any Deis component.
Copy file name to clipboardExpand all lines: src/contributing/overview.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,6 @@ We are always looking for help improving the core platform, other workloads, too
16
16
17
17
When you're ready to begin writing code, review [Design Documents][dd] and get your [Development Environment][dev-environment] set up.
18
18
19
-
!!! important
20
-
If you're a new contributor to Deis, your Pull Request could earn you [credit at DigitalOcean][do-credit]!
21
-
22
19
## Triage Issues
23
20
24
21
If you don't have time to code, consider helping with triage. The community will thank you for saving them time by spending some of yours. See [Triaging Issues](triaging-issues.md) for more info.
@@ -30,6 +27,5 @@ Interact with the community on our user mailing list or live in our IRC channel,
Reference [this table](http://kubernetes.io/v1.1/docs/getting-started-guides/#table-of-solutions) in the official Kubernetes documentation for a more extensive (but still non-exhaustive) list of Kubernetes provisioning options supported by the project or the community.
18
+
17
19
## Prerequisites
18
20
Please make sure you enable the Daemon Sets api if you are installing a pre-1.2 version of kubernetes. As it is not turned on by default. You can learn more about how to do that [here](http://kubernetes.io/v1.1/docs/api.html#enabling-resources-in-the-extensions-group).
0 commit comments