Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(vector): add minReadySeconds to StatefulSet and Deployment specs #367

Conversation

alexanderldavis
Copy link
Contributor

The chart currently supports minReadySeconds for DaemonSet-based deployments of the Vector agent. This PR extends this value to also apply to StatefulSets and Deployment specs.

Copy link
Member

@jszwedko jszwedko left a comment

Choose a reason for hiding this comment

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

Thanks @alexanderldavis . This change makes sense to me!

@jszwedko
Copy link
Member

@alexanderldavis it looks like there are some CI failures here when you get some time.

@jszwedko jszwedko enabled auto-merge (squash) February 15, 2024 17:42
auto-merge was automatically disabled February 15, 2024 17:42

Head branch was pushed to by a user without write access

@jszwedko jszwedko enabled auto-merge (squash) February 15, 2024 17:44
@jszwedko jszwedko merged commit b9e67eb into vectordotdev:develop Feb 15, 2024
3 of 8 checks passed
@alexanderldavis
Copy link
Contributor Author

@jszwedko I'm struggling to find a good way to pass the linter for older kube versions. minReadySeconds was added to Statefulsets in v1.22, but made generally available in v1.25. Do you have a recommendation for how that should be handled?

@jszwedko
Copy link
Member

@alexanderldavis I was expecting the failing CI checks to block the automerge but apparently they didn't 😓 I opened #371 to revert.

minReadySeconds was added to Statefulsets in v1.22, but made generally available in v1.25

My assumption would be that we'd only want to template it out for v1.25+ then, but maybe I'm missing something 🤔

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.

2 participants