-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Add "podman kube play" cmd #14772
Add "podman kube play" cmd #14772
Conversation
@vrothberg PTAL |
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.
@mheon, I would like this PR to get in after we branched for 4.2. Do you know when we're going to branch? |
FWIW I find adding a |
I think you are late to the game. @nicrowe00 is working on it for a number of weeks now and mentioned it in the meetings. What I don't like about scattering kube-things over different commands is that it's impossible to explore functionality. I think commands should be structured by objects, not by actions. For instance, there is "play" does not mean anything to me personally but I can guess what may happen behind "kube". |
it seems like we have a enough debate, including me, here to put this on pause and hash this out. might I suggest a cabal or a design doc that we can all review? |
How can this change go unnoticed? Niall has mentioned it in every meeting the past 3 weeks. Let's chat in today's meeting, so we can unblock Niall. Note that there was consensus in #12475 for doing that already and is has been discussed in meetings back then. |
Because you brought this up publicly @vrothberg , I am compelled to respond. I have my hands in more than a couple of things right now including planning for the team. I have also been on PTO. It is actually relatively easy to miss something like this as it is NOT my responsibility to know what everyone on the team is doing; there are other people for that. |
At this point we've had enough people weigh in on both sides that consensus seems unlikely. I'm OK to proceed with this PR given that - we've discussed the point a lot already and could not come to an agreement. The commands are aliased, which seems like the best compromise we can make. |
Lets talk at Cabal. |
Since you're on PTO. Which Cabal are you referring to? I am pressing since I would ask Niall to work on something else if we need a longer period of time to iron things out. |
Ill be working on Thursday. |
Thanks! Let's chat during Cabal on Thursday then. |
The remote failures are flakes. Rebasing the PR should fix it. |
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.
Just a couple of comments, mostly related to breaking changes.
@rhatdan @baude @umohnani8 PTAL
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.
A lot of unhappy red tests still. |
The "podman kube play" command is designed to be a replacement for the "podman play kube" command. It performs the same function as "play kube" while also still working with the same flags and options. The "podman play kube" command is still functional as an alias of "kube play". Closes #12475 Signed-off-by: Niall Crowe <[email protected]> Signed-off-by: Valentin Rothberg <[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.
LGTM
@rhatdan @baude PTAL
Let's wait for a head nod from @edsantiago as well.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nicrowe00, rhatdan 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 |
The "podman kube play" command is designed to be a replacement for the
"podman play kube" command.
It performs the same function as "play kube" while also still working with the same flags and options.
The "podman play kube" command is still functional as an alias of "kube play".
Closes #12475
Signed-off-by: Niall Crowe [email protected]
Does this PR introduce a user-facing change?