Properly resolve imagePullSecrets from app and deploymentID if relevant property does not exist #7403
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On TriggerSchedulerRun (k3s scheduler) the existing configuration only checks for image-pull-secrets scheduler-k3s property on the app. For a case of a private registry/repo, this means that the authentication configured by
dokku registry:loginis not available, so the pod cannot fetch the image. Unless you set the image-pull-secrets manually.The pull secrets resolution is properly configured on
func TriggerSchedulerDeploy. Not sure if it would be a better solution to update the scheduler property on each deploy instead of re-constructing a string here though; haven't dug deeper to check all use-cases. Thoughts?