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

chore: update logging-operator to 4.6.1 #663

Merged
merged 4 commits into from
May 29, 2024
Merged

Conversation

tobybellwood
Copy link
Member

This PR updates the upstream sub-chart for the logging-operator to 4.6.0 and utilises the new oci chart registry

@tobybellwood tobybellwood force-pushed the logging-operator-460 branch from d0b9729 to 7192cca Compare May 22, 2024 11:06
@smlx
Copy link
Member

smlx commented May 24, 2024

4.6.1 is available now with the patched fluent-bit.

https://github.com/kube-logging/logging-operator/releases/tag/4.6.1

edit: doh! you were too fast :D

@tobybellwood tobybellwood changed the title chore: update logging-operator to 4.6.0 chore: update logging-operator to 4.6.1 May 24, 2024
@tobybellwood
Copy link
Member Author

The post-install CRD update command will change because of this new registry

helm show crds oci://ghcr.io/kube-logging/helm-charts/logging-operator --version 4.6.1 | kubectl apply --server-side --force-conflicts -f -

@tobybellwood tobybellwood marked this pull request as ready for review May 28, 2024 04:21
Copy link
Member

@shreddedbacon shreddedbacon left a comment

Choose a reason for hiding this comment

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

As far as the changes in the PR goes, this looks fine.

From a functional view of the actual operation or update to the version and underlying logging operator, I can't provide proper feedback on.

@tobybellwood
Copy link
Member Author

Fully tested in the test cluster 😁

@tobybellwood tobybellwood merged commit cfa4548 into main May 29, 2024
17 checks passed
@tobybellwood tobybellwood deleted the logging-operator-460 branch May 29, 2024 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants