You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2022. It is now read-only.
currently there is feature to define custom hostannotation https://github.com/ElisaOyj/openshift-lb-controller/blob/master/pkg/controller/controller.go#L39 However, this is not good thing if you have two separate lb-controllers in same openshift cluster. Lets say that we have two different lb-controllers, first one is taking care of external.company.com and second one internal.company.com. Now if we have this custom hostannotation defined in both, the lb-controller does not know where to expose this custom host. Currently it will expose that to both, and it is security issue if used like this.
The text was updated successfully, but these errors were encountered:
zetaab
changed the title
possibility to disable using customhostannotation
possibility to disable using custom hostannotation
Sep 21, 2018
currently there is feature to define custom hostannotation https://github.com/ElisaOyj/openshift-lb-controller/blob/master/pkg/controller/controller.go#L39 However, this is not good thing if you have two separate lb-controllers in same openshift cluster. Lets say that we have two different lb-controllers, first one is taking care of
external.company.com
and second oneinternal.company.com
. Now if we have this custom hostannotation defined in both, the lb-controller does not know where to expose this custom host. Currently it will expose that to both, and it is security issue if used like this.The text was updated successfully, but these errors were encountered: