Jx: Add support for Digital Ocean

[jstrachan]

I notice that kops recently added support for Digital Ocean
https://github.com/kubernetes/kops/blob/master/docs/tutorial/digitalocean.md

So we should be able to create a jx create cluster do for using kops on DO - the current jx create cluster aws uses kops under the covers to spin up the kubernetes cluster - so we’ve hopefully done the heavy lifting already

[tcarrio]

This seems like a good idea, but it's worth mentioning that even that page says

WARNING: digitalocean support on kops is currently alpha meaning it is in the early stages of development and subject to change, please use with caution.

Support for this would be experimental at best, but it wouldn't hurt to target the API and keep it up to date as changes occur.

[barrymac]

Managed to get this quite far on an existing kubernetes cluster in DO, but only after installing a fix for the persistence CSI plugin which can be found here: https://github.com/digitalocean/csi-digitalocean/issues/86

Only issue at this stage seems to be permissions on the mongoDB volume which is needed for chart museum

[barrymac]

Aaand all the compliance tests pass, so that instils some confidence!

[akeating]

I notice DO Kubernetes is now in _Limited Availability_ which I understand is a prelude to _GA_.

[ghost]

Can you please update us on the current status of DO?

[zetaron]

DO Kubernetes is now in General Availability and managed clusters can be created using eg. the official doctl kubernetes cluster create command, much like what's currently done for Amazons EKS with its eksctl.

[jstrachan]

@zetaron awesome - should be super easy to create a jx create cluster do CLI in Jenkins X.

Anyone fancy trying it out? We love pull requests! https://jenkins-x.io/contribute/

@balazs-pinter it looks like most things work - there's just one issue on Digital Ocean - the Kubernetes REST API is exposed inside the kubernetes cluster using https but there is no valid cert for the DNS name when pods try to use the internal kubernetes service. So java code fails in Jenkins's use of kubernetes plugin and the kubernetes credential provider plugins.

A workaround is I think adding the environment variable KUBERNETES_TRUST_CERTIFICATES=true in the Jenkins pod and the jx-build-template pods too.

Ideally we'd get the kubernetes service exposed either as http or with a valid cert then we won't need these workarounds

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[solarsoft0]

any progress on this

[thakkarsagar12]

any progress on this

???

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[VanThanhThai]

any one looking into this?