Dimitri Koshkin
Dimitri Koshkin
Thank you for the quick response! That makes sense to me.
Thanks for opening the issue. Will work on this once Pod Priority is out of Alpha. The deprecation of the re-scheduler seemed premature at 1.10 before really having an alternative.
We are hesitant to include any experimental features as they are difficult to remove/modify when things change in the future. However you are able to configure this now with some...
It would be great to keep this open to include this in a later release when it becomes more stable.
This can be installed post installation and as off `v1.9.2` the DNS replicas can be specified in the plan file. https://github.com/apprenda/kismatic/pull/1172
I would recommend upgrading one minor version at a time as that is what we test. since you now have a `v1.9` cluster with all the services upgraded to use...
@bobclarke are you able to share an example of what the changes being reported, all tasks are idempotent and nothing will be modified if you rerun `kismatic install apply` (assuming...
I think a better solution would be to run the tests in a new ns and clean up the whole ns after a test.
@emmetthitz were there any workarounds or is there just no way to remove a specific resource?
@swade1987 The motivation here is that a user might want to drain a node, delete it from the cluster and then choose a specific node to delete.