Skip to content

Workaround for invalid upstream k8s API#167

Merged
kluevandrew merged 1 commit into
masterfrom
165-workaround-for-k8s-26
Dec 26, 2022
Merged

Workaround for invalid upstream k8s API#167
kluevandrew merged 1 commit into
masterfrom
165-workaround-for-k8s-26

Conversation

@kluevandrew
Copy link
Copy Markdown
Contributor

All Submissions:

  • Have you opened an Issue before filing this PR?
  • Is linter passing?
  • Are the tests passing?
  • Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).

Closes #165

@kluevandrew kluevandrew merged commit ee047eb into master Dec 26, 2022
@kluevandrew kluevandrew deleted the 165-workaround-for-k8s-26 branch December 26, 2022 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The upstream k8s API is invalid

1 participant