Berndt Jung
Berndt Jung
This needs attention
This is just to support a docker compatible repository, not harbor specifically
Should we move to the Kong ingress controller at this time?
Could we use the k8s readiness check for this? Though, I feel like it would be hard to relay the failure back to the user. We could introduce a "status"...
This needs to be discussed further. It is a very large and potentially difficult change.
Returning a not found/404 on exec I think is the real issue here. We should return an error indicating the function exists, but is not in a READY state yet....
These errors shouldn't be coming from the default backend are they?
This occurs when a user is not logged in and tries to use the dispatch cli ``` $ dispatch get images received unexpected error: &{0 } (*models.Error) is not supported...
This is going to be tough... as we are just printing out helm output. We could try and ensure all credentials are stored as secrets and not passed in through...
A stop-gap could be that the invocation data has a TTL and that it is expired in order to address unbounded growth