Jamil
Jamil
After 1.0 launch we could ship this and self-hosted Relays in the next launch
> > I don't think we need this at 1.0 launch -- at launch we could apply static `tc` rules to our managed Relays. > > @jamilbk In the epic...
Blocked on #2044 Blocked on #3353 ## Todo - [ ] Create separate Relay tiers depending on plan - [ ] Refactor STUN-only codepaths in portal to instead select appropriate...
I think the consensus here so far is to have "colored" relays that are sent to clients depending on the account tier they're in. Can save for a bit later.
Refs #2138
So for 1.0 we are prioritizing the cloud-managed portal. Keeping this open to add a prometheus exporter for the self-hosted Relay and Gateway components (which should be much easier).
I suppose we wouldn't if they were only using it as a layer 3 client. But a site-to-site tunnel that's used to connect users in an office to a cloud...
Thanks for your input @Yasamato. > client-to-client communication required Firezone 1.0 policies assume client -> gateway traffic currently. To support those scenarios we would probably want to simply add "gateway...
This actually requires us to [trademark our logo first](https://apps.google.com/supportwidget/articlehome?hl=en&article_url=https%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F10911028%3Fhl%3Den&assistant_id=generic-unu&product_context=10911028&product_name=UnuFlow&trigger_context=a) and then register with a cert authority, which will be a process.
Blocked on firezone/bizops#80