Hide Forgot
In order to provide proper HA support, it's necessary to be able to fence misbehaving Pods, which is currently not possible. The need is to fenc faulty containers, or containers on faulty hosts, so that we can prevent them from creating diverging datasets and/or consume other "jobs". By fencing a pod, all the containers of the pod would be left out of a cluster/network (like pacemaker's fence operations work).
Flavio - can you review https://github.com/kubernetes/kubernetes/pull/34160 and see if this meets your use case/need?
Hi Derek, Absolutely, we'll review and report back. Thanks for the heads up.
As the proposal itself states, it lays much if not all the groundwork for what we need without providing the entity (fencing controller) that would take advantage of it all and make it happen. We'll need both pieces, but this proposal is exactly the direction we would want to see.
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers. Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant. This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.