In your question you didn’t put any specific reasons why you think it’s a good idea to open source your project. There may be certain immediate benefits, such as the discipline it would force you in to. There are big downsides too, such as the distraction of bug triage or code reviews taking you away from focusing on growing your business.
Until you decide, why not work on project as if it was already open source (PRs, unit tests, documentation, etc.) without actually opening it up, and see how it feels first? If the hassle of keeping it going feels like too much when you’re by yourself, that would be valuable to know before you involve others.
I understand the need for launching with GitHub integration only, really. It's probably 2020 table stakes for launching a hosting platform, ticking the "up and running in 5 minutes" requirement checkbox. (See also: Digital Ocean's recently launched App Platform, same situation.)
But many of us walked away from GitHub and embraced GitLab in the last few years, probably a big wave in 2018. As far as I can tell, there's not a publicly documented non-GitHub way to interact with Cloudflare Pages. Cloudflare folks: if you can't launch with a full GitLab integration that's understandable, but I'm tired of sitting these things out because they can only launch in simple mode. For my part, I'd rather fuss around with .gitlab-ci.yml now than start a project on my old GitHub account and deal with unknown migration pains later.
It's disappointing that Github doesn't have repository mirroring, like many competitors do. I suppose that would encourage people to leave their walled garden but still take advantage of their features.
Going by blog posts, 1.17 was released 2019-12-09, 1.18 was released 2020-03-25, 1.19 was released 2020-08-26, and 1.20 was released 2020-12-08 (today). Great cadence.
AWS EKS seems to support major versions six or seven months later. Support for 1.17 was announced 2020-07-13, 1.18 was announced 2020-10-13. I'm guessing we can plan for 1.20 support on EKS around June of 2021. No judgement, just an observation.
This is one of Kubernetes' biggest downfalls. On a small team, time is king. You likely don't have a team dedicated to keeping up with Kube releases, troubleshooting issues, etc.
When you build something, you need it to work until _you_ decide to futz with it again.
supported are 3 minor releases with (1.18) 9months and newer minors 1year updates.
you should always upgrade to one version behind the last major in self managed scenarios. i.e. my company is on 1.18 and goes to 1.19 now. basically if something breaks it's most often not the end of the world, especially not if you do backups with velero.
Straightforward imo (go containers first if this is your eventual intent), with the effort involved dependent on what your service mesh, networking, and storage situation and requirements looks like. More complexity is of course going to make such an effort more work.
Someone else mentioned Fly.io, have a look at Render too.