[
https://issues.jboss.org/browse/JBIDE-23014?page=com.atlassian.jira.plugi...
]
Marián Labuda edited comment on JBIDE-23014 at 9/16/16 2:58 AM:
----------------------------------------------------------------
Not sure how this was meant to be working, but something is not working and other things
which could are not working too.
I have a CDK and I changed cluster namespace from openshift to something different.
"customproject". I guess I would have to set proper policy, rules for the
project with oadm command etc etc. to have it as a cluster namespace.
First thing. Although I changed default value "openshift" to something different
(what probably is not the meant cluster namespace), retrieving templates and image builder
is not working correctly. New OpenShift Application wizard still lists templates with
"openshift" namespace, although image builders are not listed here anymore. So
it results to a list of template with "openshift" namespace without image
builders for this namespace although cluster namespace is not "openshift"
anymore and I have not opened wizard on the "openshift" project.
Next thing, which I am not sure if should be possible, but if cluster namespace is not
anything else but project with proper rules, policy.. it should work. I have another
project, let's say "customproject02". I have uploaded a template to project
"customproject". I am able to be switched on command line client to
customproject02 and still list template(s) on customproject. But in tooling if I select
customproject02 and open a New OpenShift Application wizard on it via context menu, the
template with namespace "customproject" is not listed there although I set it as
a cluster namespace.
I am also missing units tests (one liner in Unit tests is not enough, and no integration
test for this)
was (Author: mlabuda):
Not sure how this was meant to be working, but something is not working and other things
which could are not working too.
I have a CDK and I changed cluster namespace from openshift to something different.
"customproject". I guess I would have to set proper policy, rules for the
project with oadm command etc etc. to have it as a cluster namespace.
First thing. Although I changed default value "openshift" to something different
(what probably is not the meant cluster namespace), retrieving templates and image builder
is not working correctly. New OpenShift Application wizard still lists templates with
"openshift" namespace, although image builders are not listed here anymore. So
it results to a list of template with "openshift" namespace without image
builders for this namespace although cluster namespace is not "openshift"
anymore and I have not opened wizard on the "openshift" project.
Next thing, which I am not sure if should be possible, but if cluster namespace is not
anything else but project with proper rules, policy.. it should work. I have another
project, let's say "customproject02". I have uploaded a template to project
"customproject". I am able to be switched on command line client to
customproject02 and still list template(s) on customproject. But in tooling if I select
customproject02 and open a New OpenShift Application wizard on it via context menu, the
template with namespace "customproject" is not listed there although I set it as
a cluster namespace.
Allow connections to configure the cluster namespace from which to
get clusterwide templates
--------------------------------------------------------------------------------------------
Key: JBIDE-23014
URL:
https://issues.jboss.org/browse/JBIDE-23014
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.4.1.Final
Reporter: Jeff Cantrill
Assignee: Jeff MAURY
Labels: connection, connection_wizard, new_and_noteworthy, openshift,
openshift_v3
Fix For: 4.4.2.AM1
There are a few places where we assume the cluster is configured with the openshift
namespace (e.gretrieve templates) which contains templates and other resources that are
available to everyone. We should provide a per connection configuration (advanced
property?) that allows us to change the default since it is not discoverable from the
server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)