-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Add option to remove Pod name prefix in resulting container name #27302
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
Conversation
Signed-off-by: Oleksandr Krutko <[email protected]>
[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore. |
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.
At first glance, the changes look good. However, tests for the new functionality are missing.
Hello, |
Signed-off-by: Oleksandr Krutko <[email protected]>
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.
I just checked the CI results and pointed out the problematic parts.
I have a nit on documentation, but the code LGTM |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arsenalzp, mheon 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 |
Added a release note |
99d6b3f
to
37928d5
Compare
Signed-off-by: Oleksandr Krutko <[email protected]>
37928d5
to
bb4fa06
Compare
I took into account your remark, it has been just fixed. |
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.
LGTM, Thanks
/lgtm |
This PR is bringing capability to remove Pod name prefix from resulting container name.
Close #26396
If no objections for my solution then I will create test case!
Does this PR introduce a user-facing change?
No