Bug: list of Deployments not shown in UI#88
Open
eugene-marchanka wants to merge 3 commits intopixel-point:masterfrom
Open
Bug: list of Deployments not shown in UI#88eugene-marchanka wants to merge 3 commits intopixel-point:masterfrom
eugene-marchanka wants to merge 3 commits intopixel-point:masterfrom
Conversation
Author
|
@proAlexandr Could you, please, take a look? |
bump version, update @kubernetes/client-node package
Member
|
Thanks @eugene-marchanka for your PR, I will try to check it soon and merge it! |
Author
|
Hey! |
|
@lnikell please review this PR, thanks |
|
Hello, i fixed all the build problems in windows with node 14.20 and fixed all the problems related to the deployments. You guys can build it from my fork: https://github.com/robertohein/kube-forwarder |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The reason is App is trying to pull Deployment resources from
V1beta1Apiinstead of aCoreThis PR should fix this issue