No reason. Their dependency tree looks small, please open an issue on
GitHub and we'll try to get it added.
On Sun, Jun 12, 2016 at 6:59 AM, aleks wrote:
> Hi.
>
> I haven't found flocker in the list of supported PersistentVolume plug-ins
>
> https://docs.openshift.org/latest/architecture/additi
There's not an efficient API query to determine that today. Internally, the
API server maintains a reverse index of username to group names by watching
updates to the Group API objects
On Thu, Jun 16, 2016 at 4:03 PM, Marc Boorshtein
wrote:
> oh, if the groups field on the user is deprecated how
so i'll need to query each group and look for the user in question to be a
member?
On Thu, Jun 16, 2016 at 4:24 PM, Jordan Liggitt wrote:
> There's not an efficient API query to determine that today. Internally,
> the API server maintains a reverse index of username to group names by
> watching
On 06/16/2016 02:01 PM, Srinivas Naga Kotaru (skotaru) wrote:
Just to share an update
Am able to successfully install and configure metrics and logging
using real certs, node classification and separate apps and OPS ES
clusters.
Am happy that this setup finally working and live. Want to sha
oh, if the groups field on the user is deprecated how would I know what
groups a specific user has?
On Thu, Jun 16, 2016 at 3:57 PM, Jordan Liggitt wrote:
> Your command looks correct. Specifying groups directly on a user via the
> groups field is deprecated. `oc get group cluster-administrators
Just to share an update
Am able to successfully install and configure metrics and logging using real
certs, node classification and separate apps and OPS ES clusters.
Am happy that this setup finally working and live. Want to share feedback from
operation side. There is some scope to improve an
Your command looks correct. Specifying groups directly on a user via the
groups field is deprecated. `oc get group cluster-administrators -o yaml`
would show that your command is effective.
When a user makes an API request, their effective groups are determined by
combining the names of the Group
I can't seem to add a user to a group. I have a user:
$ curl -k -v -XGET -H "User-Agent: oc/v1.1.2 (darwin/amd64)
openshift/2711160" -H "Authorization: Bearer
PDqIrEiOTqtwJvHDcTB-snC5FpcpnCz5fIrz7S6ORCI"
https://openshift.rheldemo.lan:8443/oapi/v1/users/0b126172-33e9-11e6-9c91-525400d4fbc4
* T
Thanks!
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
On Thu, Jun 16, 2016 at 10:19 AM, v wrote:
> You could modify your app so it returns a 200 status code in the header
> but shows the 503 error in the body. In that case your service should pass
> the health checks and haproxy should display the body with the 503 error.
That a terrible idea beca
You could modify your app so it returns a 200 status code in the header but
shows the 503 error in the body. In that case your service should pass the
health checks and haproxy should display the body with the 503 error.
Am 2016-06-16 um 15:48 schrieb Philippe Lafoucrière:
For the record,
For the record, having /* redirected to /maintenance with a 307, then a 503
doesn't work either :(
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
That value comes from the `oadm router` command you need to pass it
the --images flag and provide the same format string you've configured
in your master-config when you create the router. Now that it's
already created you can just edit the deployment config.
On Thu, Jun 16, 2016 at 8:47 AM, Den C
I edited my playbook.
this in my master-config:
docker.io/my-registry/origin-${component}:${latest}
But this is in the dc config (when I try to start a router).
image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49
and it fails.
From: dencow...@hotmail.com
To: sdod...@redhat.com; ccole...
14 matches
Mail list logo
