Skip to content

vlagent: use single volume for all vlagent data by default#1705

Merged
AndrewChubatiuk merged 1 commit intomasterfrom
vlagent-tmp-data-path
Jan 21, 2026
Merged

vlagent: use single volume for all vlagent data by default#1705
AndrewChubatiuk merged 1 commit intomasterfrom
vlagent-tmp-data-path

Conversation

@AndrewChubatiuk
Copy link
Copy Markdown
Contributor

@AndrewChubatiuk AndrewChubatiuk commented Dec 20, 2025

fixes #1696

  • added collector extraFilter, includePodLabels, includePodAnnotations, includeNodeLabels and includeNodeAnnotations support
  • use single volume for all vlagent data by default, before there was a separate path for checkpoints and remotewrite data by default
  • update strict security mode for vlagent, before it failed

This comment was marked as outdated.

This comment was marked as outdated.

This comment was marked as outdated.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 12 out of 12 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

// Path to directory where temporary data for remote write component is stored (default /vlagent_pq/vlagent-remotewrite-data)
// If defined, operator ignores spec.storage field and skips adding volume and volumeMount for pq
// Path to directory where temporary data for remote write component is stored.
// Defaults to /vlagent-data/vlagent-remotewrite-data or /var/lib/vlagent-data/vlagent-remotewrite-data in collector mode
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If undefined defaults to /var/lib/vlagent-data

Copy link
Copy Markdown
Contributor Author

@AndrewChubatiuk AndrewChubatiuk Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

value in PR is correct, this is spec.remoteWriteSettings.tmpData, which is a data path for remote write data

if ptr.Deref(cr.Spec.K8sCollector.IncludePodLabels, true) {
args = append(args, "-kubernetesCollector.includePodLabels")
}
if ptr.Deref(cr.Spec.K8sCollector.IncludePodAnnotations, false) {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if ptr.Deref(cr.Spec.K8sCollector.IncludePodAnnotations, false) {
if ptr.Deref(cr.Spec.K8sCollector.IncludePodAnnotations, true) {

We should not be setting this flag if its unset, right?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kept it's value the same as vlagent has

@vrutkovs vrutkovs self-assigned this Jan 15, 2026
@AndrewChubatiuk AndrewChubatiuk merged commit 8220f39 into master Jan 21, 2026
3 checks passed
@AndrewChubatiuk AndrewChubatiuk deleted the vlagent-tmp-data-path branch January 21, 2026 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

VLAgent: k8sCollector errors out if it cannot read logs

3 participants