Open StasCelium opened 3 years ago
Made it work after configured a notification channel weird..
Can you elaborate how u fixed it?
Coz im facing exactly the same issue
@rusenask pls help :)
@StanislavBerezin I'm really sorry my friend, i didn't see the notification! I just got to setup Mattermost(It may be any notification setup), then everything goes well!
Try to look at your deployment manifest, you will find a section where you have to put credentials and the endpoint for the notification channel of any service, for my case, i used Mattermost, then this message just disappeared. I was like (what?) but didn't try to understand more as it works, but i believe this step was hanging the procedure
Having a very similar problem to this issue https://github.com/keel-hq/keel/issues/546
After following the steps in the answer, i'm still having the same problem. Used keel previously many times and never had problems of this sort, not sure what is happening.
The error:
I have installed via helm by typing
helm upgrade --install keel --namespace=kube-system keel/keel --set googleApplicationCredentials=$(cat ./secret.json | base64) --set gcr.enabled=true --set gcr.projectId=PROJECT_ID
In my deployment file I have
I have also made sure that the service account does have the right premissions by doing
It did authenticate, and allowed me to push and pull images.
But still not working on k8s
EDIT: Whenever I
kubectl apply -f mydeploy.yaml
it seems to work fine, but whenever it needs to update an image, it just throws those errorsEDIT2: