-
Notifications
You must be signed in to change notification settings - Fork 19
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
Pass default-image-prefix to function runners #151
Conversation
Hi @mozesl-nokia. Thanks for your PR. I'm waiting for a nephio-project member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
/approve |
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.
It seems very complex to achieve even simple things in Porch.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kispaljr, liamfallon, mozesl-nokia The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@mozesl-nokia you will need to sign the CLA before we can merge this PR. |
Just a quick note: we are aware of this constant in the podevaluator: porch/func/internal/podevaluator.go Line 65 in 6d34cf8
I recommended not to touch that in this PR, but handle it in a future, unrelated PR. The rationale behind that is the following: in my understanding that constant is used to determine if special auth parameters and/or a special TLS ca.crt should be used for a registry or not. That means this constant shouldn't be set to the default registry passed as a command line argument, because it can be a private repository. Instead we should allow specifying which custom ca.crt should be used for which registry, but that is out-of-scope of this bugfix. @Catalin-Stratulat-Ericsson could you verify that? |
Yes @kispaljr it is as you described.
|
/lgtm |
The default-image-prefix server argument was not passed along to the KRM function runner previously. This PR is a fix for that.