BGP md5 authentication about meridio HOT 1 CLOSED

• Extend Gateway in NSP API and in configmap model with BGP Authentication consisting of a key name and key source fields.
  Source would refer to a Secret that contains the key by name.
  Store newly introduced BGP auth information along with the rest of the Gateway config in Frontend.
• Modify Frontend to watch referenced Secret(s) and lookup the key value i.e. password by name. Then write BGP config accordingly.
  NSP used to be the single source of configuration from Gateways' point of view. Which shall change with the introduction of Secrets acting as source of authentication data. Thus, change in Secrets of interest shall trigger re-configuration (the intention is to keep the password separated from related Gateway config and avoid storing too much state information).
• The implementation must support update of key values in Secret(s).
  Also, if a key or a Secret referenced by a Gateway is removed, the affected Gateway shall be removed from the active BIRD configuration.
• Update Operator (Gateway CRD, validation, configmap writer, service account/role/role-binding to watch Secrets)
• Check if the owner/group and privileges of the BIRD config file should be changed (currently root:fsGroup and 644)
  Update: we should not care about that

from meridio.