Question & Answer
Question
We found out that some core functionality of the product in the kube-system namespace is deployed as kubernetes deployment. In a case of master down for maintenance then the pods are not rescheduled once the node is back to the cluster. This may hamper the functionality as the pods are not distributed.
Example: Logging deployments : logging-elk-client, logging-elk-logstash, logging-elk-master
Question: Can we have a mechanism for pods affinity ?
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBS6K","label":"IBM Cloud Private"},"Component":"Configuration","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF043","label":"Red Hat"},{"code":"PF040","label":"RedHat OpenShift"},{"code":"PF048","label":"SUSE"},{"code":"PF031","label":"Ubuntu"}],"Version":"ICP 3.1.2","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
31 May 2019
UID
ibm10886321