81–90 of 256 posts
Earlier quoted context omitted.
Ditto - I would also be interested in a similar migration guide from docker-compose to k8s in DO.
check this out: https://github.com/kubernetes/kompose
I'm a long time happy DO user, this is exciting. I've been managing multiple docker apps (using docker-compose) on DO for years. Is there a guide I can use to transition my apps from docker-compose to k8s? I've dabbled in k8s, but am not an expert at all. Any suggestions?
Check this out: https://github.com/kubernetes/kompose and this article may help: https://www.digitalocean.com/community/tutorials/modernizing...
Earlier quoted context omitted.
hi, yes no charges for the managed / master nodes. This is Shiv from DO (I head Products there).
Can you give some insight on whether the master nodes are tiered and if so, how they are tiered. My DO master node doesn't respond to commands as quickly as GKE's but I don't know if that's because it's dependent on the tier I chose for the nodes in the node pool.
Master node tiering is something on our roadmap for the future and not currently implemented.
Hmm, now all it needs is just a comprehensive tutorial for somebody who ignored the whole container fuss so far (happy with Ansible). How to get from 0 to 100 to use Kubernetes?
I'm a long time happy DO user, this is exciting. I've been managing multiple docker apps (using docker-compose) on DO for years. Is there a guide I can use to transition my apps from docker-compose to k8s? I've dabbled in k8s, but am not an expert at all. Any suggestions?
My understanding is that you'll still need to do some work, especially if you are building via compose instead of pointing to an image on a registry.
Do I understand correctly that they provide the manager nodes for free?
Yes, this is the pricing model for everyone except EKS/AWS as I understand it. Manager nodes are bundled with whatever you spend on your worker nodes. Google has gone so far with GKE as to offer HA masters distributed across availability zones at no extra cost. (On the day that Amazon announced EKS general availability, if I remember correctly, which is priced at $250/mo base cost, before you even get around to spend…
Just want to call out that our worker node pricing is the same as our Droplets (servers). There is no price markup on using our managed service. In fact it's cheaper than deploying it yourself on DO because you don't have to pay for the master node.
Earlier quoted context omitted.
We have a big roadmap for 2019. Queues are interesting and so are functions in general. Nothing to share today but those are items we are assessing for future roadmaps :)
Is application hosting (heroku, app engine, elb) on the roadmap?
This is an open-source fork of Deis Workflow.
We're hoping to add support for Digital Ocean's Kubernetes and ancillary services like storage in the next release. Preliminary testing indicates that it is very much possible. The only dependencies of a prod Workflow deployment are, any compliant Kubernetes, Load Balancers, and an S3-api compatible storage, all of which are available on DO now.
The latest Hephy release does not yet support general S3-api compatibility with arbitrary S3 providers like DO, but DigitalOcean is our first target platform for expanding the supported offerings. The pull requests are open right now.
(Currently supported platforms include GCP/GKE, Amazon, and Azure AKS.)
Been a user of DOs beta kubernetes service and it works well. Though I would say the title of the linked article is a bit misleading. It is a Kubernetes as a service, like EKS, GKE and AKS. But not vanilla container service a la ECS, Fargate, the former Docker Cloud, etc.
Container Service as a Service
Been a user of DOs beta kubernetes service and it works well. Though I would say the title of the linked article is a bit misleading. It is a Kubernetes as a service, like EKS, GKE and AKS. But not vanilla container service a la ECS, Fargate, the former Docker Cloud, etc.