External IP's

[alex goretoy]

https://www.youtube.com/watch?v=pNe1wWeaHOU&list=PLYI8318YYdkCsZ7dsYV01n6TZhXA6Wf9i&index=1

Best regards,
Alex Goretoy
Goretoy Web Services - CEO

alex at goretoy.com

https://www.youtube.com/watch?v=pNe1wWeaHOU&list=PLYI8318YYdkCsZ7dsYV01n6TZhXA6Wf9i&index=1

Senior Solutions Architect Entrepreneur Artist Director Therapist
Professional Boss

Portfolio  Linkedin  Twitter  StackOverflow  Github  Gist  TreeHouse
 Freelance CV

http://audiobible.life CHECK IT OUT! We The People! Have The Power!
Don't Be A Clown! Join The Revolution!

On Wed, Sep 6, 2017 at 7:27 PM, Tim Van Steenburgh <
tim.van.steenburgh at canonical.com> wrote:

> Hi Micheal,
>
> You don't get the external IP automatically because the k8s cloud-provider
> flag is not automatically set to vsphere for you (yet).
>
> When you deploy to AWS with conjure-up, we set the k8s cloud-provider for
> you so that you can use AWS features like ELBs and EBS. We intend to add
> this native-cloud integration for vsphere also, but haven't yet. So for now
> you'd need to do it manually. More info here: https://github.com/juju-
> solutions/bundle-canonical-kubernetes/issues/402
>
> Hope that helps,
> Tim
>
> On Tue, Sep 5, 2017 at 7:31 PM, Micheal B <tictoc at tictoc.us> wrote:
>
>> My lab is juju using vsphere kubernetes - https://jujucharms.com/docs/2.
>> 1/help-vmware - my nodes all get their IP’s and DNS from a local domain
>> server and tested used using the - https://kubernetes.io/docs/con
>> cepts/services-networking/dns-pod-service/
>>
>> All of the Nodes Master and worker have 8GB Mem, 30GB of disk space as
>> well. The VMware environment is my main lab and it’s well established, I do
>> allot of testing [image: ☺]
>>
>>
>>
>>
>>
>> So as far as I know everything looks good and the logs seem happy on the
>> DNS side. I did have to adjust my DHCP Server some and the deployment
>> script to use the server but other than that it seems to be fine.  It’s
>> part of the reason I am looking for a way to build a deployment YAML file
>> out of my current running environment so I can change settings without
>> redepoloying and having to redo all of the DNS Server names etc.
>>
>>
>>
>> But when I start testing using this - https://kubernetes.io/docs/tut
>> orials/stateless-application/expose-external-ip-address/
>>
>>
>>
>> I never get an external IP Address – I have been through several
>> documents and test some ingress and such still not getting an IP
>> automatically
>>
>>
>>
>> Now if I do the same above but add in
>>
>>
>>
>> kubectl expose deployment hello-world --type=LoadBalancer
>> --external-ip=192.168.0.162 --name=my-service          – set the
>> externalip= is one of my worker nodes then I can hit the deployment fine.
>>
>>
>>
>> So what else am I missing?
>>
>>
>>
>>
>>
>> Cheers
>>
>>
>>
>> Micheal
>>
>>
>>
>>
>>
>> --
>> Juju mailing list
>> Juju at lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>>
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20170906/a79b688e/attachment.html>