OpenShift automatically prunes images off nodes and has done so since at
least 3.4. Please see
https://docs.okd.io/latest/admin_guide/garbage_collection.html
On Tue, Sep 25, 2018 at 12:32 PM Tim Dudgeon wrote:
> As time progresses more and more docker images will be present on the
> nodes in a
As time progresses more and more docker images will be present on the
nodes in a cluster as different pods get deployed.
This could use up significant disk space.
Does openshift provide a mechanism for pruning these, or is doing this
up to the cluster administrator?
On Sep 25, 2018, at 6:22 AM, Joel Pearson
wrote:
Clayton, does this mean that in OpenShift 4.0 you'd be able to take a
vanilla kubernetes installation and then install a bunch of OpenShift
operators and basically have an OpenShift cluster?
It’s not really the goal, since there are still
Clayton, does this mean that in OpenShift 4.0 you'd be able to take a
vanilla kubernetes installation and then install a bunch of OpenShift
operators and basically have an OpenShift cluster? Or is that not really
the goal of migration to operators? Is it just to make future OpenShift
releases
It looks like not, I found some references saying that Kubernetes has alpha
support in 1.9 and some improvements in 1.10
https://github.com/kubernetes/kubernetes/issues/1443
https://github.com/kubernetes/kubernetes/issues/62822
I did find this article suggesting that you might be able to use
