Martin Pitt
2018-09-14 15:00:10 UTC
Hello all,
Cockpit's "Kubernetes" package has provided a web UI for managing
Kubernetes/OpenShift deployments for a long time. In the last year it also got
some initial support for showing KubeVirt[1] VMs that run in OpenShift.
Since Red Hat's acquiring of CoreOS there are now *three* web UIs: OpenShift's
own "OpenShift Console", Tectonic, and Cockpit's "Cluster" dashboard. The first
two are meant to become one at some point [2] and currently see a lot of
development; i. e. Console/Tectonic/Quay will be *the* web UI for OpenShift
(including KubeVirt) soon. On the other hand, cockpit-kubernetes has been in
maintenance mode for a fair while now - both because of that merging effort,
and also because we haven't had (and still don't have) any development capacity
for it in the Cockpit team. It's also rather hard to maintain, being written in
a very old Angular version.
So long-term cockpit-kubernetes will go away. As a strawman I would propose to
still keep it in Fedora 29 (as it's past beta freeze already), but drop it from
Rawhide. Thus there will still be a supported cockpit-kubernetes package for
~ 1.5 more years.
cockpit-kubernetes also contains some support for KubeVirt. Apparently
community interest has waned on that, and we actually haven't been able to
build a recent kubevirt-enabled OpenShift image in four months -- [3] were the
last attempts at fixing it. Thus we had to kick out kubevirt testing from
the openshift image [4], and we'll have to kick it off the openshift-prerelease
image as well if we need to rebuild it at some point. Once this happens, there
is no way how we can further support the KubeVirt bits in cockpit-kubernetes,
so I'd actually like to remove this from Fedora 29 already, in its current
condition.
Is there any interest from anyone to continue to maintain it? If so, then the
best course of action would be to split it off into a separate
cockpit-kubernetes upstream project, like we recently did with cockpit-ostree [5],
and maintain it there (by a different group of people than the Cockpit core
team). Of course we will gladly help you to set this up.
Thanks,
Martin
[1] http://kubevirt.io/
[2] https://www.redhat.com/en/about/press-releases/red-hat-unveils-roadmap-coreos-integration-red-hat-openshift
[3] https://github.com/cockpit-project/cockpit/issues/9479 and https://github.com/cockpit-project/cockpit/pull/9638
[4] https://github.com/cockpit-project/cockpit/commit/2795ceb8ee13
[5] https://github.com/cockpit-project/cockpit-ostree
Cockpit's "Kubernetes" package has provided a web UI for managing
Kubernetes/OpenShift deployments for a long time. In the last year it also got
some initial support for showing KubeVirt[1] VMs that run in OpenShift.
Since Red Hat's acquiring of CoreOS there are now *three* web UIs: OpenShift's
own "OpenShift Console", Tectonic, and Cockpit's "Cluster" dashboard. The first
two are meant to become one at some point [2] and currently see a lot of
development; i. e. Console/Tectonic/Quay will be *the* web UI for OpenShift
(including KubeVirt) soon. On the other hand, cockpit-kubernetes has been in
maintenance mode for a fair while now - both because of that merging effort,
and also because we haven't had (and still don't have) any development capacity
for it in the Cockpit team. It's also rather hard to maintain, being written in
a very old Angular version.
So long-term cockpit-kubernetes will go away. As a strawman I would propose to
still keep it in Fedora 29 (as it's past beta freeze already), but drop it from
Rawhide. Thus there will still be a supported cockpit-kubernetes package for
~ 1.5 more years.
cockpit-kubernetes also contains some support for KubeVirt. Apparently
community interest has waned on that, and we actually haven't been able to
build a recent kubevirt-enabled OpenShift image in four months -- [3] were the
last attempts at fixing it. Thus we had to kick out kubevirt testing from
the openshift image [4], and we'll have to kick it off the openshift-prerelease
image as well if we need to rebuild it at some point. Once this happens, there
is no way how we can further support the KubeVirt bits in cockpit-kubernetes,
so I'd actually like to remove this from Fedora 29 already, in its current
condition.
Is there any interest from anyone to continue to maintain it? If so, then the
best course of action would be to split it off into a separate
cockpit-kubernetes upstream project, like we recently did with cockpit-ostree [5],
and maintain it there (by a different group of people than the Cockpit core
team). Of course we will gladly help you to set this up.
Thanks,
Martin
[1] http://kubevirt.io/
[2] https://www.redhat.com/en/about/press-releases/red-hat-unveils-roadmap-coreos-integration-red-hat-openshift
[3] https://github.com/cockpit-project/cockpit/issues/9479 and https://github.com/cockpit-project/cockpit/pull/9638
[4] https://github.com/cockpit-project/cockpit/commit/2795ceb8ee13
[5] https://github.com/cockpit-project/cockpit-ostree