Skip to content
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.

Commit

Permalink
feat(docs): document deis tags under the "Applications" section
Browse files Browse the repository at this point in the history
  • Loading branch information
Matthew Fisher committed Nov 11, 2016
1 parent 88b7353 commit bdf2472
Show file tree
Hide file tree
Showing 2 changed files with 30 additions and 3 deletions.
28 changes: 25 additions & 3 deletions src/applications/managing-app-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@

A Deis application [stores config in environment variables][].


## Setting Environment Variables

Use `deis config` to modify environment variables for a deployed application.
Expand Down Expand Up @@ -205,9 +206,30 @@ TCP Socket Probe: N/A
Configured health checks also modify the default application deploy behavior. When starting a new
Pod, Workflow will wait for the health check to pass before moving onto the next Pod.

[Slugbuilder]: ../understanding-workflow/components.md#builder-builder-slugbuilder-and-dockerbuilder

## Isolate the Application

Workflow supports isolating applications onto a set of nodes using `deis tags`.

!!! note
In order to use tags, you must first launch your cluster with the proper node labels. If you do
not, tag commands will fail. Learn more by reading ["Assigning Pods to Nodes"][pods-to-nodes].

Once your nodes are configured with appropriate label selectors, use `deis tags:set` to restrict
the application to those nodes:

```
$ deis tags:set environ=prod
Applying tags... done, v4
environ prod
```


[attached resources]: http://12factor.net/backing-services
[stores config in environment variables]: http://12factor.net/config
[kubernetes-probes]: http://kubernetes.io/docs/user-guide/pod-states/#container-probes
[pods-to-nodes]: http://kubernetes.io/docs/user-guide/node-selection/
[release]: ../reference-guide/terms.md#release
[router]: ../understanding-workflow/components.md#router
[kubernetes-probes]: http://kubernetes.io/docs/user-guide/pod-states/#container-probes
[Slugbuilder]: ../understanding-workflow/components.md#builder-builder-slugbuilder-and-dockerbuilder
[stores config in environment variables]: http://12factor.net/config
5 changes: 5 additions & 0 deletions src/managing-workflow/security-considerations.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,8 @@ with `region=us-east-1`, you can configure an application to be deployed to us-w
by using `deis tags set region=us-west-1`. Workflow will pass this configuration
along to Kubernetes, which will schedule your application in different regions.

See [Isolate the Application][] for more information.

# Running Workflow on Public Clouds

If you are running on a public cloud without security group features, you will have to set up
Expand Down Expand Up @@ -65,3 +67,6 @@ Application level whitelisting can also be done using the Deis client. To add/re
$ deis whitelist -a drafty-zaniness
=== drafty-zaniness Whitelisted Addresses
10.0.1.0/24


[Isolate the Application]: ../applications/managing-app-configuration.md#isolate-the-application

0 comments on commit bdf2472

Please sign in to comment.