July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-165) You dont need to be cluster-admin to be able to work with operator on OpenShift

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-165?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFWIP-165: ------------------------------- Description: Instructions how to install operator on OpenShift [1] are shown under cluster-admin role. As role, role-binding and crd are cluster scoped resources I would expect that only cluster-admin can specify that. However I wouldt expect to have cluster-admin role to be able to deploy application using operator with oc apply -f deploy/crds/quickstart-cr.yaml To be able to run this as developer user have to be granted (by cluster-admin) these permission: {code} oc create role wildfly-server --verb=* --resource=wildflyservers.wildfly.org -n <namespace> oc adm policy add-role-to-user wildfly-server developer --role-namespace=<namespace> -n <namespace> {code} Please make this clear in install procedure. [1] https://github.com/wildfly/wildfly-operator#OpenShift was: nstructions how to install operator on OpenShift [1] are shown under cluster-admin role. As role, role-binding and crd are cluster scoped resources I would expect that only cluster-admin can specify that. However I wouldt expect to have cluster-admin role to be able to deploy application using operator with oc apply -f deploy/crds/quickstart-cr.yaml To be able to run this as developer user have to be granted (by cluster-admin) these permission: {code} oc create role wildfly-server --verb=* --resource=wildflyservers.wildfly.org -n <namespace> oc adm policy add-role-to-user wildfly-server developer --role-namespace=<namespace> -n <namespace> {code} Please make this clear in install procedure. [1] https://github.com/wildfly/wildfly-operator#OpenS > You dont need to be cluster-admin to be able to work with operator on OpenShift > ------------------------------------------------------------------------------- > > Key: WFWIP-165 > URL: https://issues.jboss.org/browse/WFWIP-165 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > Instructions how to install operator on OpenShift [1] are shown under cluster-admin role. > As role, role-binding and crd are cluster scoped resources I would expect that only cluster-admin can specify that. > However I wouldt expect to have cluster-admin role to be able to deploy application using operator with > oc apply -f deploy/crds/quickstart-cr.yaml > To be able to run this as developer user have to be granted (by cluster-admin) these permission: > {code} > oc create role wildfly-server --verb=* --resource=wildflyservers.wildfly.org -n <namespace> > oc adm policy add-role-to-user wildfly-server developer --role-namespace=<namespace> -n <namespace> > {code} > Please make this clear in install procedure. > [1] https://github.com/wildfly/wildfly-operator#OpenShift -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-165) You dont need to be cluster-admin to be able to work with operator on OpenShift

by Martin Choma (Jira)

Martin Choma created WFWIP-165: ---------------------------------- Summary: You dont need to be cluster-admin to be able to work with operator on OpenShift Key: WFWIP-165 URL: https://issues.jboss.org/browse/WFWIP-165 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Choma Assignee: Brian Stansberry nstructions how to install operator on OpenShift [1] are shown under cluster-admin role. As role, role-binding and crd are cluster scoped resources I would expect that only cluster-admin can specify that. However I wouldt expect to have cluster-admin role to be able to deploy application using operator with oc apply -f deploy/crds/quickstart-cr.yaml To be able to run this as developer user have to be granted (by cluster-admin) these permission: {code} oc create role wildfly-server --verb=* --resource=wildflyservers.wildfly.org -n <namespace> oc adm policy add-role-to-user wildfly-server developer --role-namespace=<namespace> -n <namespace> {code} Please make this clear in install procedure. [1] https://github.com/wildfly/wildfly-operator#OpenS -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-165) You dont need to be cluster-admin to be able to work with operator on OpenShift

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-165?page=com.atlassian.jira.plugin.... ] Martin Choma reassigned WFWIP-165: ---------------------------------- Assignee: Jeff Mesnil (was: Brian Stansberry) > You dont need to be cluster-admin to be able to work with operator on OpenShift > ------------------------------------------------------------------------------- > > Key: WFWIP-165 > URL: https://issues.jboss.org/browse/WFWIP-165 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > nstructions how to install operator on OpenShift [1] are shown under cluster-admin role. > As role, role-binding and crd are cluster scoped resources I would expect that only cluster-admin can specify that. > However I wouldt expect to have cluster-admin role to be able to deploy application using operator with > oc apply -f deploy/crds/quickstart-cr.yaml > To be able to run this as developer user have to be granted (by cluster-admin) these permission: > {code} > oc create role wildfly-server --verb=* --resource=wildflyservers.wildfly.org -n <namespace> > oc adm policy add-role-to-user wildfly-server developer --role-namespace=<namespace> -n <namespace> > {code} > Please make this clear in install procedure. > [1] https://github.com/wildfly/wildfly-operator#OpenS -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12279) EE Concurrency Capability API

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12279: -------------------------------------- Summary: EE Concurrency Capability API Key: WFLY-12279 URL: https://issues.jboss.org/browse/WFLY-12279 Project: WildFly Issue Type: Enhancement Components: Concurrency Utilities Reporter: Eduardo Martins Assignee: Eduardo Martins There are several EE Concurrency resources which other subsystems (than EE) interact with, and that should be done using Capability API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-818) Update upstream pipelines to support Maistra TP12