description

there are a number of issues with the docs that make initial configuration of Envoy somewhat difficult to understand

• its not immediately clear to new users the migration from config -> typed_config
• there doesnt seem to be an authoritative list of well-known extensions/docs
• its not easy to figure out which keys/configs need to change migrating v2 -> v3 typed_configs

some of the confusion seems to be due to docs not being updated (see https://stackoverflow.com/questions/63473416/envoy-configuration-possible-values-of-type-keys). This problem is slowly being addressed (#13503 #13529 )

it may also be a lack of knowledge on my part - but it feels like this is quite a steep learning curve, and google searches dont always provide easy answers to problems like config migration - mostly i have to test to confirm that i have changed the right things.

refs

• https://stackoverflow.com/questions/63473416/envoy-configuration-possible-values-of-type-keys
• examples: Fix deprecations/warnings in configs #13503 examples: Fix more deprecations/warnings in configs #13529
• docs: automate listing all stock/built-in types for typed extensions #13167