fix: support logs db for k8s #1864
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
h4ck3rk3y
approved these changes
Nov 28, 2023
internal_testsuites/golang/testsuite/stream_logs_test/stream_logs_test.go
Outdated
Show resolved
Hide resolved
tedim52
force-pushed
the
tedi/fix-k8s-logs
branch
2 times, most recently
from
ecd6fff
to
4155be7
Compare
tedim52
force-pushed
the
tedi/fix-k8s-logs
branch
from
4155be7
to
e5d8454
Compare
github-merge-queue bot
pushed a commit
that referenced
this pull request
Nov 29, 2023
🤖 I have created a release *beep* *boop* --- ## [0.85.38](0.85.37...0.85.38) (2023-11-29) ### Bug Fixes * support logs db for k8s ([#1864](#1864)) ([8afa9c7](8afa9c7)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: kurtosisbot <kurtosisbot@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
service logsover kubernetes was mistakenly turned off when centralized logging over docker was implemented. This change turns it back on.Is this change user facing?
YES (users will be able to do
service logsover k8s)References (if applicable):