Hi,

interesting. So the default project in minishift with the ovs-subnet SDN
has no special properties, but on a multitenant SDN the default
project was made public with oc adm pod-network make-projects-global?

So to make a service global but don't expose it to the public via a
route I have to make the project global on a multitenant SDN
environment?

I'm asking because making a project global can only be done with the
help of an admin.

Regards,

Gerhard

On Thu, Apr 18, 2019 at 09:40:19AM +0200, Nikolas Philips wrote:
>    Hi Gerhard,
>    OpenShift uses by default the "ovs-subnet" SDN (software-defined
>    network) plugin. I think this is the only one supported with minishift.
>    With the "ovs-subnet" plugin, all Services are from all Namespaces
>    reachable.
>    So all you need to do is creating a [1]Service for your
>    [2]Deployment/DeploymentConfig. The inside your cluster resolvable FQDN
>    of your service ist always
>    <service-name>.<namespace-name>.svc
>    Regards,
>    Nikolas
>
>    Am Do., 18. Apr. 2019 um 07:33 Uhr schrieb Gerhard <[3][email protected]>:
>
>      Hi,
>      I'm trying to find out how docker-registry.default.svc is made. It
>      is a
>      service that is visible to all projects. If I want to build a
>      similar
>      thing how should I do that?
>      I found
>          oc adm pod-network make-projects-global
>      But that doesn't work on minishift because there is no multitenant
>      plugin installed. But there is still docker-registry.default.svc, so
>      there must be an other way to implement this.
>      Can you tell what I have to read, to learn how to do this?
>      Gerhard
>      _______________________________________________
>      users mailing list
>      [4][email protected]
>      [5]http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
> References
>
>    1. 
> https://docs.openshift.com/container-platform/3.11/architecture/core_concepts/pods_and_services.html#services
>    2. 
> https://docs.openshift.com/container-platform/3.11/dev_guide/deployments/how_deployments_work.html
>    3. mailto:[email protected]
>    4. mailto:[email protected]
>    5. http://lists.openshift.redhat.com/openshiftmm/listinfo/users

_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to