[
https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-22959:
---------------------------------------
[~adietish] To my knowledge I don't know that we surface replica sets at the moment,
but this leads to a design question we need to resolve. DeploymentConfigs are moving
upstream and are (I think) being rebranded as Deployments. There will be a transitional
period between OS dc and Kube deployments where the os kind will be more full featured.
Aside from what we call it, we will need to figure out how to make the two co-exist in the
ui; the console is or is planning to do that. It will be represented and identified
differently (i believe) which means we will need to understand how to degrade
functionality most likely
Properties: rename Deployment to Replication Controller
-------------------------------------------------------
Key: JBIDE-22959
URL:
https://issues.jboss.org/browse/JBIDE-22959
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.1.AM3
Reporter: Marián Labuda
Priority: Minor
Labels: openshift_v3, properties
Fix For: 4.4.x
We should rename Deployment in tabbed properties to Replication Controller. I was
complaining about it some times ago, but now I found also good reason to change it -
underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation
of replication controller). And those resources are something a bit different although it
has similar functionality. For users coming from Kubernetes world or those who are
familiar with Kubernetes, could this be a bit misleading.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)