loggregator_trafficcontroller job from cf/286
Github source:
78dc88f7
or
master branch
Properties¶
cc
¶
internal_service_hostname
¶Internal hostname used to resolve the address of the Cloud Controller
mutual_tls
¶
ca_cert
¶PEM-encoded CA certificate for secure, mutually authenticated TLS communication
tls_port
¶Port for internal TLS communication
- Default
9023
doppler
¶
grpc_port
¶Port for outgoing log messages via GRPC
- Default
8082
outgoing_port
¶Port for outgoing doppler messages
- Default
8081
loggregator
¶
doppler
¶
addrs
¶The addresses of Dopplers (alternative to doppler link)
- Default
[]
etcd
¶
ca_cert
¶PEM-encoded CA certificate
- Default
""
machines
¶IPs pointing to the ETCD cluster
maxconcurrentrequests
¶Number of concurrent requests to ETCD
- Default
10
require_ssl
¶Enable ssl for all communication with etcd
- Default
false
outgoing_dropsonde_port
¶Port for outgoing dropsonde messages
- Default
8081
tls
¶
ca_cert
¶CA root required for key/cert verification
cc_trafficcontroller
¶
cert
¶TLS certificate for communication between Cloud Controller and trafficcontroller
key
¶TLS key for communication between Cloud Controller and trafficcontroller
trafficcontroller
¶
cert
¶TLS certificate for trafficcontroller
key
¶TLS key for trafficcontroller
uaa
¶
client
¶Doppler’s client id to connect to UAA
- Default
doppler
client_secret
¶Doppler’s client secret to connect to UAA
uaa_client_id
¶DEPRECATED in favor of loggregator.uaa.client.
- Default
""
metric_emitter
¶
interval
¶The interval that metrics are emitted to the metron.
- Default
1m
metron_endpoint
¶
dropsonde_port
¶The port used to emit dropsonde messages to the Metron agent
- Default
3457
grpc_port
¶The port used to emit grpc messages to the Metron agent
- Default
3458
host
¶The host used to emit messages to the Metron agent
- Default
127.0.0.1
ssl
¶
skip_cert_verify
¶when connecting over https, ignore bad ssl certificates
- Default
false
system_domain
¶
Domain reserved for CF operator, base URL where the login, uaa, and other non-user apps listen
traffic_controller
¶
disable_access_control
¶Traffic controller bypasses authentication with the UAA and CC
- Default
false
etcd
¶
client_cert
¶PEM-encoded client certificate
- Default
""
client_key
¶PEM-encoded client key
- Default
""
health_addr
¶The host:port to expose health metrics for trafficcontroller
- Default
localhost:14825
locked_memory_limit
¶Size (KB) of shell’s locked memory limit. Set to ‘kernel’ to use the kernel’s default. Non-numeric values other than ‘kernel’, ‘soft’, ‘hard’, and ‘unlimited’ will result in an error.
- Default
unlimited
pprof_port
¶The pprof port for runtime profiling data
- Default
0
security_event_logging
¶
enabled
¶Enable logging of all requests made to the Traffic Controller in CEF format
- Default
false
uaa
¶
ca_cert
¶PEM encoded CA certificate for secure communication to UAA. Required if uaa.internal_url is provided.
- Default
""
internal_url
¶Internal URL of UAA
- Default
""- Example
https://uaa.service.cf.internal:8443
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/loggregator_trafficcontroller/
directory
(learn more).
bin/dns_health_check
(fromdns_health_check.erb
)bin/loggregator_trafficcontroller_ctl
(fromloggregator_trafficcontroller_ctl.erb
)config/certs/cc_trafficcontroller.crt
(fromcc_trafficcontroller.crt.erb
)config/certs/cc_trafficcontroller.key
(fromcc_trafficcontroller.key.erb
)config/certs/etcd-ca.crt
(frometcd-ca.crt.erb
)config/certs/etcd-client.crt
(frometcd-client.crt.erb
)config/certs/etcd-client.key
(frometcd-client.key.erb
)config/certs/loggregator_ca.crt
(fromloggregator_ca.crt.erb
)config/certs/mutual_tls_ca.crt
(frommutual_tls_ca.crt.erb
)config/certs/trafficcontroller.crt
(fromtrafficcontroller.crt.erb
)config/certs/trafficcontroller.key
(fromtrafficcontroller.key.erb
)config/certs/uaa_ca.crt
(fromuaa_ca.crt.erb
)config/loggregator_trafficcontroller.json
(fromloggregator_trafficcontroller.json.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.