diff --git a/content/day3/01_day-two.md b/content/day3/01_day-two.md index a84d3b0..0bae306 100644 --- a/content/day3/01_day-two.md +++ b/content/day3/01_day-two.md @@ -3,6 +3,7 @@ title: Surviving Day2: Picking the right tool to secure your kubernetes habitat weight: 1 tags: - kubecon + - security --- diff --git a/content/day3/02_open-feature.md b/content/day3/02_open-feature.md new file mode 100644 index 0000000..cd883ae --- /dev/null +++ b/content/day3/02_open-feature.md @@ -0,0 +1,30 @@ +--- +title: "Type-safe feature flagging in openfeature: Lessons learned from using feature flags at google" +weight: 2 +tags: + - kubecon + - dev +--- + + + + +## Featureflags? + +- Idea: Change the behaviour of an application without rebuilding it +- Goal: Control rollout, reduce risk, experiment (a/b) +- At google: A huge number of feature flags (150k+) but that's because people forget to turn them off + +## Where does the flag come from + +- Lifecycle of a flag: Create, Manage, Deprecate, Delete -> But will it be created frist in code or in the service +- Classic implementation: Just a if/else that uses a function to get the flag +- Problem: What if the flag names missmatch between the code and flag ser -> Muliple sources of truth +- Solution: Require use of auto-generated flag bindings (codegen from the management system) to mitigate typos, etc. + +## OpenFeature + +- Goal: Vendor agnostic, standardized, open source +- Basic setup: Register provider (once per app), create a client, use client to get flags +- CLI: Integrate into management system, keep a local manifest of all flags and generate code (generates the client) +- Now: Just call the client's method instead of hard-coding feature flag names diff --git a/content/day3/_index.md b/content/day3/_index.md index b7fed02..6577a55 100644 --- a/content/day3/_index.md +++ b/content/day3/_index.md @@ -7,11 +7,11 @@ weight: 7 The last day of KubeCon - aka the day everone leaves early. But not me and I had no meetings scheduled for this day -> More talks for me and notes for you. -This being my 7th day of the trip and 6th day of non-stop conferences took a bit of a toll on my note taking skills (expect more spelling mistakes) +This being my 7th day of the trip and 6th day of non-stop conferences took a bit of a toll on my note taking skills (expect more spelling mistakes). ## Talk recommendations -- TODO: +- Intro to feature flags and related tips: [Type-safe feature flagging in openfeature: Lessons learned from using feature flags at google](../02_open-feature) ## Other stuff I learned or people i talk to