Daniel Froehlich

Hey, I am wondering what is the state of this case and project. Is it still being maintained? I am seeing a lot of good PRs also on the original...

I vote for MOVE, because history is important. Just my two cents Dan --- Sent from mobile, please excuse brevity. [email protected], +49 176 10 24 84 33 John R Barker...

I suggest we switch to the operator based deployment. AMQ Broker 7.10 docs describe how to deploy the operator using CLI, without OLM. This approach should work with MicroShift. https://access.redhat.com/documentation/en-us/red_hat_amq_broker/7.10/html-single/deploying_amq_broker_on_openshift/index#proc-br-deploying-operator-cli_broker-ocp...

Maybe with a list of 109 entries in the label? The issue today is that license information can be located anywhere in the image and it is very hard to...

If I would work for an organization doing tough compliance checks on containers, it would be important for me that if the license label provides accurate and complete information, so...

Today, I grepped for "license" in my local openshift demo setup which contains ~300 image layers. In total, I could find ~180 unique different license files. You are right, there...

what is also important is that the reference to `` works unmodified with the runtime, e.g. if used in systemd file, scripts using podman, microshift etc. No matter what the...

Thx for progressing on this! I would feel better with some automated CI test cases that mimic the actual use case as a smoke test: a container image with whiteouts...

No, that "important" section is still correct. But seeing the rendered version, I notice that "Checking version update path"-> "MicroShift version 4.16" is missing a bullet for a V4.16 to...

@aravipra , the snippets/microshift-rhde-compatibility-table-snip.adoc table: If I see it correctly, in each row, we document both the "from" version and the "to" version upgrade path. So inthe 4.16 row, the...