Skip to content
This repository has been archived by the owner on Feb 10, 2022. It is now read-only.

Allow operators to control feature gates #201

Merged
merged 3 commits into from
Apr 30, 2018

Conversation

bsnchan
Copy link
Contributor

@bsnchan bsnchan commented Apr 27, 2018

bsnchan and others added 2 commits April 27, 2018 15:34
Signed-off-by: Dave Protasowski <dprotaso@gmail.com>
@cfdreddbot
Copy link

Hey bsnchan!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/157161612

The labels on this github issue will be updated when the story is started.

Copy link
Member

@tvs tvs left a comment

Choose a reason for hiding this comment

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

This can be very useful. I suppose it's possible that the operator could use this to disable a feature that defaults to on and that we rely on, but given that there are so many other ways to break the cluster (e.g. configuring wonky certs), I'm not sure that matters.

@bsnchan
Copy link
Contributor Author

bsnchan commented Apr 30, 2018

@glestaris any thoughts about this? Some of the features we wanted to try out are CustomResourceValidation and CustomResourceSubresources.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants