Merge pull request #5313 from trungnvfet/fix_http_https

Change http to https for security links

CONTRIBUTING.md

@@ -15,7 +15,7 @@ us a chance to try to fix the issue before it is exploited in the wild.
 The sign-off is a simple line at the end of the explanation for a commit. All 
 commits needs to be signed. Your signature certifies that you wrote the patch or
 otherwise have the right to contribute the material. The rules are pretty simple,
-if you can certify the below (from [developercertificate.org](http://developercertificate.org/)):
+if you can certify the below (from [developercertificate.org](https://developercertificate.org/)):
 
 ```
 Developer Certificate of Origin

docs/chart_best_practices/conventions.md

@@ -22,7 +22,7 @@ The directory that contains a chart MUST have the same name as the chart. Thus,
 
 ## Version Numbers
 
-Wherever possible, Helm uses [SemVer 2](http://semver.org) to represent version numbers. (Note that Docker image tags do not necessarily follow SemVer, and are thus considered an unfortunate exception to the rule.)
+Wherever possible, Helm uses [SemVer 2](https://semver.org) to represent version numbers. (Note that Docker image tags do not necessarily follow SemVer, and are thus considered an unfortunate exception to the rule.)
 
 When SemVer versions are stored in Kubernetes labels, we conventionally alter the `+` character to an `_` character, as labels do not allow the `+` sign as a value.
 

docs/chart_template_guide/yaml_techniques.md

@@ -7,7 +7,7 @@ to read.
 
 ## Scalars and Collections
 
-According to the [YAML spec](http://yaml.org/spec/1.2/spec.html), there are two
+According to the [YAML spec](https://yaml.org/spec/1.2/spec.html), there are two
 types of collections, and many scalar types.
 
 The two types of collections are maps and sequences:

docs/charts.md

@@ -71,7 +71,7 @@ Other fields will be silently ignored.
 ### Charts and Versioning
 
 Every chart must have a version number. A version must follow the
-[SemVer 2](http://semver.org/) standard. Unlike Helm Classic, Kubernetes
+[SemVer 2](https://semver.org/) standard. Unlike Helm Classic, Kubernetes
 Helm uses version numbers as release markers. Packages in repositories
 are identified by name plus version.
 
@@ -792,7 +792,7 @@ standard references that will help you out.
 
 - [Go templates](https://godoc.org/text/template)
 - [Extra template functions](https://godoc.org/github.com/Masterminds/sprig)
-- [The YAML format](http://yaml.org/spec/)
+- [The YAML format](https://yaml.org/spec/)
 
 ## Using Helm to Manage Charts
 

docs/developers.md

@@ -170,7 +170,7 @@ workflow for doing this is as follows:
 5. When you are ready for us to review, sign your commit, push your branch to GitHub, and
    then open a new pull request with us.
 
-For Git commit messages, we follow the [Semantic Commit Messages](http://karma-runner.github.io/0.13/dev/git-commit-msg.html):
+For Git commit messages, we follow the [Semantic Commit Messages](https://karma-runner.github.io/0.13/dev/git-commit-msg.html):
 
 ```
 fix(helm): add --foo flag to 'helm install'
@@ -201,7 +201,7 @@ Common scopes:
 Read more:
 - The [Deis Guidelines](https://github.com/deis/workflow/blob/master/src/contributing/submitting-a-pull-request.md)
   were the inspiration for this section.
-- Karma Runner [defines](http://karma-runner.github.io/0.13/dev/git-commit-msg.html) the semantic commit message idea.
+- Karma Runner [defines](https://karma-runner.github.io/0.13/dev/git-commit-msg.html) the semantic commit message idea.
 
 ### Go Conventions
 

docs/glossary.md

@@ -37,7 +37,7 @@ are bundled with it.
 ## Chart Version
 
 Charts are versioned according to the [SemVer 2
-spec](http://semver.org). A version number is required on every chart.
+spec](https://semver.org). A version number is required on every chart.
 
 ## Chart.yaml
 

docs/history.md

@@ -12,7 +12,7 @@ Differences from Helm Classic:
 - Helm's chart format has changed for the better:
   - Dependencies are immutable and stored inside of a chart's `charts/`
     directory.
-  - Charts are strongly versioned using [SemVer 2](http://semver.org/spec/v2.0.0.html)
+  - Charts are strongly versioned using [SemVer 2](https://semver.org/spec/v2.0.0.html)
   - Charts can be loaded from directories or from chart archive files
   - Helm supports Go templates without requiring you to run `generate`
     or `template` commands.

docs/provenance.md

@@ -180,7 +180,7 @@ The following pieces of provenance data are added:
 * The signature (SHA256, just like Docker) of the chart package (the .tgz file)
   is included, and may be used to verify the integrity of the chart package.
 * The entire body is signed using the algorithm used by PGP (see
-  [http://keybase.io] for an emerging way of making crypto signing and
+  [https://keybase.io] for an emerging way of making crypto signing and
   verification easy).
 
 The combination of this gives users the following assurances:
@@ -202,7 +202,7 @@ keywords:
   - proxy
 source:
 - https://github.com/foo/bar
-home: http://nginx.com
+home: https://nginx.com
 
 ...
 files:
@@ -221,7 +221,7 @@ first is the Chart.yaml. The second is the checksums, a map of filenames to
 SHA-256 digests (value shown is fake/truncated)
 
 The signature block is a standard PGP signature, which provides [tamper
-resistance](http://www.rossde.com/PGP/pgp_signatures.html).
+resistance](https://www.rossde.com/PGP/pgp_signatures.html).
 
 ## Chart Repositories
 

docs/related.md

@@ -8,9 +8,9 @@ or [pull request](https://github.com/helm/helm/pulls).
 ## Article, Blogs, How-Tos, and Extra Documentation
 
 - [Awesome Helm](https://github.com/cdwv/awesome-helm) - List of awesome Helm resources
-- [CI/CD with Kubernetes, Helm & Wercker ](http://www.slideshare.net/Diacode/cicd-with-kubernetes-helm-wercker-madscalability)
+- [CI/CD with Kubernetes, Helm & Wercker ](https://www.slideshare.net/Diacode/cicd-with-kubernetes-helm-wercker-madscalability)
 - [Creating a Helm Plugin in 3 Steps](http://technosophos.com/2017/03/21/creating-a-helm-plugin.html)
-- [Deploying Kubernetes Applications with Helm](http://cloudacademy.com/blog/deploying-kubernetes-applications-with-helm/)
+- [Deploying Kubernetes Applications with Helm](https://cloudacademy.com/blog/deploying-kubernetes-applications-with-helm/)
 - [GitLab, Consumer Driven Contracts, Helm and Kubernetes](https://medium.com/@enxebre/gitlab-consumer-driven-contracts-helm-and-kubernetes-b7235a60a1cb#.xwp1y4tgi)
 - [Honestbee's Helm Chart Conventions](https://gist.github.com/so0k/f927a4b60003cedd101a0911757c605a)
 - [Releasing backward-incompatible changes: Kubernetes, Jenkins, Prometheus Operator, Helm and Traefik](https://medium.com/@enxebre/releasing-backward-incompatible-changes-kubernetes-jenkins-plugin-prometheus-operator-helm-self-6263ca61a1b1#.e0c7elxhq)
@@ -90,7 +90,7 @@ Tools layered on top of Helm or Tiller.
 Platforms, distributions, and services that include Helm support.
 
 - [Fabric8](https://fabric8.io) - Integrated development platform for Kubernetes
-- [Jenkins X](http://jenkins-x.io/) - open source automated CI/CD for Kubernetes which uses Helm for [promoting](http://jenkins-x.io/about/features/#promotion) applications through [environments via GitOps](http://jenkins-x.io/about/features/#environments)
+- [Jenkins X](https://jenkins-x.io/) - open source automated CI/CD for Kubernetes which uses Helm for [promoting](https://jenkins-x.io/about/features/#promotion) applications through [environments via GitOps](https://jenkins-x.io/about/features/#environments)
 - [Kubernetic](https://kubernetic.com/) - Kubernetes Desktop Client
 - [Qstack](https://qstack.com)
 

docs/release_checklist.md

@@ -41,7 +41,7 @@ Just kidding! :trollface:
 
 All releases will be of the form vX.Y.Z where X is the major version number, Y
 is the minor version number and Z is the patch release number. This project
-strictly follows [semantic versioning](http://semver.org/) so following this
+strictly follows [semantic versioning](https://semver.org/) so following this
 step is critical.
 
 It is important to note that this document assumes that the git remote in your

docs/using_helm.md

@@ -17,7 +17,7 @@ cluster. Think of it like the Kubernetes equivalent of a Homebrew formula,
 an Apt dpkg, or a Yum RPM file.
 
 A *Repository* is the place where charts can be collected and shared.
-It's like Perl's [CPAN archive](http://www.cpan.org) or the
+It's like Perl's [CPAN archive](https://www.cpan.org) or the
 [Fedora Package Database](https://admin.fedoraproject.org/pkgdb/), but for
 Kubernetes packages.
 
@@ -190,7 +190,7 @@ imageTag: 10.1.14-r3
 
 ## Specify a imagePullPolicy
 ## Default to 'Always' if imageTag is 'latest', else set to 'IfNotPresent'
-## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
+## ref: https://kubernetes.io/docs/user-guide/images/#pre-pulling-images
 ##
 # imagePullPolicy: