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

We have subcommands master and node that reflect old versions of the benchmark where there were just two sections, which were implemented in test files cfg/<benchmark version>/master.yaml and cfg/<benchmark version>/node.yaml respectively. For all the spec versions we now support, there are several more sections (for example etcd has its own section). We have the --targets parameter for

I came across several instances in only a single .go file where log.Warningf and log.Errorf were being used incorrectly (they passed in parameters but did not use %v-type replacement fields in the message string, as an example - see kiali/kiali#3628).

This issue is to ask that someone go through the entire Go codebase and make sure that problem is not found anywhere e

$ 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.

I noticed these today:

https://github.com/fabric8io/kubernetes-client/blob/0a4794f7d1581b3becb3d4f6f8c743941c6d9956/kubernetes-client/src/main/java/io/fabric8/kubernetes/client/dsl/base/HasMetadataOperation.java#L72-L74

https://github.com/fabric8io/kubernetes-client/blob/0a4794f7d1581b3becb3d4f6f8c743941c6d9956/kubernetes-client/src/main/java/io/fabric8/kubernetes/client/dsl/base/HasMetadata

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.

Setting logging.level.org.apache.camel=DEBUG does not affect integration logs.

So if users set flag --logging-level org.apache.camel=DEBUG, that is currently translated into the property above and does not work.

The correct mapping should be something like: quarkus.log.category."org.apache.camel".level=DEBUG

We should also change the doc to point to the Quarkus documentation for con

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