Skip to content
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.

Sign up for GitHub

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

Jump to bottom

change: remove k8s_deployment_info #3098

Merged
merged 1 commit into from
Dec 22, 2020
Merged

change: remove k8s_deployment_info #3098

merged 1 commit into from
Dec 22, 2020

Conversation

spacewander
Copy link
Member

Fix #3068

Signed-off-by: spacewander spacewanderlzx@gmail.com

What this PR does / why we need it:

Pre-submission checklist:

  • Did you explain what problem does this PR solve? Or what new features have been added?
  • Have you added corresponding test cases?
  • Have you modified the corresponding document?
  • Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

@spacewander
change: remove k8s_deployment_info
578092b 
Fix apache#3068

Signed-off-by: spacewander <spacewanderlzx@gmail.com>
@spacewander spacewander marked this pull request as ready for review December 22, 2020 05:11
@membphis membphis merged commit 560a2fe into apache:master Dec 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@membphis membphis membphis approved these changes

@nic-chen nic-chen nic-chen approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[DISCUSS] Do we need to keep k8s_deployment_info in Upstream?
3 participants
@spacewander @membphis @nic-chen