Summary

When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.

This means that when new versions of the application are created the unchanged dependencies can't be reused.

It would be a great enhancement if the application code where p

What steps did you take and what happened:
i am running kube-bench tool for Openshiftv3.11 and i see inconsistent result for similar tests.

file: cfg/rh-0.7/master.yaml

section - id: 5.2
text: "Verify the default OpenShift setting for the client-cert-auth argument"
audit: "/bin/sh -c'/usr/local/bin/master-exec etcd etcd grep ETCD_CLIENT_CERT_AUTH=true /proc/1/env

Kiali uses tooltip in multiple locations, in some cases style difers even for the same concepts.

I noticed some changes on this kiali/kiali-ui#1884 but it would require some global issue to review all tooltips and check that they look like similar (at least for the same concept).

$ minishift status
Minishift:  Running
Profile:    minishift
OpenShift:  Stopped
DiskUsage:  ERR of

perhaps this is related to the error state from the OpenShift isRunning check

It would be nice to include k8s liveness and readiness probes support.

Kind of issue

Feature request

Observed behavior

When the script is run in summarize mode, it shows the count of bricks in fstab, lvs, gluster volume info and mount and does not provide any information if the counts don't match.

Expected/desired behavior

When the count does not match for all 4, it should provide information about the difference and also possible commands t

I'm in the app folder.
I mkdir exports to make an export folder.
I run rake evm:export:service_dialogs -- --directory exports
I get back:

(in /var/www/miq/vmdb)
Error: argument --directory Destination directory must exist.
Try --help for help.

How can this be? I can ls and see my exports folder in this directory.

If I set:

camel.component.twitter-search.xxx

The camel-twitter component should be added to the set of dependencies automatically.

Also because the new property-binding mechanism goes in error otherwise.

We should inspect direct properties and property-files.
We may extend the search also to linked secrets and configmaps.

Add metrics based on monitor created/deleted, availability etc.