tadayosi commented on issue #2473:
URL: https://github.com/apache/camel-k/issues/2473#issuecomment-893307059
Yes, my goal is to adapt it as a GH action and run it in a CI workflow.
> Also, out of curiosity, does the monitoring stack come out of the box (in
the openshift-monitoring namespace)?
In reality, the out of the box configuration is quite austere like this:
```
$ k get po -A
NAMESPACE NAME
READY STATUS RESTARTS AGE
kube-system kube-flannel-ds-m6d8g
1/1 Running 0 6d21h
kubevirt-hostpath-provisioner
kubevirt-hostpath-provisioner-5jf7c 1/1 Running 0
6d21h
openshift-dns dns-default-qtpk2
3/3 Running 0 145m
openshift-ingress router-default-78d9fc46bb-nz8tk
1/1 Running 0 6d21h
openshift-service-ca service-ca-66bcdfc59-wbtg2
1/1 Running 3 6d21h
```
By default it's far from fully functional OCP environment. That's another
reason why we might need to wait for
https://github.com/redhat-et/microshift/issues/144 to be done from Microshift
side.
--
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 comment.
To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
