Installation method:
Kubernetes version: 1.16.0
Dashboard version: 1.10.1
Operating system: ubuntu:bionic
Node.js version ('node --version' output):
Go version ('go version' output):
This report is more of a notification to everybody that dashboard v1.10.1 still uses the apps/v1beta2 API group, while it was deprecated and is disabled by default in the kubernetes 1.16
I am not sure what do you expect from us. For notifications you can post message on sig-ui slack.
/close
@floreks: Closing this issue.
In response to this:
I am not sure what do you expect from us. For notifications you can post message on sig-ui slack.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@floreks an official resolution: whether it is a genuine bug or wontfix
v2 is not ready for production, and v1 is broken for the current stable kubernetes 馃し鈥嶁檪
That's what issue template is for and this one section with 'Expected result'. We won't update v1. We will update v2 for sure this week.
@floreks right, indeed that's my fault then, sorry and thanks.
@floreks
We will update v2 for sure this week.
Sorry, can we get any update on the update please? The front page of the github repo still says v1 and the kubernetes doco still says alpha.
@andrewsav-datacom https://github.com/kubernetes/dashboard/releases - here you will find current releases.
Thank you for that. I was enquiring about "v2 update this week" that was mentioned 8 days ago. I'd like to get update on it's status if possible.
I think we can push a new beta today, right @floreks?
Ye, we can do that, if we fix v1.16 compatibility issues :slightly_smiling_face:
@floreks thank you for this, is there a place where these issues can be tracked? The only one I could find (besides this one) is https://github.com/kubernetes/dashboard/issues/4327 which is also closed. Many thanks!
https://github.com/kubernetes/dashboard/pull/4377 PR will fix compatibility issues. Then we can do the release.
@floreks looks like it has been merged!
Yep, we will do the release soon.