| Item | Link |
|---|---|
| Tracking Issue | cloudfoundry/community#1481 |
| RFC | cloudfoundry/community#1438 |
| routing-release | cloudfoundry/routing-release#535 |
| cloud_controller_ng | cloudfoundry/cloud_controller_ng#4910 |
Context: PR cloudfoundry/java-buildpack-client-certificate-mapper#16 adds support for the Envoy XFCC key-value format including a XFCC_URI_ATTRIBUTE. The gorouter change emits Hash=<sha256>;Subject="<DN>" — no URI=. Question: does it make sense to add it?
Diego's createCertificateTemplate (executor/depot/containerstore/credmanager.go) generates the app identity certificate:
return &x509.Certificate{When investigating suspicious files on Cloud Foundry Diego cells (compute nodes), you may encounter files in the download cache directory (/var/vcap/data/rep/shared/garden/download_cache/) with cryptic filenames like:
14a739ab8e326514832ea14273ca4410-1781206925504478185-56
OlderNewer