inlets-archived
kt-connect
Our great sponsors
inlets-archived | kt-connect | |
---|---|---|
8 | 1 | |
8,407 | 1,451 | |
- | 2.3% | |
8.0 | 0.0 | |
almost 3 years ago | 8 months ago | |
Go | Go | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
inlets-archived
-
Is it normal for an open source creator to be angry you used their code because they "revoked" it?
This appears to be a very old version of the project before it was eventually forked to a repo that belonged to the inlets org on GitHub. That's why when Alex deleted the github.com/inlets/inlets-archived repo yesterday (a fork he controlled, where all the work since late 2018 was done), this repo under the-cc-dev now appears as the root repo of all the forks that exist right now, including my fork (https://github.com/mattwelke/inlets-archived).
-
are there any open source microservice projects for a home user?
Also if you're looking to self host something checkout inlets: https://docs.inlets.dev/#/
-
No port forwarding and bad VPNs - cheap, reliable alternative?
I've used Hamachi (vpn.net), that worked pretty well. You could also try Inlets (https://github.com/inlets/inlets).
-
port-forwarding behind a firewall
Did you check https://github.com/inlets/inlets ? It’s an opensource alternative to cloudfared. Never use it myself but creator has a good track-record of developing nice oss solutions (were raspberry is usually first-class citizen)
-
Which method do you prefer for accessing your Kubernetes API Server within the Private Network?
I found some of them that are related to this topic, it might be useful for you too: * inlets * kt-connect * shuttle * ngrook
- Ngrok alternative (TCP for the most part) for remote SSH
- Show HN: Inlets 3.0 RC1
-
Azure Hybrid Connection Manager Latency
You could build something similar to HCM yourself. For instance you can use Inlets but you'd have to maintain the server yourself and pay for it. Plus, HCM is a breeze to set up and can be automated with the Azure CLI
kt-connect
-
Which method do you prefer for accessing your Kubernetes API Server within the Private Network?
I found some of them that are related to this topic, it might be useful for you too: * inlets * kt-connect * shuttle * ngrook
What are some alternatives?
chisel - A fast TCP/UDP tunnel over HTTP
kubesphere - The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️
Nebula - A scalable overlay networking tool with a focus on performance, simplicity and security
sshuttle - Transparent proxy server that works as a poor man's VPN. Forwards over ssh. Doesn't require admin. Works with Linux and MacOS. Supports DNS tunneling.
localtunnel - expose yourself
bank-vaults - A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
arkade - Open Source Marketplace For Developer Tools
inlets - Expose your local endpoints to the Internet
quadis-server - Puzzle Arcade Game Clone / Authoritative Server
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)