You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Security Note: Explicitly allowing intentions:write on the token you provide to a service instance at registration time opens up a significant additional vulnerability. Although you may trust the service team to define which inbound connections they accept, using a combined token for registration allows a compromised instance to to redefine the intentions which allows many additional attack vectors and may be hard to detect. We strongly recommend only delegating intentions:write using tokens that are used by operations teams or orchestrators rather than spread via application config, or only manage intentions with management tokens.
## todo# consul kv put consul/configuration/db_port 5432# consul kv get consul/configuration/db_port# dig @127.0.0.1 -p 8600 consul.service.consul# consul catalog services -tags# consul services register svc-db.hcl# curl 172.17.0.1:8500/v1/status/leader #get the leader# consul cmd cmd cmd --help has wonderful examples, thank me later# curl --request GET http://127.0.0.1:8500/v1/agent/checks
# this only works if the consul server is bootstrapped# doesnt work if your trying to bootstrap a greenfield server
healthcheck:
<<: *service-healthcheck test: consul catalog nodes | grep $CONSUL_NODE_PREFIX || exit $?
The text was updated successfully, but these errors were encountered:
The text was updated successfully, but these errors were encountered: