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
Not sure why cloning repository is failing after bootstrapping. This is the error that I am seeing when trying to reconcile manually. My staging cluster is still able to clone the repo and is using the same deploy key as dev.
This is the error that I am seeing on the flux-controller. Can anyone help with where I should look? It doesn't seem to be an auth issue from what I can tell.
Components
flux version 0.17.1
app.kubernetes.io/version: v0.14.2 to v0.17.1
controller-gen.kubebuilder.io/version: v0.4.1 to v0.5.0
helm-controller:v0.10.1 to v0.11.2
kustomize-controller:v0.12.2 to v0.14.1
notification-controller:v0.14.1 to v0.16.0
source-controller:v0.13.2 to v0.15.4
EDITED: I tested by rolling back the source controller back to v0.13.2 and that works.. Then I bumped it to v0.14.0 and ran into the same error above (context deadline exceeded). Seems like something broke here for me. Maybe related to this change? #372
The text was updated successfully, but these errors were encountered:
Yeah that seems to work if I set it in the spec. @stefanprodan, weird I was suspecting that was the issue. I forgot to mention that I ran flux reconcile git source bpham-firespotter --timeout 10m with no luck so I didn't try putting it in the spec.
Not sure why cloning repository is failing after bootstrapping. This is the error that I am seeing when trying to reconcile manually. My staging cluster is still able to clone the repo and is using the same deploy key as dev.
This is the error that I am seeing on the flux-controller. Can anyone help with where I should look? It doesn't seem to be an auth issue from what I can tell.
Components
flux version 0.17.1
app.kubernetes.io/version: v0.14.2 to v0.17.1
controller-gen.kubebuilder.io/version: v0.4.1 to v0.5.0
helm-controller:v0.10.1 to v0.11.2
kustomize-controller:v0.12.2 to v0.14.1
notification-controller:v0.14.1 to v0.16.0
source-controller:v0.13.2 to v0.15.4
EDITED: I tested by rolling back the source controller back to v0.13.2 and that works.. Then I bumped it to v0.14.0 and ran into the same error above (context deadline exceeded). Seems like something broke here for me. Maybe related to this change? #372
The text was updated successfully, but these errors were encountered: