ppkarwasz commented on issue #2151:
URL:
https://github.com/apache/logging-log4j2/issues/2151#issuecomment-2023138028
I am closing this, since a new `kubernetes-log4j` lookup is available since
version 6.11.0 of Kubernetes Client (cf.
[announcement](https://github.com/fabric8io/kubernetes-
ppkarwasz closed issue #2151: Log4j incompatible with recent kubernetes-client
URL: https://github.com/apache/logging-log4j2/issues/2151
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific c
ppkarwasz commented on issue #2151:
URL:
https://github.com/apache/logging-log4j2/issues/2151#issuecomment-1887084583
@Amya28,
If you don't use the `KubernetesLookup` (i.e. you don't have `${k8s:...}`
placeholders in your config file), you can remove the `log4j-kubernetes`
dependenc
Amya28 commented on issue #2151:
URL:
https://github.com/apache/logging-log4j2/issues/2151#issuecomment-1887037647
@ppkarwasz @vy
There's no KubernetesLookup.
In our case, we are working with spring boot and through Spring cloud the
kubernetes version is set to latest 6.9.2 by fra
vy commented on issue #2151:
URL:
https://github.com/apache/logging-log4j2/issues/2151#issuecomment-1878804058
@ppkarwasz, yes, I have seen fabric8io/kubernetes-client#5682 discussion.
Thanks for reporting the issue to the upstream. I agree that if
`kubernetes-client` wants to adopt `log4j
ppkarwasz commented on issue #2151:
URL:
https://github.com/apache/logging-log4j2/issues/2151#issuecomment-1878791937
@vy,
After the explanations provided by @manusa in
fabric8io/kubernetes-client#5682, I think that the best solution would be to
either move `log4j-kubernetes` to a F
vy commented on issue #2151:
URL:
https://github.com/apache/logging-log4j2/issues/2151#issuecomment-1878659536
@Amya28, are there any particular reasons you choose `KubernetesLookup` over
exporting associated Kubernetes configuration to environment variables and
accessing them using `Envir
ppkarwasz commented on issue #2151:
URL:
https://github.com/apache/logging-log4j2/issues/2151#issuecomment-1875029797
@Amya28,
In Maven you **need** to specify an artifact's version, it throws an error
if you don't. The reason you don't see it in `log4j-kubernetes/pom.xml` is that
w
Amya28 commented on issue #2151:
URL:
https://github.com/apache/logging-log4j2/issues/2151#issuecomment-1875016646
> @Amya28,
>
> thank you for the issue report. Currently `log4j-kubernetes` is compiled
against version 5.12.4:
>
>
https://github.com/apache/logging-log4j2/blob
ppkarwasz commented on issue #2151:
URL:
https://github.com/apache/logging-log4j2/issues/2151#issuecomment-1874962737
@Amya28,
thank you for the issue report. Currently `log4j-kubernetes` is compiled
against version 5.12.4:
https://github.com/apache/logging-log4j2/blob/846997
Amya28 commented on issue #2151:
URL:
https://github.com/apache/logging-log4j2/issues/2151#issuecomment-1874907608
https://github.com/apache/logging-log4j2/blob/rel/2.22.1/log4j-kubernetes/pom.xml
This doesnot specify the kubernetes-client version hence, it is fetching to
the late
Amya28 opened a new issue, #2151:
URL: https://github.com/apache/logging-log4j2/issues/2151
## Description
While using the latest log4j release version ; we encountered the following
error :
ERROR StatusConsoleListener Unable to create Lookup for k8s
java.lang.NoSuchMethodErro
12 matches
Mail list logo
