Open vorburger opened 5 years ago
future participants not running with a privileged admin account
Just FTR: Following the (my..) Quarkus Doc steps when logging into the cluster with a token obtained from the /console/
UI to which one logged in with cluster admin account, it works just fine.
FTR: It seems to work, even for a "normal user" (via oc login
and typing Username and Password, no token).
BTW: The guide (above) is actually wrong, I fixed it in https://github.com/quarkusio/quarkus/pull/1898.
So it seems that the problem is that we cannot patch the build config until we have created it and oc new-app will both create the build config and start a build. One solution may be to use oc cancel-build bc/quarkus-quickstart-native
after the oc new-app and then patch the bc and then use oc start-build bc/quarkus-quickstart-native
.
FTR: @tqvarnst meanwhile documented this with an update to https://quarkus.io/guides/openshift-s2i-guide - we can probably close this issue now?
Try https://github.com/quarkusio/quarkus/blob/master/docs/src/main/asciidoc/openshift-s2i-guide.adoc (which should appear on https://quarkus.io/guides/openshift-s2i-guide very soon..) on the Workshop Demo Cluster.
Be particularly mindful of future participants not running with a privileged admin account; the
patch
to increase thelimit
may be a a problem, and need a solution in a set up such as this.Ultimate goal of this issue would be to create a Guide for this Native S2I.