0.7.0

Changelog

• Increase progressDeadlineSeconds for log-cache deployment to account for slow UAA startup on some IaaSes #58
• Refactor config values to follow standard format #65
• Images now have OCI compliant labels instead of using deplab

0.6.0

Changelog

• Introduce Log Cache API deployment that can horizontally scaled independently from the Log Cache Deployment.
• Move images to the cloudfoundry Docker Hub repository

0.5.0

• Log Cache changes:
  • Doesn't crash while waiting for UAA to start. The cf-auth-proxy will start but not respond to requests or readiness probes until UAA is accessible.
  • Now uses a static memory limit set rather then using node memory
  • Now accepts larger messages (up to 65 KiB)
  • Now limited to 1,000 messages per app. The previous limit of 100,000 only made sense in cf-deployment environments where Log Cache contains metrics.
  • Responds 501 to PromQL queries as metrics are not stored in Log Cache in cf-for-k8s.
• Memory/CPU limits/reqs now set on all containers.

0.4.0

• Add aggregate drains/app_log_destinations, a list of syslog destinations that will receive logs for all apps on the platform.
• Improve fluentd performance, allowing higher log throughput.
• Add prometheus metrics, for observing the health of the logging stack.
• Pull in logging specific network policies from cf-for-k8s repo

0.3.1

Add osl information to 0.3.0 release.

0.3.0

• Remove TLS from Log Cache, rely on Envoy for mTLS
• Update source type to look like logs on CF on BOSH, include process type and source type
• Remove Envoy sidecar logs from application log output for clarity
• Improved Log Cache ingestion performance

0.2.1

Change Log

• Additional metadata in images

0.2.0

Changelog

• Build logs now included in cf-push
• remove uaa client from log-cache
• Add Forwarder API to enable components to egress logs on behalf of cf apps

0.1.0

Merge pull request #19 from cloudfoundry/ubuntu

switch fluent image to ubuntu