Previous incidents
Carrier TMS new release
Resolved Sep 21 at 05:35am CDT
Carrier TMS new features will be released
Carrier TMS Elasticsearch migration to separate nodes
Resolved Sep 12 at 03:00am CDT
Currently Carrier TMS Elasticsearch shares Kubernetes nodes with other workloads and they have to fight for resources with each other. Also there was an incident when Elasticsearch couldn’t be scheduled on a node because of its big resource requests.
We are going to isolate Elasticsearch by moving it to separate Kubernetes nodes. These nodes will host only Elasticsearch nodes.
Risks are not expected.
Carrier TMS Elasticsearch migration to separate nodes
Resolved Sep 12 at 02:00am CDT
Currently Carrier TMS Elasticsearch shares Kubernetes nodes with other workloads and they have to fight for resources with each other. Also there was an incident when Elasticsearch couldn’t be scheduled on a node because of its big resource requests.
We are going to isolate Elasticsearch by moving it to separate Kubernetes nodes. These nodes will host only Elasticsearch nodes.
Risks are not expected.
Carrier TMS performance optimizations
Resolved Jul 21 at 09:00pm CDT
We'll be doing a routine maintenance work to optimize the Carrier TMS performance. No down time is expected.
Carrier TMS database system upgrade
Resolved Jul 01 at 10:12pm CDT
Maintenance has been finished.
1 previous update