Closed Infra-Red closed 5 years ago
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.
@Infra-Red Thats great you have fixed the problem, but when I look at the change:
it seems like instead of using elastichserch.host
you are using now CF_SYSTEM_DOMAIN
. This means the job cannot be used anymore when Kibana is not installed as a CF app. Is this required from now on, or there was another reason for the change?
Hey @vetin4ri! Is your Kibana instance accessible via CF route? Usually it’s should be available at logs.CF_SYSTEM_DOMAIN
.
Hi @Infra-Red, not really, we are using a setup where ELK is not associated with specific CF installation, but can handle logs deployments, including Kubernetes. It is not accessible via CF route nor installed on CF, but also in a separate network.
We were using upload-kibana-objects as it was loosely coupled with other jobs and could be easily used on its own.
Please first merge https://github.com/cloudfoundry-community/logsearch-boshrelease/pull/140
Fixes https://github.com/cloudfoundry-community/logsearch-for-cloudfoundry/issues/318