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

Introduce feature flags machinery #2543

Closed
jpeach opened this issue May 20, 2020 · 3 comments
Closed

Introduce feature flags machinery #2543

jpeach opened this issue May 20, 2020 · 3 comments
Labels
area/deployment Issues or PRs related to deployment tooling or infrastructure. blocked/needs-design Categorizes the issue or PR as blocked because it needs a design document. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jpeach
Copy link
Contributor

jpeach commented May 20, 2020

Please describe the problem you have

As we introduce more features and tuning knobs into Contour, we increase the probability of some behavior being desirable in one cluster but harmful in another. We also increase the probability of needing to ship experimental features that can be disabled in configuration.

So we should think about and discuss a feature flagging mechanism in Contour - how it would work, what kinds of application we think it might have, and how it interacts with our compatibility commitments.

@jpeach jpeach added area/deployment Issues or PRs related to deployment tooling or infrastructure. kind/feature Categorizes issue or PR as related to a new feature. blocked/needs-design Categorizes the issue or PR as blocked because it needs a design document. labels May 20, 2020
@xaleeks
Copy link

xaleeks commented Mar 2, 2021

Are you referring to functionality like feature gate like in k8s, so you can enable or disable them with command line flags and query for supported versions and EOL info.

@youngnick
Copy link
Member

I think that covers what we're talking about, yes.

@sunjayBhatia
Copy link
Member

closing, I think we're too far along at this point to start this machinery, but can reopen if it comes up again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/deployment Issues or PRs related to deployment tooling or infrastructure. blocked/needs-design Categorizes the issue or PR as blocked because it needs a design document. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants