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

feat(controller): Add security and cost recommendation conditions #4743

Merged
merged 1 commit into from Jan 27, 2021

Conversation

alexec
Copy link
Contributor

@alexec alexec commented Dec 15, 2020

Signed-off-by: Alex Collins alex_collins@intuit.com

Checklist:

image
image

@alexec alexec marked this pull request as ready for review December 15, 2020 19:41
@@ -1,5 +1,54 @@
# Security
Copy link
Member

Choose a reason for hiding this comment

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

Given that this is doc on security from various perspectives, should we add a section on security policy of the project and link to https://github.com/argoproj/argo/blob/master/SECURITY.md?

docs/security.md Show resolved Hide resolved
docs/security.md Show resolved Hide resolved
docs/security.md Show resolved Hide resolved
docs/security.md Show resolved Hide resolved
@alexec alexec changed the title docs: Expand on controller security feat(controller): Add security and cost recommendation conditions Jan 24, 2021
@alexec
Copy link
Contributor Author

alexec commented Jan 26, 2021

@simster7 what do you think of adding these as conditions?

Copy link
Member

@terrytangyuan terrytangyuan left a comment

Choose a reason for hiding this comment

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

Looks great! It's a good way for users to find out about related features to reduce security risk and costs.

@simster7
Copy link
Member

@simster7 what do you think of adding these as conditions?

Will take a look momentarily

@jessesuen
Copy link
Member

jessesuen commented Jan 27, 2021

@simster7 what do you think of adding these as conditions?

Honestly, I feel like adding conditions is a step too far, out of the purview of the controller, and will be annoying for anyone who understands what they are doing and has no way of removing these conditions. e.g. they intentionally do not want to use the GC feature because they have their own out-of-band GC mechanism.

@alexec
Copy link
Contributor Author

alexec commented Jan 27, 2021

Honestly, I feel like adding conditions is a step too far, out of the purview of the controller.

Ok. I'll revert these changes. Can I get approval for the docs changes?

@jessesuen

Copy link
Member

@jessesuen jessesuen left a comment

Choose a reason for hiding this comment

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

I pushed my desired doc changes. Conditional approval to remove the conditions which were added.

@jessesuen jessesuen removed their assignment Jan 27, 2021
Signed-off-by: Alex Collins <alex_collins@intuit.com>
@alexec alexec merged commit 727e27a into argoproj:master Jan 27, 2021
@alexec alexec deleted the sec branch January 27, 2021 20:32
@simster7 simster7 mentioned this pull request Feb 1, 2021
32 tasks
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.

None yet

4 participants