What's next?

[SteinRobert]

We have received some awesome feedback for Gefyra. We made it to v1 within 2022. Thank you to all the people who gave us feedback, opened issues and all the valuable contributions.

So what's next?

Before building new features we'd like to increase the community and user base of Gefyra. Our hope is that with more users we will be able to better select which features are actually needed / requested.

How do we grow the user base?
We do appreciate anyone sharing Gefyra on any social networks or even among your fellow tech people. Blueshoe is sponsoring some ad-budget to help spread the word.

On the development side we'd like increase the accessibility of Gefyra. It has potentially a lot of flags you need pass to make it work - constructing the commands can be cumbersome sometimes. We currently have 2 approaches on how this could be improved:

1. An extension for Docker Desktop - this is a simple UI which allows to enter everything needed to run an image with Gefyra (in a certain namespace, with env variables...).
2. A VSCode Extension - helping developers within their IDE - adding some UI elements to make the start/input easier. We're using VSCode a lot - if you have other suggestions feel free to comment here.

If you have any ideas on how we could grow our community - we're very grateful for any help or suggestions!

As soon as these things are done and stable we will take a look into further development of Gefyra itself. We will still investigate any bugs or problems with Gefyra itself - so the development is not stuck!

Please let me know if you have questions, ideas or feedback for our team.

---

Robert

[tetricky]

Looks like a very useful toolkit.

I've been using k3s at the edge, and in distributed and multi-clusters...for a range of applications. These are now starting to become more connected (utilising services in one cluster, from another). With dual-stack wireguard now reaching primetime this is of accelerating importance to me.

For various reasons, I've moved away from docker. With local development pretty much exclusively in podman (before deploying to k3s).

So my feature request (and I believe it is on your roadmap...but...) would be podman support. Until that point I am excluded (I realise I'm an edge case, not mainstream...but that may change).

[SteinRobert]

@tetricky thank you for your feedback! You're helping us prioritising the further development with it! I might get back to you on that one :)

[SteinRobert]

Short update on this thread!

We managed to build the first version of the Docker Desktop extension (https://hub.docker.com/r/gefyra/docker-desktop-extension).
We're now preparing the submission to the Docker Desktop marketplace.
Meanwhile we decided to defer the development on the VSCode extension - see how the Docker Desktop extension develops and bring some new features to Gefyra.
This we have planned for the next couple of weeks/months:

• multi peer run - multiple users are able to run / connect their local container to the same cluster (not bridge!) (Geyfra equivelant of personal intercept #269)
• Minikube profile support - Minikube allows to setup multiple clusters via profiles - it is currently not supported by Gefyra to connect to those (gefyra up --minikube not working when Minikube was created with a defined profile #305)
• no public IP / loadbalancer - Gefyra currently relies on NodePorts which means your K8s nodes need to have some kind of public IP - we'd like to change this and make use of LoadBalancers (Running gefyra up --endpoint on nodes without public ip address #292)

[SteinRobert]

Another update!

We're currently in the review process of applying our Docker Desktop extension to the Docker Extension marketplace. Docker asked us to make some changes which lead us to rethink some UI elements we had in the extension. We're continuing to work on this for the next weeks.
Moreover we noticed that with rather loosely written labels and selectors the --env-from flag might pick up the wrong pod to copy the environment (#330) and that Gefyra might exit with 0 even stuff did actually not work (#335).
We refactored the tests from single Github action bash scripts to actual Python tests (#327). Tests are now faster, more precise, less flaky and more granular.

[SteinRobert]

Update the Gefyra Docker Desktop Extension is available on the marketplace! We also fixed some smaller bugs in Gefyra itself (1.0.3). Also we are receiving more feedback and input from you guys which is amazing! Thank you very much!
@Schille is working on making the Gefyra tests more accessible to developers machines as well as some refactorings on the gefyra client itself. The downloads of Gefyra images will be hitting an all time high the month 🤩
I myself will be on vacation and back mid of March. Once all the refactorings are we'll add new features! 🚀
Thank you for helping us making Gefyra even more amazing.

• Robert

[selckin]

End of feb, they scraped stars of other projects and gathered email addresses to send out a giant spam campaign. Violating github TOS https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies#7-information-usage-restrictions

[SteinRobert]

End of feb, they scraped stars of other projects and gathered email addresses to send out a giant spam campaign. Violating github TOS https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies#7-information-usage-restrictions

Thanks for reaching out to us, even though I would have wished you'd found another way than our pinned update thread, knowingly the main maintainer is on vacation for some time.
Let me shine some light on this - we are reaching out to people who have publicly shown interest in Kubernetes related topics, not only since Feb basically since mid of last year. We're working with different sources and services for this "reach-out" - asking for feedback for our open source project - and leave a star if you like it. I admit this is kind of an unsolicited approach of potential users for Gefyra. You could frame this as spam - I wouldn't agree really, since there are no annoying multiple contact tries, no sign up for newsletters or similar.
Anyway your request is heard and our team will put some time into investigating the sources of our sources. Thanks again for reporting and many greetings from my vacation.

-Robert

[selckin]

Yes how unfortunate he's on vacation and you can't just delete my post and sweep this under the rung

[SteinRobert]

Marking this as resolved since this thread went off-topic we no longer run reach-outs.