Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
H
helm3
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
go
helm3
Commits
6e3a0a12
Commit
6e3a0a12
authored
Mar 27, 2018
by
Jonathan Hall
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Remove outdated note.
parent
b2ac6d3d
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
7 deletions
+0
-7
provenance.md
docs/provenance.md
+0
-7
No files found.
docs/provenance.md
View file @
6e3a0a12
...
...
@@ -4,13 +4,6 @@ Helm has provenance tools which help chart users verify the integrity and origin
of a package. Using industry-standard tools based on PKI, GnuPG, and well-respected
package managers, Helm can generate and verify signature files.
**Note:**
Version 2.0.0-alpha.4 introduced a system for verifying the authenticity of charts.
While we do not anticipate that any major changes will be made to the file formats
or provenancing algorithms, this portion of Helm is not considered _frozen_ until
2.
0.0-RC1 is released. The original plan for this feature can be found
[
at issue 983
](
https://github.com/kubernetes/helm/issues/983
)
.
## Overview
Integrity is established by comparing a chart to a provenance record. Provenance
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment