You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to be able to specify the priority class for this deployment.
In the case where nexus is working as a Docker proxy, its possible to end up in the situation where Nexus isn't running and k8s tries to first create other pods, which will fail to start as they can't pull from the Nexus Docker Repository.
The easy solution is to give Nexus a high priority class name so that k8s will schedule it before all other pods and thus ensure they can start properly.
The text was updated successfully, but these errors were encountered:
Hi there,
It would be great to be able to specify the priority class for this deployment.
In the case where nexus is working as a Docker proxy, its possible to end up in the situation where Nexus isn't running and k8s tries to first create other pods, which will fail to start as they can't pull from the Nexus Docker Repository.
The easy solution is to give Nexus a high priority class name so that k8s will schedule it before all other pods and thus ensure they can start properly.
The text was updated successfully, but these errors were encountered: