Conversation
| deployment when unlocking a Terraform plan. Otherwise, the deployment’s | ||
| integrity can be compromised. | ||
|
|
||
| Docker registry timeouts |
There was a problem hiding this comment.
I don't think inspecting the cluster is the right place for such workarounds.
ahmad-can
force-pushed
the
OPEN-3450-bootstrap-image-registry
branch
3 times, most recently
from
61303e4 to
d1191e4
Compare
…guration Signed-off-by: Ahmad Hassan <ahmad.hassan@canonical.com>
ahmad-can
force-pushed
the
OPEN-3450-bootstrap-image-registry
branch
from
d1191e4 to
f9694f7
Compare
|
@gboutry please review so i can merge. |
|
@ahmad-can there is still an unresolved comment that's still relevant. |
@gboutry I am not following, please can you clarify a bit? In the resolved comment you mentioned 'It should 100% be documented, and inspecting the cluster is the right place I believe.' which contradicts with the unresolved comment ? |
|
I see why it's not clear. Basically: Inspecting the cluster is the right place to document how to diagnose this issue. How to solve it, is not. I think we should have a more general purpose how-to, about: how to change juju containers registry or something like that, and in inspecting the cluster, we should just link to that page. Because, all in all, this ONE potential solution, not a panacea. There might be other issues at play that would show similar symptoms... |
3 participants
https://warthogs.atlassian.net/browse/OPEN-3450