A couple of weeks ago I presented my talk:
Elixir, Kubernetes, and minikube
in the Elixir Meetup #5 organized by the fine people on curiosum.com.
This talk is based on chapter 4 of my book "Deploying Elixir: Advanced Topics".
If you haven't gotten the book, this is an excellent way to see what the book is about.
Watch the recorded talk here:
About
I'm Miguel Cobá. I write about Elixir, Elm, Software Development, and eBook writing.
- Follow me on Twitter
- Subscribe to my newsletter
- Read all my articles on my blog
- Get my books:
Top comments (9)
Heyo,
Would you please consider embedding your video here instead of just linking to it? This way folks can see your content and discuss things on DEV without having to navigate elsewhere.
You might not have realized, but DEV actually allows folks to embed YouTube & Vimeo videos via Liquid Tags. For instance, writing:
{% embed https://www.youtube.com/watch?v=dQw4w9WgXcQ %}Creates:
By the way, here's a link to the editor guide where you can see other liquid tags and formatting options.
Hope this is helpful! 🙂
Nice to know. Going to change it. Thanks Michael
Changed it. Much better now. :)
Awesome! No probs at all, happy to help!
A quick question. You don't make any use of the Erlang cookie. How is it so?
It is because of the libcluster strategy used. That doesn't require any cookie to connect nodes among themselves. It uses DNS to get a list of server names and then connect them to form a cluster.
Ok! Thanks. On the use case of "native clusters", I understand that Channels need a native cluster to work. But if you don't "natively clusterize" you Elixir-Phoenix app, would you need to add a WS server and configure the Ingress for WS? Please feel free to redirect to some doc. Many thanks
Channels should work just the same no matter how the cluster was created, either by cookies, or using a libcluster strategy.
About the Ingress for WS, I don't really know the answer. I might learn about it and write a future article on it.
Thanks for the topic idea :D
I meant "native" by an Erlang cluster, in opposition of the k8 cluster. So I wondered how to make WS work between pods of a Phoenix app if you don't Erlang-clusterize (<=> "native" in my mind), and just have the k8 network.