Open kaovilai opened 2 years ago
@kaovilai, we are not planning to support Operator Lifecycle Manager (OLM) with MicroShift.
Operators may still be installed if they do not require any OCP APIs unsupported by MicroShift. You should inquire with the OADP team if non-OLM installation is possible/supported.
@ggiguash I am part of the OADP team and we are investigating ways to get around 40minute install time for e2e testing if possible. Microshift is one of the possible avenues to explore.
Looked into Hive cluster but it seems like we may not have enough permission there to install operators unless we make our own hive.
@ggiguash I am part of the OADP team and we are investigating ways to get around 40minute install time for e2e testing if possible. Microshift is one of the possible avenues to explore.
Please, review the list of OCP API supported by MicroShift at https://github.com/openshift/microshift/blob/main/docs/enabled_apis.md. We have no plans to enable OLM support in the foreseeable future.
Let's close this issue, unless there is any further questions on OADP installation without OLM.
We are not worried about OADP installation specifically. This issue is not regarding any operator installation or OLM. The ask is simply, can we have something like kind create cluster
for microshift.
If you have go (1.17+) and docker installed go install sigs.k8s.io/kind@v0.17.0 && kind create cluster is all you need!
I am not asking for additional API support, OLM support, OADP support from microshift.
I am asking that microshift be as easy to install and up and running ready for kubectl/oc like kind cluster
specifically on non RHEL systems that are used by travis-ci/circle-ci if possible.
I hope title change clear up the minimal requirements.
Hey,
I'm not sure if Ubuntu support makes a lot of sense for this project. Microshift is a project build for the Red Hat family of operating systems. Designed to be a light weight, edge worthy deployment of OpenShift and ideally run on os-tree bistro deployments.
In that regard, I'm not sure the mission of the Microshift project would include support for multiple Operating Systems. I understand what you're saying about upstream CI environments. But I don't think multi-OS support is something this project is pursuing.
With regards to kind-like deployment that can be up and running quickly. Have you tried Code Ready Containers? https://github.com/code-ready/crc https://developers.redhat.com/blog/2019/09/05/red-hat-openshift-4-on-your-laptop-introducing-red-hat-codeready-containers
Maybe that would be better suited for your use case?
@kaovilai, At this time, we only plan supporting MicroShift on RHEL 8.x and, later, RHEL 9.x OS. Furthermore, due to the nature of the project, we are not planning to support container-based bootstrap for MicroShift. All these for downstream activities.
When upstream activities are resumed, it is likely that CentOS and Fedora are going to be used by the community.
Overall, the only configuration we can offer for running MicroShift on Ubunty is to bootstrap a RHEL VM and run MicroShift in it. An example of such a quick-starter can be found at https://github.com/openshift/microshift/blob/main/docs/getting_started.md.
Microshift had Ubuntu install scripts previously iiuc but later removed.
I just need a flavor of openshift that runs in Travis/circleci. Point me to one if you know anything that works ☺️.
Apart from specific distribution support.
kind cluster support any environment with a valid docker and golang install.
Not so microshift.
I'm afraid that's all we can offer at this time. There are no plans to support Ubuntu or containerized MicroShift deployment as part of the downstream activities.
After we resume upstream work and decouple the current CSI and CNI plugins from the main code base, I don't see any particular reason that MicroShift couldn't be supported on other OSes by community members who wanted to do so.
I did notice a project that is working with MicroShift in Docker - https://github.com/christianh814/fauxpenshift
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Ubuntu/Debian support is still relevant. Many edge devices are not certified to run Fedora or it's just not possible without extensive hacking. There used to be support for ubuntu in this project last year. If part of this microshift effort is goodwill and openness for the community and driving growth of Openshift, this should be considered. https://community.ibm.com/community/user/cloud/blogs/alexei-karve/2022/04/17/microshift-13
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Agree @Ozfer it's very important. It's almost as foundational as Podman.
@kaovilai have you tried k0s/k3s/microk8s?
I've tried kind cluster which works well but lacks openshift apis
/lifecycle frozen
I've tried kind cluster which works well but lacks openshift apis
@kaovilai , note that MicroShift does not support full set of OpenShift APIs. See https://github.com/openshift/microshift/blob/main/docs/contributor/enabled_apis.md for more information.
Yeah that should be good enough.. and then I assume I can add operatorhub on top as necessary.
BTW, unblocking other OSes would be a huge help in getting more community contributions to fixing the project IMO.. and reduce likelihood of this project adoption being limited.. but perhaps that's by design. As seen in LinkedIn post
I found this Microshift installer script that doesn't require a pull secret. Perhaps that's a good starting point for an eventual PR that will solve this issue.
@codespearhead , the script installs a 2-year-old microshift package from @redhat-et/microshift
.
See https://github.com/nerdalert/microshift-installer/blob/8cb53a452d0461555026a8d9c372242d7b0327fc/microshift-install.sh#L40
@ggiguash True.
# microshift version
MicroShift Version: 4.8.0-0.microshift-2022-04-20-141053
Base OKD Version: 4.8.0-0.okd-2021-10-10-030117
However, this seems to be a symptom of a problem that's oddly familiar with this one in the OC repository, don't you think?
In that case, which of these tags identify the latest version that should be published to @redhat-et/microshift
?
In that case, which one the tags identify the latest version that should be published to @redhat-et/microshift?
We stopped publishing MicroShift to @redhat-et/microshift
copr repository long time ago. It contains outdated s/w.
We want to be able to start and run microshift from ubuntu which is used by many ci systems.