-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jlo/fix-relay-restarts #15
Conversation
Signed-off-by: Javier Lopez <[email protected]>
Signed-off-by: Javier Lopez <[email protected]>
Signed-off-by: Javier Lopez <[email protected]>
supervisor: | ||
context: . | ||
image: ${REGISTRY_AND_USER:-okteto}/supervisor:${VERSION:-latest} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what do you think if we use some more conventional env vars?
If we use OKTETO_NAMESPACE
instead of USER it's replaced out of the box. For the Registry, unfortunatelty it's only injected in the deploy steps, but still we could have a comment as example.
image: ${REGISTRY_AND_USER:-okteto}/supervisor:${VERSION:-latest} | |
image: ${OKTETO_REGISTRY_URL}/${OKTETO_NAMESPACE}/supervisor:${VERSION:-latest} | |
# Example: OKTETO_REGISTRY_URL=registry.product.okteto.dev okteto build` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With that approach it's difficult to know that you can push to other registries rather than the okteto one, like docker hub.
Signed-off-by: Javier Lopez <[email protected]>
Signed-off-by: Javier Lopez [email protected]
Fixes #DEV-395
Proposed changes