Re: [atomic-devel] Exposing Pods to external network

Thanks for the reply.

Questions:

1. What distro of Atomic are you using?

Fedora-Cloud-Atomic-23-20160607.x86_64-ap-southeast-2-HVM-standard-0 (ami-0f69406c)

2. How have you set up the Services for those pods?

created cluster based on http://www.projectatomic.io/docs/gettingstarted/

Its simple ngingx deployment and created service using

kubectl expose deployment my-nginx --port=80

web server is accessible only within the cluster not from outside the cluster to external network.

On Thu, Jul 7, 2016 at 1:16 AM, Josh Berkus <jberkus redhat com> wrote:

On 06/21/2016 01:37 PM, Rafiqul Islam wrote:
> Dear Team
> Thanks for this wonderful project. I have created a kuberntes cluster
> based on fedora atomic image
> (http://www.projectatomic.io/docs/gettingstarted/) . We can run
> applications running on pods from inside the network. However we are not
> able access these application from external network. There may be a load
> balancer concept to expose services to external network. Could you
> please help enlighten me on the load balancer to expose services to
> external network?

Sorry for hold on this; we had a glut of spam and I didn't notice your
question waiting in moderation.

Questions:

1. What distro of Atomic are you using?

2. How have you set up the Services for those pods?

--
--
Josh Berkus
Project Atomic
Red Hat OSAS

Rafiqul Islam | Technology, Ops, and Infrastructure Lead

M: +8801709651000

Skype: islamraofu | E: rafiqul telenordigital com