service-discovery-controller job from cf-networking/2.4.0
Github source:
c5ab864c
or
master branch
Properties¶
address
¶
Address which service-discovery-controller will listen on.
- Default
0.0.0.0
dnshttps
¶
client
¶
ca
¶client-side mutual TLS configuration for dns over http
server
¶
tls
¶Server-side mutual TLS configuration for dns over http
log_level_address
¶
Address which log level endpoint listens on
- Default
127.0.0.1
log_level_port
¶
Port which log level endpoint listens on
- Default
8055
metron_port
¶
Forward metrics to this metron agent, listening on this port on localhost
- Default
3457
nats
¶
machines
¶IPs of each NATS cluster member
- Example
|+ - 192.168.50.123 - 192.168.52.123
password
¶Password for NATS authentication
- Example
natSpa55w0rd
port
¶TCP port of NATS servers
- Example
4222
user
¶User name for NATS authentication
- Example
nats
port
¶
Port which service-discovery-controller will listen on.
- Default
8054
route_emitter_interval_seconds
¶
Interval in seconds for which the route emitter is told to emit all routes. This value should be less than the staleness_threshold_seconds
- Default
60
staleness_threshold_seconds
¶
Staleness threshold in seconds for routes. If the service-discovery-controller does not receive a message about a route within this threshold, the route will be pruned from the table. This value is recommended to be three times the value of route_emitter_interval_seconds
- Default
180
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/service-discovery-controller/
directory
(learn more).
bin/post-start
(frompost-start.erb
)bin/service-discovery-controller_as_vcap
(fromservice-discovery-controller_as_vcap.erb
)bin/service-discovery-controller_ctl
(fromservice-discovery-controller_ctl.erb
)config/certs/client_ca.crt
(fromclient_ca.crt.erb
)config/certs/server.crt
(fromserver.crt.erb
)config/certs/server.key
(fromserver.key.erb
)config/config.json
(fromconfig.json.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.