-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: add chains integration #3660
base: main
Are you sure you want to change the base?
Conversation
/cc @ankitm123 |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
⭐ PR built and available in a preview jenkins-x-jx-docs-pr-3660 here |
|
503592b
to
6f4aa6b
Compare
⭐ PR built and available in a preview jenkins-x-jx-docs-pr-3660 here |
6f4aa6b
to
bbf1819
Compare
/test preview |
⭐ PR built and available in a preview jenkins-x-jx-docs-pr-3660 here |
Signed-off-by: osamamagdy <[email protected]>
bbf1819
to
01f3ca6
Compare
Kudos, SonarCloud Quality Gate passed! |
⭐ PR built and available in a preview jenkins-x-jx-docs-pr-3660 here |
/hold |
- path: helmfiles/tekton-chains/helmfile.yaml | ||
``` | ||
|
||
3. Add this line to the `./helmfile.yaml` of the cluster repo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
point 2 and 3 look very similar to me
url: https://chainguard-dev.github.io/tekton-helm-charts/ | ||
releases: | ||
- chart: tekton/tekton-chains | ||
version: 0.2.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the version come from versionstream?
|
||
5. Create a `./helmfiles/tekton-chains/jx-values.yaml` to include additional configurations to suit your use. | ||
|
||
6. As a final step you need to generate your own encrypted x509 keypair and save it as a Kubernetes secret, install [cosign](https://github.com/sigstore/cosign) and run the following: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Save in jx namespace?
No description provided.