David Parker
David Parker
Speaking to the db2u team about this ...
We should do this in the ocp_verify role rather than suite_verify: - https://github.com/ibm-mas/ansible-devops/tree/master/ibm/mas_devops/roles/ocp_verify If we know that unsync'd clocks is an issue, we should treat this as a basic requirement...
For some background … we are publishing immutable tags (obv not technically immutable in the registry; Artifactory instance FWIW), but immutable by process. everything is spat out of a build...
> Tekton really just create the pod and waits for it to be running Maybe I'm misunderstanding something basic :) I would expect to see a pod resource sitting in...
Having implemented a pre-load, this is what we see .. pulling down 200 odd images across all worker nodes there will be a handful that fail the first time with...
Since we added image pre-loading with the daemonsets as above we've not hit this issue again in the last 2 months. I still don't think we should need to perform...
> The proposed enhancement would be for the error message to clearly state which Suite CR needs to be reviewed/fixed before the installation can proceed. Agreed, we should be able...
Our install, upgrade, and update pre checks are designed to prioritize safety/cautious & be extra pessimistic if they see anything unhealthy in the cluster ... If we detect any unhealthy...
Not ready for review, moving to draft state
Closing PR, hasn't been updated in half a year and lots of merge conflicts that need to be resolved, looks abandoned