logcache referenced but not provided as alias about app-autoscaler-release

[chombium]

Hi @dennisjbell,

The log_cache which you are trying to reuse is not meant to be use for client . This certificate is used for gRCP mTLS communication between the Log Cache nodes and should not be used for external communication with Log Cache. On the other side, reusing certificates is a bad idea and you should create a separate certificate.

As you want to consume data from Log Cache, you will need to create certificate and key for your metrics collector which are signed with the log-cache ca. You can take a look at the cc_logcache_tls certificate as an example. For the common name and alternative names you should configure the domains used by the your metrics collector.

I hope this helps.

Best Regards,
Jovan

[dennisjbell]

Note that cloudfoundry/cf-deployment#1113 was raised because cf internally references the alias as log-cache.services.cf.internal, but does not provide a certificate that is valid for that domain. While ideally, the bosh-dns-alias should be for log-cache.services.cf.internal, that won't work until that issue is resolved.

[silvestre]

Hi @dennisjbell ,

sorry for late reply, but it seems you are using the old template https://github.com/cloudfoundry/app-autoscaler-release/blob/main/templates/app-autoscaler-deployment.yml which is missing https://github.com/cloudfoundry/app-autoscaler-release/blob/main/templates/app-autoscaler.yml#L121-L127

We don't test and maintain the old template, and we are going to remove it in one of the upcoming releases, so please either migrate to the new template app-autoscaler.yml or continue maintaining app-autoscaler-deployment.yml in your own repository.