Configuring an egress router pod destination list from a config map

    For a large or frequently-changing set of destination mappings, you can use a config map to externally maintain the list. An advantage of this approach is that permission to edit the config map can be delegated to users without cluster-admin privileges. Because the egress router pod requires a privileged container, it is not possible for users without cluster-admin privileges to edit the pod definition directly.

    Prerequisites

    Procedure

    1. Create a file containing the mapping data for the egress router pod, as in the following example:

      You can put blank lines and comments into this file.

    2. Create an egress router pod definition and specify the stanza for the EGRESS_DESTINATION field in the environment stanza:

    Additional resources