Hide Forgot
Description of problem: After the upgrade from 3.2.1.4 to 3.2.1.13 for a Red Hat customer, any project with a glusterfs endpoint that did not have a corresponding glusterfs service, the endpoint would disappear. This link describes the issue well: https://github.com/openshift/origin/pull/6167 Customer indicates that they did not see this issue in 3.2.1.4 Additional info: Frequently if the service doesn't exist. Creating a service in each project persists the endpoint, which is not ideal since end-users could accidentally delete the service.
I noticed this OpenShift commit between 3.2.1.4 and 3.2.1.13: https://github.com/openshift/ose/commit/1fc581b329820ea74cde33eac9094cfe91fc332e Andy, could it lead to missing endpoints in this case?
Isn't this 'working as designed' and one needs to make a headless service to stop the garbage collector?
I don't see how. It only modifies endpoints under the "kubernetes" service in the "default" namespace.
(In reply to Eric Paris from comment #2) > Isn't this 'working as designed' and one needs to make a headless service to > stop the garbage collector? "Customer indicates that they did not see this issue in 3.2.1.4" I'd expect they will have hard time in 3.3 and 3.4, however we should not break it in a minor release.
We were unable to reproduce this behavior in 3.2 and we believe that anything related to garbage collection of Endpoints has been fixed in 3.3.