Live data from Hacker News

Jenkins X: a CI/CD solution for cloud applications on Kubernetes

jenkins.io

1–10 of 106 posts

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#4
post #3

No TLS on jenkins-x.com, tisk tisk.

it's using github pages for the main website i think so i'm not sure if it's possible to setup custom domain + custom ssl cert for it?

I've used cloudflare to do SSL for a custom github pages domain before.

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#5
post #3

No TLS on jenkins-x.com, tisk tisk.

it's using github pages for the main website i think so i'm not sure if it's possible to setup custom domain + custom ssl cert for it?

Should be able to use CloudFlare and "flexible" SSL setup. CNAME at the apex pointing to GitHub pages.

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#6
post #3

No TLS on jenkins-x.com, tisk tisk.

it's using github pages for the main website i think so i'm not sure if it's possible to setup custom domain + custom ssl cert for it?

It's possible but not very straightforward. Reference for anyone else trying to setup ssl cert for github pages: https://www.jonathan-petitcolas.com/2017/01/13/using-https-w...

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#7
post #3

Earlier quoted context omitted.

it's using github pages for the main website i think so i'm not sure if it's possible to setup custom domain + custom ssl cert for it?

Should be able to use CloudFlare and "flexible" SSL setup. CNAME at the apex pointing to GitHub pages.

Please don't do this. It gives the user the illusion that their connection is secure, but the connection between Cloudflare and the site is not secure. Arguably it's better to encrypt some of the route rather than none of it, but also giving people a false sense of security comes with its own drawbacks.

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#8

Earlier quoted context omitted.

Should be able to use CloudFlare and "flexible" SSL setup. CNAME at the apex pointing to GitHub pages.

Please don't do this. It gives the user the illusion that their connection is secure, but the connection between Cloudflare and the site is not secure. Arguably it's better to encrypt some of the route rather than none of it, but also giving people a false sense of security comes with its own drawbacks.

Actually "flexible" might not be needed, "full" without strict should work. Traffic is still over TLS, but a valid named certificate is not required.

Re: Jenkins X: a CI/CD solution for cloud applications on Kubernetes

#10
In no attempt to bash OP at all, but what is the HN policy on links that have been posted before?

Edit: Previous posts for reference

https://news.ycombinator.com/item?id=16622215

https://news.ycombinator.com/item?id=16626765

https://news.ycombinator.com/item?id=16628313

https://news.ycombinator.com/item?id=16658640

Post reply on HN