-
Notifications
You must be signed in to change notification settings - Fork 9
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
Logging operator update #574
Conversation
47c289e
to
639d065
Compare
worth noting for the record that this is a neater way to install those CRDs
|
TIL thanks! |
8c8a8c1
to
83843dd
Compare
c93225f
to
afeb596
Compare
afeb596
to
11d9d39
Compare
kube-logging has moved to a new repository.
This flag causes e.g. daemonsets and statefulsets to be forcefully deleted and recreated if required for a configuration change. Unfortunately this can mean transient data loss (e.g. data in buffers), but that seems to be a reasonable tradeoff.
11d9d39
to
ae7c7d0
Compare
hi @tobybellwood any problem with merging this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - happy to merge
Worth noting here that in the upgrade process if you encounter an error with PSP
You should use the mapkubeapis helm plugin to remove the PSP from the helm cache
|
This PR updates the logging operator, which is the underlying log collection system of the
lagoon-logging
chart.Importantly, this update requires some manual CRD updates to be applied after the chart is upgraded, if upgrading from an earlier version of
lagoon-logging
:helm repo add kube-logging https://kube-logging.github.io/helm-charts helm show crds kube-logging/logging-operator --version 4.2.3 | kubectl apply --server-side --force-conflicts -f -
I'll also add the instructions above to the release notes.