-
Notifications
You must be signed in to change notification settings - Fork 74
Extended configMap #80
base: master
Are you sure you want to change the base?
Conversation
* implement interface specification for service * implement multiple services on the same IP * configmap key now is [OPTIONAL_INDEX-]IP_ADDRESS[@OPTIONAL_INTERFACE]
@mshaverdo @steven-sheehy I don't like the new format. Right now, using a configmap makes no sense with all the features we are trying to define in a key-value string definition. I think is time to evolve using a no namespaced CRD |
@mshaverdo @steven-sheehy Maybe, it's a good idea to summarize desired features?
|
👍 concur on CRD |
another major comment for this implementation: But so I think the resolution for diff NIC interface is : a global config item in CRD... |
forgive my ignorance. iface can be VIP granularity .
|
In our usecase we met several problems:
To solve this problems, we've extended configmap semantics: configmap key now is
[OPTIONAL_INDEX-]IP_ADDRESS[@OPTIONAL_INTERFACE]
, e.g.:01-10.0.0.1@eth0
or01-10.0.0.1
or10.0.0.1@eth0
or just10.0.0.1
. It allows to specify several services on single IPs and explicitly specify interface name. If interface is not specified in configmap, it uses interface specified via--iface
flagIt fixes #12 and fixes #77