+1 (non-binding)
Thanks !
regards,
François Papon
fpa...@apache.org
On 15/08/2018 12:21, Christian Schneider wrote:
> The main change in this release is to have two kinds of checks: liveness
> and readiness. This matches what kubernetes wants to check. At least in
> kubernetes failing the live
+1
- Ray
On Wed, Aug 15, 2018 at 5:16 AM, Karl Pauls wrote:
> +1
>
> regards,
>
> Karl
> On Wed, Aug 15, 2018 at 10:22 AM Christian Schneider
> wrote:
> >
> > The main change in this release is to have two kinds of checks: liveness
> > and readiness. This matches what kubernetes wants to check
GitHub user timothyjward opened a pull request:
https://github.com/apache/felix/pull/150
Configuration Admin Security can cause a NoClassDefFoundError
Fixes FELIX-5908
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/timothyjward/f
[
https://issues.apache.org/jira/browse/FELIX-5908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581038#comment-16581038
]
Timothy Ward commented on FELIX-5908:
-
The attached GitHub Pull Request contains two
[
https://issues.apache.org/jira/browse/FELIX-5908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581037#comment-16581037
]
ASF GitHub Bot commented on FELIX-5908:
---
GitHub user timothyjward opened a pull req
Timothy Ward created FELIX-5908:
---
Summary: NoClassDefFoundError for the CM Security Domain combiner
Key: FELIX-5908
URL: https://issues.apache.org/jira/browse/FELIX-5908
Project: Felix
Issue Ty
+1
regards,
Karl
On Wed, Aug 15, 2018 at 10:22 AM Christian Schneider
wrote:
>
> The main change in this release is to have two kinds of checks: liveness
> and readiness. This matches what kubernetes wants to check. At least in
> kubernetes failing the liveness tests means the pod is killed and
+1 (non-binding)
On Wed, Aug 15, 2018 at 10:22 AM Christian Schneider <
ch...@die-schneider.net> wrote:
> The main change in this release is to have two kinds of checks: liveness
> and readiness. This matches what kubernetes wants to check. At least in
> kubernetes failing the liveness tests mea
The main change in this release is to have two kinds of checks: liveness
and readiness. This matches what kubernetes wants to check. At least in
kubernetes failing the liveness tests means the pod is killed and
recreated. Failing readiness tests means the pod is taken out of the load
balancer and
