-
Notifications
You must be signed in to change notification settings - Fork 18
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
Function support for private registry in RuntimeImageOverride #309
Comments
Its possible to read a user defined secret and inject it into filesystem of kaniko's build container spec:
runtime: ...
runtimeImageOverride: ...
runtimeImageOverridePullSecret: #reference to secret of type `dockerconfigjson` In such case kaniko's |
This issue or PR has been automatically marked as stale due to the lack of recent activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /lifecycle stale |
This issue or PR has been automatically closed due to the lack of activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /close |
@kyma-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Description
As a function runtime developer, I want to provide my own custom runtime image from a private registry so that I can have security and privacy into enterprise images.
Reasons
We have an internal custom runtime image that we don't want it to be publicly exposed. We want to run our custom runtime image in BTP Kyma where we shouldn't change its internal modules configurations.
Attachments
In our local Kyma setup with k3d, we append to the default kaniko arguments the k3d insecure registry available within the cluster:
--insecure-registry=k3d-kyma-registry:5000
. During function image build, kaniko can access and pull the custom runtime.In BTP Kyma, changes to the serverless deployment are overwritten after some period of time, and we would need to push the custom runtime image to its internal registry so that it can access the image privately.
Error when trying to use a private repository from docker.io:
The text was updated successfully, but these errors were encountered: