[
https://issues.jboss.org/browse/JBIDE-21627?page=com.atlassian.jira.plugi...
]
Marián Labuda commented on JBIDE-21627:
---------------------------------------
I was playing with deploying of docker images lately and I found following workflow.
When I have a pod and I want a service for it, I can do "oc expose pod pod-name"
and it creates a service for the pod. But pod and service have still internal IP so to
access to it I need another exposure "oc expose service service-name" which
creates a new routing which is accessible. E.g. I was using openshift/hello-openshift
image as a dummy use case and when pod was created I could not access to it yet, when
service was created, I still could not access to it, but once routing is existing, it is
accessible. This feature will be much more useful once JBIDE-20937 is done. That is
because user could create pod from json and then create further resources (service and
routing) by exposure.
Enable exposure of OpenShift resources in tooling
-------------------------------------------------
Key: JBIDE-21627
URL:
https://issues.jboss.org/browse/JBIDE-21627
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Labels: openshift_v3
Fix For: 4.4.x
It would be nice if we would have something similar as oc binary to expose an existing
resource. To expose existing pods or services.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)