Release Notes 2023
Release Notes 2022
Release Notes 2021
Release Notes 2020
Release Notes 2019
Other Mezmo Resources
Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
LogDNA Agent for Kubernetes and OpenShift, version 3.0
Copy Markdown
Open in ChatGPT
Open in Claude
Connect to Cursor
Connect to VS Code
Release Notes
December 15th, 2020
LogDNA is pleased to announce the general availability release of the LogDNA Agent for Kubernetes and OpenShift, version 3.0.
LogDNA Agent runs on Kubernetes (version 1.9 or later) or Red Hat OpenShift (version 4.5 or later). For more detailed information about the LogDNA Agent for Kubernetes and Openshift, refer to the documentation in our public GitHub repository.
New features and enhancements
Note: These Release Notes reflect the same content as the v2.2 Beta release, as no user-facing changes were made.
- LogDNA Agent for Kubernetes and Openshift is now configurable to run as a non-root user. For details refer to our documentation on Running as non-root.
- Configuration for Lookback options for how the Agent handles files upon starting.
- Enabling journald monitoring for Kubernetes or OpenShift.
- Logging Kubernetes events. See Configuring Kubernetes Events
- Base image of the Agent hosted on DockerHub is updated to UBI 8
- Kubernetes Labels support; log file's metadata is now enriched with Kubernetes labels.
Changes
- Updated tagging scheme for the Agent image that is available on DockerHub.
Known limitations
- With
lookback=startthe Agent will temporarily fully buffer files in memory before uploading; this may cause issues with log files that are larger than available memory. - When lookback is enabled pre-existing lines will be updated only after a change is detected in the file. If a file is completely static the lines will not be uploaded.
- Agent lookback does not track which lines have been uploaded, therefore log duplication may result if the agent is restarted with lookback enabled.
- The agent may generate many log entries when a file matching an ignore pattern is recreated or updated frequently. A workaround would be to configure the RUST_LOG environment variable to raise the log level to
warn, errorthreshold.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Last updated on
Was this page helpful?
Next to read:
Dec 3rd, 2020 - LogDNA Web Version 4.29.11Discard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message