New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes support #59

Closed
jroper opened this Issue Mar 22, 2016 · 13 comments

Comments

Projects
None yet
8 participants
@jroper
Member

jroper commented Mar 22, 2016

It would be great if Lagom also supported Kubernetes as a target production platform.

This would require the following things:

  • Kubernetes based ServiceLocator implementation
  • Pick up configuration for Akka clustering, service location and database location from Kubernetes
  • sbt-native-packager based packaging to produce artifacts that can be deployed by Kubernetes
  • Documentation

To be clear, this is not going to be implemented by Lightbend, but we are creating this issue to indicate that we would be happy to accept such contributions from the community. We recommend, at least initially, implementing it in a separate repo, which could later be pulled into the Lagom GitHub organization if that makes sense.

@jroper jroper added the help wanted label Mar 22, 2016

@jroper jroper changed the title from Kubernates support to Kubernetes support Mar 22, 2016

@huntc

This comment has been minimized.

Show comment
Hide comment
Contributor

huntc commented Mar 28, 2016

@hmnasr

This comment has been minimized.

Show comment
Hide comment
@hmnasr

hmnasr Oct 16, 2016

I want to deploy my service on my own kubernetes environment any new news

hmnasr commented Oct 16, 2016

I want to deploy my service on my own kubernetes environment any new news

@huntc

This comment has been minimized.

Show comment
Hide comment
@huntc

huntc Oct 16, 2016

Contributor

I actually have a DNS SRV implementation in flight. More on that this week.

Contributor

huntc commented Oct 16, 2016

I actually have a DNS SRV implementation in flight. More on that this week.

@lejoow

This comment has been minimized.

Show comment
Hide comment
@lejoow

lejoow Dec 25, 2016

Hello @huntc it looks like the project is now merged into https://github.com/typesafehub/service-locator-dns.

Quick question - is this production-ready? Are you using it in production by any chance?

Thanks!

lejoow commented Dec 25, 2016

Hello @huntc it looks like the project is now merged into https://github.com/typesafehub/service-locator-dns.

Quick question - is this production-ready? Are you using it in production by any chance?

Thanks!

@huntc

This comment has been minimized.

Show comment
Hide comment
@huntc

huntc Dec 25, 2016

Contributor

The DNS service locator is being used in production.

Contributor

huntc commented Dec 25, 2016

The DNS service locator is being used in production.

@johdah

This comment has been minimized.

Show comment
Hide comment
@johdah

johdah Aug 1, 2017

Is there any known projects on github or examples using service-locator-dns? I guess that there is a reason that this issue is still open?

johdah commented Aug 1, 2017

Is there any known projects on github or examples using service-locator-dns? I guess that there is a reason that this issue is still open?

@huntc

This comment has been minimized.

Show comment
Hide comment
@huntc

huntc Aug 1, 2017

Contributor

We have some guides and sample code coming within the next month.

Contributor

huntc commented Aug 1, 2017

We have some guides and sample code coming within the next month.

@johdah

This comment has been minimized.

Show comment
Hide comment
@johdah

johdah Aug 1, 2017

Nice, in the Lagom docs or in the service-locator-dns project?

johdah commented Aug 1, 2017

Nice, in the Lagom docs or in the service-locator-dns project?

@huntc

This comment has been minimized.

Show comment
Hide comment
@huntc

huntc Aug 1, 2017

Contributor

Initially as guides on our tech hub, with modifications to the Chirper sample.

Contributor

huntc commented Aug 1, 2017

Initially as guides on our tech hub, with modifications to the Chirper sample.

@huntc

This comment has been minimized.

Show comment
Hide comment
@huntc

huntc Aug 16, 2017

Contributor

I'd like to see this issue closed. What do you think @jroper - given that we now have the Tech hub guide: https://tech-hub.lightbend.com/guides/k8s-microservices/

Contributor

huntc commented Aug 16, 2017

I'd like to see this issue closed. What do you think @jroper - given that we now have the Tech hub guide: https://tech-hub.lightbend.com/guides/k8s-microservices/

@erip

This comment has been minimized.

Show comment
Hide comment
@erip

erip Dec 25, 2017

Contributor

I think this can be closed, too.

Contributor

erip commented Dec 25, 2017

I think this can be closed, too.

@renatocaval

This comment has been minimized.

Show comment
Hide comment
@renatocaval

renatocaval Jan 3, 2018

Member

Closing...

Member

renatocaval commented Jan 3, 2018

Closing...

@ignasi35

This comment has been minimized.

Show comment
Hide comment
@ignasi35

ignasi35 May 5, 2018

Member

For future reference. Currently the recommended way to deploy Lagom in kubernetes is using the Lightbend Orchestration tools

Member

ignasi35 commented May 5, 2018

For future reference. Currently the recommended way to deploy Lagom in kubernetes is using the Lightbend Orchestration tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment