cloud-native-toolkit / cloud-native-toolkit/planning

Augment CD with Feature Flags

Open
#459 0 comments 0 reactions 0 assignees View on GitHub
enhancement pipeline
Dominant language
No language data
Stars
4
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Let's enhance the CD pipeline with not only GitOps but also [Feature Flags](https://www.martinfowler.com/articles/feature-toggles.html). This will enable more custom control over the SDLC stages such that two stages that use equivalent environments can share an environment rather than redeploy.

Feature Flags enable engineering to separate code deployment from feature rollout. For example, a team can use [LaunchDarkly](https://launchdarkly.com/features/feature-flags/) to deploy new features to production but hide them so that no one can use them, then make them available in stages to additional groups until everyone has access. This can replace or augment a separate staging environment and be used to perform A/B testing, canary testing, and blue/green deployment. Stages in the SDLC don't necessarily have to be separate deployment environments (namespaces, clusters, etc.), but in some cases can be code deployed in the same environment that is exposed for use by different stages.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.