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

Correctly use custom kubernetes context if specified #451

Merged
merged 1 commit into from
Mar 8, 2022
Merged

Correctly use custom kubernetes context if specified #451

merged 1 commit into from
Mar 8, 2022

Conversation

schustmi
Copy link
Contributor

@schustmi schustmi commented Mar 8, 2022 •
edited
Loading

Describe changes

Correctly use custom kubernetes context if specified

Pre-requisites

Please ensure you have done the following:

  • I have read the CONTRIBUTING.md document.
  • If my change requires a change to docs, I have updated the documentation accordingly.
  • If I have added an integration, I have updated the integrations table.
  • I have added tests to cover my changes.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Other (add details above)

@schustmi schustmi requested a review from htahir1 March 8, 2022 08:55
@github-actions github-actions bot added internal To filter out internal PRs and issues bug Something isn't working labels Mar 8, 2022
@schustmi schustmi merged commit ba2647a into develop Mar 8, 2022
@schustmi schustmi deleted the bugfix/ENG-654-kubeflow-context branch March 8, 2022 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@wjayesh wjayesh wjayesh approved these changes

@htahir1 htahir1 htahir1 approved these changes

Assignees
No one assigned
Labels
bug Something isn't working internal To filter out internal PRs and issues
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@schustmi @htahir1 @wjayesh