Open andy812 opened 3 years ago
Tested with same ism_template's index_patterns. Create kube-system-events-timestamp
index and see it's being managed.
One thing I suspect is when do you create kube-system-events-timestamp
? If it's created before ism_template is there, it won't be auto managed.
I use opendistro with index management plugin v1.13.2.0. My index policy contains such ism_template:
I have no problems with indices prod-service1-timestamp, prod-service2-timestamp, dev-service1-timestamp, etc. But policy do nothing with indices kube-system-events-timestamp, default-events-timestamp, etc.
How to fix it?