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

Add ability to disable namespace opt-in #268

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

slimm609
Copy link
Contributor

Description of the change

  • add the ability to disable opt-in support for namespace validation and enforce across the entire cluster
  • add helm-docs template to allow helm-docs to generate the README automatically.

Existing or Associated Issue(s)

sigstore/policy-controller#66

Additional Information

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

@slimm609 slimm609 force-pushed the namespace_optIn_flag branch 3 times, most recently from f4c66ce to c616289 Compare August 18, 2022 19:57
@cpanato cpanato requested a review from hectorj2f August 19, 2022 06:46
charts/policy-controller/Chart.yaml Outdated Show resolved Hide resolved
JAORMX
JAORMX previously approved these changes Aug 22, 2022
@hectorj2f
Copy link
Contributor

@slimm609 Sorry, could you rebase these changes again ? I think this PR got lost somehow. Happy to help you to get it in.

- add the ability to disable opt-in support for namespace validation
and enforce on across the entire cluster

Signed-off-by: slimm609 <dbrian@vmware.com>
Signed-off-by: slimm609 <dbrian@vmware.com>
Signed-off-by: slimm609 <dbrian@vmware.com>
@slimm609
Copy link
Contributor Author

@hectorj2f rebased

@@ -0,0 +1,115 @@
{{ template "chart.header" . }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q: Why do we need this file ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't have to do helm-docs --dry-run then modify the README.md each time. Instead you run helm-docs and it generates the entire file for you.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also makes it easy to validate because if helm-docs generates a diff, then you know it wasn't properly updated.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sgtm, what do you think @cpanato ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned, let's revert this change and keep only the opt-in functionality.

Signed-off-by: slimm609 <dbrian@vmware.com>
Signed-off-by: slimm609 <dbrian@vmware.com>
@hectorj2f
Copy link
Contributor

@slimm609 Could we remove the helm docs addition as part of this PR? We want to evaluate it's benefits in a separate PR.

## More info

You can find more information about the policy-controller in [here](https://docs.sigstore.dev/policy-controller/overview/).

----------------------------------------------
Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's move this change to a separate PR, so we can address the issue itself.

@shani-e
Copy link

shani-e commented Feb 6, 2023

@hectorj2f @slimm609 Any chance to promote it? 🥺

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.

5 participants