-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Remove --release-kind
and --federation
from push-build.sh
#19321
Conversation
The kubernetes_build scenario was referencing two more or less deprecated flags `--release-kind` and `--federation`. Since the scripts to execute those build does not exist any more inside k/k we can safely remove them. Signed-off-by: Sascha Grunert <[email protected]>
/approve |
/assign @spiffxp |
/lgtm |
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.
/hold
I'm OK with this in principle but I'm wary of creating more dead code. Is there an issue or PR covering its removal?
if args.federation: | ||
# TODO: do we need to set these? | ||
env['PROJECT'] = args.federation | ||
env['FEDERATION_PUSH_REPO_BASE'] = 'gcr.io/%s' % args.federation |
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.
https://cs.k8s.io/?q=FEDERATION_PUSH_REPO_BASE&i=nope&files=&repos= - this shows up in kubernetes/release/push-build.sh, is there a PR to remove this?
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.
Not right now. I was working on finishing krel push
as replacement for push-build.sh
(see kubernetes/release#1459), which is now finished. The new implementation does not have both mentioned flags.
I can't remove the script until we did not move all tests using this scenario to kubetest. :-/
'--federation', | ||
help='Push federation images to the specified project') | ||
PARSER.add_argument( | ||
'--release-kind', |
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.
https://cs.k8s.io/?q=release_kind&i=nope&files=&repos= - same deal here
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.
/hold cancel
/approve
Not a fan of dead code but I guess I'm fine pruning the surface area of this scenario (we should be striving to eliminate scenarios anyhow)
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, saschagrunert, spiffxp 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 |
/sig release |
The kubernetes_build scenario was referencing two more or less
deprecated flags
--release-kind
and--federation
. Since the scriptsto execute those build does not exist any more inside k/k we can safely
remove them.
/assign @dims @justaugustus
/cc @kubernetes/release-managers
related to #19328