anchor.diff:  	cf v3-push sidecar-dependent-app
   	```
   
  -Once you have pushed the app, you can further explore it in the sections below: [View the Processes Running in the Container](#view-processes) and [View the Web URL and App Logs](#view-logs). 
  +After you push the app, you can further explore it in the following sections: 
  +* [View the Processes Running in the Container](#view-processes) 
  +* [View the Web URL and App Logs](#view-logs)
   
   ### <a id="view-processes"></a> View the Processes Running in the Container
   
  
positive.code: 
  You can run additional processes in the same container as your app. These are called sidecar processes, or sidecars. An example of a sidecar is an Application Performance Monitoring (APM) tool. 
  
  When you provide a sidecar for your app, Cloud Foundry packages the required code and configuration needed to run the sidecar and app in the same droplet. It deploys this droplet in a single container on Diego and both processes within the container are health checked independently.
  
  For additional information about sidecars, see the _Sidecars_ section of the [CAPI v3 documentation](http://v3-apidocs.cloudfoundry.org/version/release-candidate/#sidecars). 
  
  
  ### <a id="use-case"></a> Use Cases
  
  You can use sidecars for processes that depend on each other or must run in the same container. 
  
  Some examples include processes that need do the following:
  
  * Communicate over a Unix socket or through localhost
  * Share the same filesystem
  * Be scaled and placed together
  * Have fast interprocess communication
  
  ### <a id="limitations"></a> Limitations
  
  Sidecars have the following limitations:
  
  * The start and stop order of app processes and their sidecars is undefined.
  * App processes and sidecars are codependent: if either crashes or exits, the other will as well.
  * Sidecars are currently not independently scalable and share resources with the main app process and other sidecars within the container. 
  * Sidecars only support PID-based health checks. HTTP health-checks for sidecars are not currently supported.
  
  ## <a id="create"></a> Push an App with a Sidecar
  
  This section provides general instructions for pushing an app with a sidecar. For an example that you can try yourself, see the [Sidecar Tutorial](#tutorial) section below. 
  
  ### <a id="prerequisite"></a> Prerequisites
  
  Before you can push an app with a sidecar, you have a must have the following:
  
  * An app that is currently running or ready to be pushed. 
  * A file that Cloud Foundry can execute inside the app container as a sidecar process. A few examples include an executable binary, a Java .jar file, or Ruby scripts
  
  ### <a id="create"></a> Procedure
  
  
negative.code: 	end
  	```
  
  * **A Golang sidecar**<br>The `config-server-sidecar` produces a `config-server` binary. It provides apps with their required configuration over its `/config` endpoint. It also accepts connections only over localhost on the `CONFIG_SERVER_PORT` port. This means the sidecar must be co-located in the same container as the app, so that it shares the same network namespace as the main app. 
  
  The diagram below illustrates the app architecture:
  
  