Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu support #984

Open
kaovilai opened this issue Oct 1, 2022 · 29 comments
Open

Ubuntu support #984

kaovilai opened this issue Oct 1, 2022 · 29 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@kaovilai
Copy link
Member

kaovilai commented Oct 1, 2022

We want to be able to start and run microshift from ubuntu which is used by many ci systems.

@ggiguash
Copy link
Contributor

@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.

@kaovilai
Copy link
Member Author

@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.

@kaovilai
Copy link
Member Author

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
Copy link
Contributor

@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.

@kaovilai
Copy link
Member Author

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/[email protected] && kind create cluster is all you need!

https://kind.sigs.k8s.io/

@kaovilai
Copy link
Member Author

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

@kaovilai
Copy link
Member Author

specifically on non RHEL systems that are used by travis-ci/circle-ci if possible.

@kaovilai kaovilai changed the title kind create cluster equivalents for other projects CI/CD in non RPM environments. Ubuntu support. Oct 31, 2022
@kaovilai kaovilai changed the title Ubuntu support. Ubuntu support Oct 31, 2022
@kaovilai
Copy link
Member Author

I hope title change clear up the minimal requirements.

@bshephar
Copy link

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?

@ggiguash
Copy link
Contributor

ggiguash commented Oct 31, 2022

@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.

@kaovilai
Copy link
Member Author

@kaovilai
Copy link
Member Author

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 ☺️.

@kaovilai
Copy link
Member Author

Apart from specific distribution support.

kind cluster support any environment with a valid docker and golang install.

Not so microshift.

@ggiguash
Copy link
Contributor

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.

@dhellmann
Copy link
Contributor

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.

@lbrigman124
Copy link

I did notice a project that is working with MicroShift in Docker - https://github.com/christianh814/fauxpenshift

@openshift-bot
Copy link

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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 13, 2023
@Ozfer
Copy link

Ozfer commented Mar 16, 2023

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

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 16, 2023
@openshift-bot
Copy link

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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 15, 2023
@kmf
Copy link

kmf commented Jul 2, 2023

Agree @Ozfer it's very important.
It's almost as foundational as Podman.

@kaovilai have you tried k0s/k3s/microk8s?

@kaovilai
Copy link
Member Author

kaovilai commented Jul 2, 2023

I've tried kind cluster which works well but lacks openshift apis

@kaovilai
Copy link
Member Author

kaovilai commented Jul 2, 2023

/lifecycle frozen

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 2, 2023
@openshift-ci openshift-ci bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jul 2, 2023
@ggiguash
Copy link
Contributor

ggiguash commented Jul 9, 2023

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.

@kaovilai
Copy link
Member Author

Yeah that should be good enough.. and then I assume I can add operatorhub on top as necessary.

@kaovilai
Copy link
Member Author

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

Star History

star-history-2023927

@codespearhead
Copy link

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.

@ggiguash
Copy link
Contributor

@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

@codespearhead
Copy link

codespearhead commented Apr 11, 2024

@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?

@ggiguash
Copy link
Contributor

ggiguash commented Apr 11, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

9 participants