<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Https on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/https/</link><description>Recent content in Https on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Sat, 18 Apr 2020 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/https/atom.xml" rel="self" type="application/rss+xml"/><item><title>Harbor Using a Self-Signed Certificate for HTTPS Access</title><link>https://www.chenshaowen.com/en/blog/support-https-access-harbor-using-self-signed-cert.html</link><pubDate>Sat, 18 Apr 2020 00:00:00 +0000</pubDate><atom:modified>Sat, 18 Apr 2020 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/support-https-access-harbor-using-self-signed-cert.html</guid><description>In an earlier post, Installing Harbor with Helm, I described in detail how to install Ingress and Harbor and finally push an image successfully. There the domain was publicly reachable and the certificate was issued by a certificate authority. In an intranet environment, however, we need to use an internal</description><dc:creator>微信公众号</dc:creator><category>Harbor</category><category>Kubernetes</category><category>Https</category><category>Images</category><category>Certificates</category><category>Operations</category></item></channel></rss>