Skip to content
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

tuf: Support deployment resources customization #869

Merged

Conversation

sfox-equinix
Copy link
Contributor

Description of the change

This pull request adds support for customizing the following values in the tuf Deployment resource:

  • Container resources
  • Container security context
  • Deployment security context

Existing or Associated Issue(s)

This work was originally implemented in pull request #460 which is unmerged. This current pull request supersedes Vipul's work.

Additional Information

I think I modified the values.schema.json correctly?

Checklist

  • Chart version bumped in Chart.yaml according to semver. Where applicable, update and bump the versions in any associated umbrella chart
  • Variables are documented in the values.yaml and added to the README.md. The helm-docs utility can be used to generate the necessary content. Use helm-docs --dry-run to preview the content.
  • JSON Schema generated.
  • List tests pass for Chart using the Chart Testing tool and the ct lint command.

bobcallaway
bobcallaway previously approved these changes Nov 22, 2024
This commit adds support for customizing the following values in
the tuf deployment:

- Container resources
- Container security context
- Deployment security context

Signed-off-by: Stephen Fox <sfoxjr@equinix.com>
@sfox-equinix sfox-equinix force-pushed the customize-tuf-deployment-resources branch from c3ccc27 to 1ef3fc4 Compare November 23, 2024 00:05
@bobcallaway bobcallaway merged commit 57e62b9 into sigstore:main Nov 23, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants