route_emitter job from diego/1.30.1
              Github source:
              99800b8 or
              master branch
            
Properties¶
bpm¶
  
  
    
enabled¶Experimental: use the BOSH Process Manager to manage the route-emitter process.
- Default
  false
diego¶
  
  
    
route_emitter¶
bbs¶
api_location¶Address to the BBS Server
- Default
  bbs.service.cf.internal:8889
ca_cert¶PEM-encoded CA certificate
client_cert¶PEM-encoded client certificate
client_key¶PEM-encoded client key
client_session_cache_size¶capacity of the tls client cache
max_idle_conns_per_host¶maximum number of idle http connections
require_ssl¶enable ssl for all communication with the bbs
- Default
  true
debug_addr¶address at which to serve debug info
- Default
  127.0.0.1:17009
dropsonde_port¶local metron agent’s port
- Default
  3457
healthcheck_address¶address at which to serve debug info
- Default
  127.0.0.1:17011
job_name¶The name of the Diego job referenced by this spec (DO NOT override)
- Default
  route_emitter
local_mode¶Enable cell-local mode for the route-emitter. In this mode, the route-emitter emits route registrations only for the instances associated to its cell, as determined by the BOSH-assigned VM identifier
spec.id.
- Default
  false
log_level¶Log level
- Default
  info
nats¶
machines¶IP of each NATS cluster member.
password¶Password for server authentication.
port¶The port for the NATS server to listen on.
- Default
  4222
user¶Username for server authentication.
sync_interval_in_seconds¶Interval to sync routes to the router in seconds.
- Default
  60
internal_routes¶
  
  
    
enabled¶Experimental: Enable the route-emitter to emit registrations for internal DNS-based service discovery.
- Default
  false
loggregator¶
  
  
    
ca_cert¶CA Cert used to communicate with local metron agent over gRPC
cert¶Cert used to communicate with local metron agent over gRPC
key¶Key used to communicate with local metron agent over gRPC
use_v2_api¶True to use local metron agent gRPC v2 api. False, to use UDP v1 api
- Default
  false
v2_api_port¶Local metron agent gRPC port
- Default
  3458
register_direct_instance_routes¶
  
    
      Use the container IP address and internal port instead of the host IP address and external port when registering route endpoints. Suitable only for deployments in which the gorouters and TCP routers can route directly to the container IP of instances.
- Default
 false
routing_api¶
  
  
    
auth_enabled¶Enable UAA authentication when communicating with the Routing API
- Default
  true
port¶Routing API port to be used by the tcp route-emitter
- Default
  3000
url¶Routing API uri to be used by the tcp route-emitter
- Default
  http://routing-api.service.cf.internal
tcp¶
  
  
    
enabled¶Enable the route-emitter in cell-local mode to emit TCP routes for instances to the Routing API.
- Default
  false
uaa¶
  
  
    
ca_cert¶UAA ca certificate
client_name¶UAA client id
- Default
  tcp_emitter
client_secret¶UAA client secret
hostname¶UAA hostname
- Default
  uaa.service.cf.internal
port¶The port on which UAA accepts TLS connections
- Default
  8443
skip_cert_verify¶Skip certificate verification when communicating with UAA
- Default
  false
Templates¶
            Templates are rendered and placed onto corresponding
            instances during the deployment process. This job's templates
            will be placed into /var/vcap/jobs/route_emitter/ directory
            (learn more).
          
bin/post-start(frompost-start.erb)bin/route_emitter_as_vcap(fromroute_emitter_as_vcap.erb)bin/route_emitter_ctl(fromroute_emitter_ctl.erb)config/bpm.yml(frombpm.yml.erb)config/certs/bbs/ca.crt(frombbs_ca.crt.erb)config/certs/bbs/client.crt(frombbs_client.crt.erb)config/certs/bbs/client.key(frombbs_client.key.erb)config/certs/loggregator/ca.crt(fromloggregator_ca.crt.erb)config/certs/loggregator/client.crt(fromloggregator_client.crt.erb)config/certs/loggregator/client.key(fromloggregator_client.key.erb)config/certs/uaa/ca.crt(fromuaa_ca.crt.erb)config/route_emitter.json(fromroute_emitter.json.erb)
Packages¶
            Packages are compiled and placed onto corresponding
            instances during the deployment process. Packages will be
            placed into /var/vcap/packages/ directory.