diff --git a/404.html b/404.html index 5374084c..4ebe89fd 100644 --- a/404.html +++ b/404.html @@ -5,13 +5,13 @@ Page Not Found | Zrok - +
Skip to main content

Page Not Found

We could not find what you were looking for.

Please contact the owner of the site that linked you to the original URL and let them know their link is broken.

- + \ No newline at end of file diff --git a/assets/js/05a04aa0.53525c2e.js b/assets/js/05a04aa0.9b268186.js similarity index 99% rename from assets/js/05a04aa0.53525c2e.js rename to assets/js/05a04aa0.9b268186.js index 786c9d11..50c9d942 100644 --- a/assets/js/05a04aa0.53525c2e.js +++ b/assets/js/05a04aa0.9b268186.js @@ -1 +1 @@ -"use strict";(self.webpackChunkwebsite=self.webpackChunkwebsite||[]).push([[543],{3905:(e,t,o)=>{o.d(t,{Zo:()=>d,kt:()=>k});var n=o(7294);function r(e,t,o){return t in e?Object.defineProperty(e,t,{value:o,enumerable:!0,configurable:!0,writable:!0}):e[t]=o,e}function i(e,t){var o=Object.keys(e);if(Object.getOwnPropertySymbols){var n=Object.getOwnPropertySymbols(e);t&&(n=n.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),o.push.apply(o,n)}return o}function a(e){for(var t=1;t=0||(r[o]=e[o]);return r}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(n=0;n=0||Object.prototype.propertyIsEnumerable.call(e,o)&&(r[o]=e[o])}return r}var l=n.createContext({}),p=function(e){var t=n.useContext(l),o=t;return e&&(o="function"==typeof e?e(t):a(a({},t),e)),o},d=function(e){var t=p(e.components);return n.createElement(l.Provider,{value:t},e.children)},u="mdxType",c={inlineCode:"code",wrapper:function(e){var t=e.children;return n.createElement(n.Fragment,{},t)}},h=n.forwardRef((function(e,t){var o=e.components,r=e.mdxType,i=e.originalType,l=e.parentName,d=s(e,["components","mdxType","originalType","parentName"]),u=p(o),h=r,k=u["".concat(l,".").concat(h)]||u[h]||c[h]||i;return o?n.createElement(k,a(a({ref:t},d),{},{components:o})):n.createElement(k,a({ref:t},d))}));function k(e,t){var o=arguments,r=t&&t.mdxType;if("string"==typeof e||r){var i=o.length,a=new Array(i);a[0]=h;var s={};for(var l in t)hasOwnProperty.call(t,l)&&(s[l]=t[l]);s.originalType=e,s[u]="string"==typeof e?e:r,a[1]=s;for(var p=2;p{o.r(t),o.d(t,{assets:()=>l,contentTitle:()=>a,default:()=>u,frontMatter:()=>i,metadata:()=>s,toc:()=>p});var n=o(7462),r=(o(7294),o(3905));const i={},a="Introducing zrok",s={permalink:"/blog/introducing_zrok",source:"@site/blog/introducing_zrok.md",title:"Introducing zrok",description:"I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the \"edge\" layers. It's been quite exciting to watch OpenZiti blossom and grow over the years.",date:"2023-01-31T18:49:25.000Z",formattedDate:"January 31, 2023",tags:[],readingTime:4.595,hasTruncateMarker:!1,authors:[],frontMatter:{}},l={authorsImageUrls:[]},p=[{value:"Private Sharing",id:"private-sharing",level:2},{value:"Files; Repositories; Video... Decentralized",id:"files-repositories-video-decentralized",level:2},{value:"Production zrok",id:"production-zrok",level:2},{value:"Open-Source; Self-Host",id:"open-source-self-host",level:2},{value:"A Start",id:"a-start",level:2}],d={toc:p};function u(e){let{components:t,...o}=e;return(0,r.kt)("wrapper",(0,n.Z)({},d,o,{components:t,mdxType:"MDXLayout"}),(0,r.kt)("p",null,"I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/ziti"},"OpenZiti")," project back in 2017. Most of my work on OpenZiti centered on the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/fabric"},"fabric"),', data and control plane design, and designing abstractions that would support a lot of what became the "edge" layers. It\'s been quite exciting to watch OpenZiti blossom and grow over the years. '),(0,r.kt)("p",null,"For the last six months, I've had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I'm working from the perspective of usability and enabling an amazing end-user experience. I'm excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent."),(0,r.kt)("p",null,"This new project is called... ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),"."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," focuses on streamlining sharing for both developers and end users alike. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti."),(0,r.kt)("p",null,"Here are some of the things that make ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," different..."),(0,r.kt)("h2",{id:"private-sharing"},"Private Sharing"),(0,r.kt)("p",null,'Most of the offerings in this space allow you to easily create "tunnels" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you\'ve got a public URL that you can share to allow access to your endpoint.'),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," expands on this model by supporting something that we're calling \"private sharing\". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You're still sharing with a single command, but your resources are only available to other ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," users through the zero-trust overlay network."),(0,r.kt)("p",null,"In this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect."),(0,r.kt)("p",null,"And if you want public sharing, ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," has that also. Our private sharing modes are an additional capability that ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," adds to the recipe. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),' supports fleets of "public frontends" that can be geographically deployed wherever your internet users need them.'),(0,r.kt)("h2",{id:"files-repositories-video-decentralized"},"Files; Repositories; Video... Decentralized"),(0,r.kt)("p",null,"Most of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It's considered table stakes for these tools to do this in a ",(0,r.kt)("em",{parentName:"p"},"frictionless")," way."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," also provides a frictionless experience for sharing these kinds of network resources. However, we're taking it a step further... ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven't even thought of yet."),(0,r.kt)("p",null,"Combine this kind of resource sharing with our private peer-to-peer capabilities, and you've got the recipe for very powerful decentralized services. Imagine using ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms."),(0,r.kt)("p",null,"We're still just getting started on building out these aspects of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," already provides built-in single-command file sharing. You can ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok/blob/main/docs/v0.3_getting_started/getting_started.md"},"get started")," using these powerful tools today!"),(0,r.kt)("h2",{id:"production-zrok"},"Production zrok"),(0,r.kt)("p",null,(0,r.kt)("a",{parentName:"p",href:"https://netfoundry.io"},"NetFoundry")," is offering ",(0,r.kt)("a",{parentName:"p",href:"https://zrok.io"},"zrok.io"),", a managed ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," service instance you can use to try out ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit ",(0,r.kt)("a",{parentName:"p",href:"https://zrok.io"},"zrok.io")," for details about requesting an invite."),(0,r.kt)("p",null,"Once ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," and ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok.io")," are out of beta, we'll be opening this service up to the public."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok.io")," runs on top of the open-source version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". We're building on top of the same open-source codebase that's ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"available")," today."),(0,r.kt)("h2",{id:"open-source-self-host"},"Open-Source; Self-Host"),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," is committed to being open-source. You've got everything you need to host your own ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," instance on top of your own private OpenZiti network. We've even streamlined this process, and we're including a simple ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok/blob/main/docs/v0.3_self_hosting_guide.md"},"guide")," to getting this running in minutes, including the OpenZiti portions."),(0,r.kt)("p",null,"You can ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"access")," the open-source version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," today."),(0,r.kt)("h2",{id:"a-start"},"A Start"),(0,r.kt)("p",null,"I'm really excited about sharing ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," with you. As of this writing, we're at ",(0,r.kt)("inlineCode",{parentName:"p"},"v0.3.0"),", and there is still a ton of work to do to get ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," to where I know it can go. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," is open-source, and we're going to be developing it in public, just like the rest of the OpenZiti products (check out the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti"},"OpenZiti GitHub"),")."),(0,r.kt)("p",null,"Starting with ",(0,r.kt)("inlineCode",{parentName:"p"},"v0.4"),", I'm planning on producing a set of regularly-released \"development notebooks\", documenting the development process and giving you a look at the work we're doing with ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". I'm also planning on producing a set of videos that work through some of what's involved in building your own tiny version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," on top of OpenZiti; these will be a great introduction to building a ",(0,r.kt)("em",{parentName:"p"},"Ziti Native Application")," from the ground up. These videos will also be a comprehensive look at how ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," works."),(0,r.kt)("p",null,"We'd love your participation in the ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," project! You can find us on GitHub at ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"https://github.com/openziti/zrok"),"."))}u.isMDXComponent=!0}}]); \ No newline at end of file +"use strict";(self.webpackChunkwebsite=self.webpackChunkwebsite||[]).push([[543],{3905:(e,t,o)=>{o.d(t,{Zo:()=>d,kt:()=>k});var n=o(7294);function r(e,t,o){return t in e?Object.defineProperty(e,t,{value:o,enumerable:!0,configurable:!0,writable:!0}):e[t]=o,e}function i(e,t){var o=Object.keys(e);if(Object.getOwnPropertySymbols){var n=Object.getOwnPropertySymbols(e);t&&(n=n.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),o.push.apply(o,n)}return o}function a(e){for(var t=1;t=0||(r[o]=e[o]);return r}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(n=0;n=0||Object.prototype.propertyIsEnumerable.call(e,o)&&(r[o]=e[o])}return r}var l=n.createContext({}),p=function(e){var t=n.useContext(l),o=t;return e&&(o="function"==typeof e?e(t):a(a({},t),e)),o},d=function(e){var t=p(e.components);return n.createElement(l.Provider,{value:t},e.children)},u="mdxType",c={inlineCode:"code",wrapper:function(e){var t=e.children;return n.createElement(n.Fragment,{},t)}},h=n.forwardRef((function(e,t){var o=e.components,r=e.mdxType,i=e.originalType,l=e.parentName,d=s(e,["components","mdxType","originalType","parentName"]),u=p(o),h=r,k=u["".concat(l,".").concat(h)]||u[h]||c[h]||i;return o?n.createElement(k,a(a({ref:t},d),{},{components:o})):n.createElement(k,a({ref:t},d))}));function k(e,t){var o=arguments,r=t&&t.mdxType;if("string"==typeof e||r){var i=o.length,a=new Array(i);a[0]=h;var s={};for(var l in t)hasOwnProperty.call(t,l)&&(s[l]=t[l]);s.originalType=e,s[u]="string"==typeof e?e:r,a[1]=s;for(var p=2;p{o.r(t),o.d(t,{assets:()=>l,contentTitle:()=>a,default:()=>u,frontMatter:()=>i,metadata:()=>s,toc:()=>p});var n=o(7462),r=(o(7294),o(3905));const i={},a="Introducing zrok",s={permalink:"/blog/introducing_zrok",source:"@site/blog/introducing_zrok.md",title:"Introducing zrok",description:"I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the \"edge\" layers. It's been quite exciting to watch OpenZiti blossom and grow over the years.",date:"2023-01-31T18:51:15.000Z",formattedDate:"January 31, 2023",tags:[],readingTime:4.595,hasTruncateMarker:!1,authors:[],frontMatter:{}},l={authorsImageUrls:[]},p=[{value:"Private Sharing",id:"private-sharing",level:2},{value:"Files; Repositories; Video... Decentralized",id:"files-repositories-video-decentralized",level:2},{value:"Production zrok",id:"production-zrok",level:2},{value:"Open-Source; Self-Host",id:"open-source-self-host",level:2},{value:"A Start",id:"a-start",level:2}],d={toc:p};function u(e){let{components:t,...o}=e;return(0,r.kt)("wrapper",(0,n.Z)({},d,o,{components:t,mdxType:"MDXLayout"}),(0,r.kt)("p",null,"I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/ziti"},"OpenZiti")," project back in 2017. Most of my work on OpenZiti centered on the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/fabric"},"fabric"),', data and control plane design, and designing abstractions that would support a lot of what became the "edge" layers. It\'s been quite exciting to watch OpenZiti blossom and grow over the years. '),(0,r.kt)("p",null,"For the last six months, I've had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I'm working from the perspective of usability and enabling an amazing end-user experience. I'm excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent."),(0,r.kt)("p",null,"This new project is called... ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),"."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," focuses on streamlining sharing for both developers and end users alike. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti."),(0,r.kt)("p",null,"Here are some of the things that make ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," different..."),(0,r.kt)("h2",{id:"private-sharing"},"Private Sharing"),(0,r.kt)("p",null,'Most of the offerings in this space allow you to easily create "tunnels" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you\'ve got a public URL that you can share to allow access to your endpoint.'),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," expands on this model by supporting something that we're calling \"private sharing\". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You're still sharing with a single command, but your resources are only available to other ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," users through the zero-trust overlay network."),(0,r.kt)("p",null,"In this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect."),(0,r.kt)("p",null,"And if you want public sharing, ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," has that also. Our private sharing modes are an additional capability that ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," adds to the recipe. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),' supports fleets of "public frontends" that can be geographically deployed wherever your internet users need them.'),(0,r.kt)("h2",{id:"files-repositories-video-decentralized"},"Files; Repositories; Video... Decentralized"),(0,r.kt)("p",null,"Most of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It's considered table stakes for these tools to do this in a ",(0,r.kt)("em",{parentName:"p"},"frictionless")," way."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," also provides a frictionless experience for sharing these kinds of network resources. However, we're taking it a step further... ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven't even thought of yet."),(0,r.kt)("p",null,"Combine this kind of resource sharing with our private peer-to-peer capabilities, and you've got the recipe for very powerful decentralized services. Imagine using ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms."),(0,r.kt)("p",null,"We're still just getting started on building out these aspects of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," already provides built-in single-command file sharing. You can ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok/blob/main/docs/v0.3_getting_started/getting_started.md"},"get started")," using these powerful tools today!"),(0,r.kt)("h2",{id:"production-zrok"},"Production zrok"),(0,r.kt)("p",null,(0,r.kt)("a",{parentName:"p",href:"https://netfoundry.io"},"NetFoundry")," is offering ",(0,r.kt)("a",{parentName:"p",href:"https://zrok.io"},"zrok.io"),", a managed ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," service instance you can use to try out ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit ",(0,r.kt)("a",{parentName:"p",href:"https://zrok.io"},"zrok.io")," for details about requesting an invite."),(0,r.kt)("p",null,"Once ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," and ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok.io")," are out of beta, we'll be opening this service up to the public."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok.io")," runs on top of the open-source version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". We're building on top of the same open-source codebase that's ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"available")," today."),(0,r.kt)("h2",{id:"open-source-self-host"},"Open-Source; Self-Host"),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," is committed to being open-source. You've got everything you need to host your own ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," instance on top of your own private OpenZiti network. We've even streamlined this process, and we're including a simple ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok/blob/main/docs/v0.3_self_hosting_guide.md"},"guide")," to getting this running in minutes, including the OpenZiti portions."),(0,r.kt)("p",null,"You can ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"access")," the open-source version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," today."),(0,r.kt)("h2",{id:"a-start"},"A Start"),(0,r.kt)("p",null,"I'm really excited about sharing ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," with you. As of this writing, we're at ",(0,r.kt)("inlineCode",{parentName:"p"},"v0.3.0"),", and there is still a ton of work to do to get ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," to where I know it can go. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," is open-source, and we're going to be developing it in public, just like the rest of the OpenZiti products (check out the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti"},"OpenZiti GitHub"),")."),(0,r.kt)("p",null,"Starting with ",(0,r.kt)("inlineCode",{parentName:"p"},"v0.4"),", I'm planning on producing a set of regularly-released \"development notebooks\", documenting the development process and giving you a look at the work we're doing with ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". I'm also planning on producing a set of videos that work through some of what's involved in building your own tiny version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," on top of OpenZiti; these will be a great introduction to building a ",(0,r.kt)("em",{parentName:"p"},"Ziti Native Application")," from the ground up. These videos will also be a comprehensive look at how ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," works."),(0,r.kt)("p",null,"We'd love your participation in the ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," project! You can find us on GitHub at ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"https://github.com/openziti/zrok"),"."))}u.isMDXComponent=!0}}]); \ No newline at end of file diff --git a/assets/js/3953c40d.5f9cba1b.js b/assets/js/3953c40d.5fb27c08.js similarity index 99% rename from assets/js/3953c40d.5f9cba1b.js rename to assets/js/3953c40d.5fb27c08.js index 19420625..a857cd63 100644 --- a/assets/js/3953c40d.5f9cba1b.js +++ b/assets/js/3953c40d.5fb27c08.js @@ -1 +1 @@ -"use strict";(self.webpackChunkwebsite=self.webpackChunkwebsite||[]).push([[474],{3905:(e,t,o)=>{o.d(t,{Zo:()=>d,kt:()=>k});var n=o(7294);function r(e,t,o){return t in e?Object.defineProperty(e,t,{value:o,enumerable:!0,configurable:!0,writable:!0}):e[t]=o,e}function i(e,t){var o=Object.keys(e);if(Object.getOwnPropertySymbols){var n=Object.getOwnPropertySymbols(e);t&&(n=n.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),o.push.apply(o,n)}return o}function a(e){for(var t=1;t=0||(r[o]=e[o]);return r}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(n=0;n=0||Object.prototype.propertyIsEnumerable.call(e,o)&&(r[o]=e[o])}return r}var l=n.createContext({}),p=function(e){var t=n.useContext(l),o=t;return e&&(o="function"==typeof e?e(t):a(a({},t),e)),o},d=function(e){var t=p(e.components);return n.createElement(l.Provider,{value:t},e.children)},u="mdxType",c={inlineCode:"code",wrapper:function(e){var t=e.children;return n.createElement(n.Fragment,{},t)}},h=n.forwardRef((function(e,t){var o=e.components,r=e.mdxType,i=e.originalType,l=e.parentName,d=s(e,["components","mdxType","originalType","parentName"]),u=p(o),h=r,k=u["".concat(l,".").concat(h)]||u[h]||c[h]||i;return o?n.createElement(k,a(a({ref:t},d),{},{components:o})):n.createElement(k,a({ref:t},d))}));function k(e,t){var o=arguments,r=t&&t.mdxType;if("string"==typeof e||r){var i=o.length,a=new Array(i);a[0]=h;var s={};for(var l in t)hasOwnProperty.call(t,l)&&(s[l]=t[l]);s.originalType=e,s[u]="string"==typeof e?e:r,a[1]=s;for(var p=2;p{o.r(t),o.d(t,{assets:()=>l,contentTitle:()=>a,default:()=>u,frontMatter:()=>i,metadata:()=>s,toc:()=>p});var n=o(7462),r=(o(7294),o(3905));const i={},a="Introducing zrok",s={permalink:"/blog/introducing_zrok",source:"@site/blog/introducing_zrok.md",title:"Introducing zrok",description:"I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the \"edge\" layers. It's been quite exciting to watch OpenZiti blossom and grow over the years.",date:"2023-01-31T18:49:25.000Z",formattedDate:"January 31, 2023",tags:[],readingTime:4.595,hasTruncateMarker:!1,authors:[],frontMatter:{}},l={authorsImageUrls:[]},p=[{value:"Private Sharing",id:"private-sharing",level:2},{value:"Files; Repositories; Video... Decentralized",id:"files-repositories-video-decentralized",level:2},{value:"Production zrok",id:"production-zrok",level:2},{value:"Open-Source; Self-Host",id:"open-source-self-host",level:2},{value:"A Start",id:"a-start",level:2}],d={toc:p};function u(e){let{components:t,...o}=e;return(0,r.kt)("wrapper",(0,n.Z)({},d,o,{components:t,mdxType:"MDXLayout"}),(0,r.kt)("p",null,"I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/ziti"},"OpenZiti")," project back in 2017. Most of my work on OpenZiti centered on the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/fabric"},"fabric"),', data and control plane design, and designing abstractions that would support a lot of what became the "edge" layers. It\'s been quite exciting to watch OpenZiti blossom and grow over the years. '),(0,r.kt)("p",null,"For the last six months, I've had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I'm working from the perspective of usability and enabling an amazing end-user experience. I'm excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent."),(0,r.kt)("p",null,"This new project is called... ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),"."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," focuses on streamlining sharing for both developers and end users alike. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti."),(0,r.kt)("p",null,"Here are some of the things that make ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," different..."),(0,r.kt)("h2",{id:"private-sharing"},"Private Sharing"),(0,r.kt)("p",null,'Most of the offerings in this space allow you to easily create "tunnels" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you\'ve got a public URL that you can share to allow access to your endpoint.'),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," expands on this model by supporting something that we're calling \"private sharing\". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You're still sharing with a single command, but your resources are only available to other ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," users through the zero-trust overlay network."),(0,r.kt)("p",null,"In this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect."),(0,r.kt)("p",null,"And if you want public sharing, ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," has that also. Our private sharing modes are an additional capability that ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," adds to the recipe. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),' supports fleets of "public frontends" that can be geographically deployed wherever your internet users need them.'),(0,r.kt)("h2",{id:"files-repositories-video-decentralized"},"Files; Repositories; Video... Decentralized"),(0,r.kt)("p",null,"Most of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It's considered table stakes for these tools to do this in a ",(0,r.kt)("em",{parentName:"p"},"frictionless")," way."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," also provides a frictionless experience for sharing these kinds of network resources. However, we're taking it a step further... ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven't even thought of yet."),(0,r.kt)("p",null,"Combine this kind of resource sharing with our private peer-to-peer capabilities, and you've got the recipe for very powerful decentralized services. Imagine using ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms."),(0,r.kt)("p",null,"We're still just getting started on building out these aspects of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," already provides built-in single-command file sharing. You can ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok/blob/main/docs/v0.3_getting_started/getting_started.md"},"get started")," using these powerful tools today!"),(0,r.kt)("h2",{id:"production-zrok"},"Production zrok"),(0,r.kt)("p",null,(0,r.kt)("a",{parentName:"p",href:"https://netfoundry.io"},"NetFoundry")," is offering ",(0,r.kt)("a",{parentName:"p",href:"https://zrok.io"},"zrok.io"),", a managed ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," service instance you can use to try out ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit ",(0,r.kt)("a",{parentName:"p",href:"https://zrok.io"},"zrok.io")," for details about requesting an invite."),(0,r.kt)("p",null,"Once ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," and ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok.io")," are out of beta, we'll be opening this service up to the public."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok.io")," runs on top of the open-source version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". We're building on top of the same open-source codebase that's ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"available")," today."),(0,r.kt)("h2",{id:"open-source-self-host"},"Open-Source; Self-Host"),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," is committed to being open-source. You've got everything you need to host your own ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," instance on top of your own private OpenZiti network. We've even streamlined this process, and we're including a simple ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok/blob/main/docs/v0.3_self_hosting_guide.md"},"guide")," to getting this running in minutes, including the OpenZiti portions."),(0,r.kt)("p",null,"You can ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"access")," the open-source version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," today."),(0,r.kt)("h2",{id:"a-start"},"A Start"),(0,r.kt)("p",null,"I'm really excited about sharing ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," with you. As of this writing, we're at ",(0,r.kt)("inlineCode",{parentName:"p"},"v0.3.0"),", and there is still a ton of work to do to get ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," to where I know it can go. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," is open-source, and we're going to be developing it in public, just like the rest of the OpenZiti products (check out the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti"},"OpenZiti GitHub"),")."),(0,r.kt)("p",null,"Starting with ",(0,r.kt)("inlineCode",{parentName:"p"},"v0.4"),", I'm planning on producing a set of regularly-released \"development notebooks\", documenting the development process and giving you a look at the work we're doing with ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". I'm also planning on producing a set of videos that work through some of what's involved in building your own tiny version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," on top of OpenZiti; these will be a great introduction to building a ",(0,r.kt)("em",{parentName:"p"},"Ziti Native Application")," from the ground up. These videos will also be a comprehensive look at how ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," works."),(0,r.kt)("p",null,"We'd love your participation in the ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," project! You can find us on GitHub at ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"https://github.com/openziti/zrok"),"."))}u.isMDXComponent=!0}}]); \ No newline at end of file +"use strict";(self.webpackChunkwebsite=self.webpackChunkwebsite||[]).push([[474],{3905:(e,t,o)=>{o.d(t,{Zo:()=>d,kt:()=>k});var n=o(7294);function r(e,t,o){return t in e?Object.defineProperty(e,t,{value:o,enumerable:!0,configurable:!0,writable:!0}):e[t]=o,e}function i(e,t){var o=Object.keys(e);if(Object.getOwnPropertySymbols){var n=Object.getOwnPropertySymbols(e);t&&(n=n.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),o.push.apply(o,n)}return o}function a(e){for(var t=1;t=0||(r[o]=e[o]);return r}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(n=0;n=0||Object.prototype.propertyIsEnumerable.call(e,o)&&(r[o]=e[o])}return r}var l=n.createContext({}),p=function(e){var t=n.useContext(l),o=t;return e&&(o="function"==typeof e?e(t):a(a({},t),e)),o},d=function(e){var t=p(e.components);return n.createElement(l.Provider,{value:t},e.children)},u="mdxType",c={inlineCode:"code",wrapper:function(e){var t=e.children;return n.createElement(n.Fragment,{},t)}},h=n.forwardRef((function(e,t){var o=e.components,r=e.mdxType,i=e.originalType,l=e.parentName,d=s(e,["components","mdxType","originalType","parentName"]),u=p(o),h=r,k=u["".concat(l,".").concat(h)]||u[h]||c[h]||i;return o?n.createElement(k,a(a({ref:t},d),{},{components:o})):n.createElement(k,a({ref:t},d))}));function k(e,t){var o=arguments,r=t&&t.mdxType;if("string"==typeof e||r){var i=o.length,a=new Array(i);a[0]=h;var s={};for(var l in t)hasOwnProperty.call(t,l)&&(s[l]=t[l]);s.originalType=e,s[u]="string"==typeof e?e:r,a[1]=s;for(var p=2;p{o.r(t),o.d(t,{assets:()=>l,contentTitle:()=>a,default:()=>u,frontMatter:()=>i,metadata:()=>s,toc:()=>p});var n=o(7462),r=(o(7294),o(3905));const i={},a="Introducing zrok",s={permalink:"/blog/introducing_zrok",source:"@site/blog/introducing_zrok.md",title:"Introducing zrok",description:"I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the \"edge\" layers. It's been quite exciting to watch OpenZiti blossom and grow over the years.",date:"2023-01-31T18:51:15.000Z",formattedDate:"January 31, 2023",tags:[],readingTime:4.595,hasTruncateMarker:!1,authors:[],frontMatter:{}},l={authorsImageUrls:[]},p=[{value:"Private Sharing",id:"private-sharing",level:2},{value:"Files; Repositories; Video... Decentralized",id:"files-repositories-video-decentralized",level:2},{value:"Production zrok",id:"production-zrok",level:2},{value:"Open-Source; Self-Host",id:"open-source-self-host",level:2},{value:"A Start",id:"a-start",level:2}],d={toc:p};function u(e){let{components:t,...o}=e;return(0,r.kt)("wrapper",(0,n.Z)({},d,o,{components:t,mdxType:"MDXLayout"}),(0,r.kt)("p",null,"I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/ziti"},"OpenZiti")," project back in 2017. Most of my work on OpenZiti centered on the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/fabric"},"fabric"),', data and control plane design, and designing abstractions that would support a lot of what became the "edge" layers. It\'s been quite exciting to watch OpenZiti blossom and grow over the years. '),(0,r.kt)("p",null,"For the last six months, I've had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I'm working from the perspective of usability and enabling an amazing end-user experience. I'm excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent."),(0,r.kt)("p",null,"This new project is called... ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),"."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," focuses on streamlining sharing for both developers and end users alike. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti."),(0,r.kt)("p",null,"Here are some of the things that make ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," different..."),(0,r.kt)("h2",{id:"private-sharing"},"Private Sharing"),(0,r.kt)("p",null,'Most of the offerings in this space allow you to easily create "tunnels" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you\'ve got a public URL that you can share to allow access to your endpoint.'),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," expands on this model by supporting something that we're calling \"private sharing\". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You're still sharing with a single command, but your resources are only available to other ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," users through the zero-trust overlay network."),(0,r.kt)("p",null,"In this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect."),(0,r.kt)("p",null,"And if you want public sharing, ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," has that also. Our private sharing modes are an additional capability that ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," adds to the recipe. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),' supports fleets of "public frontends" that can be geographically deployed wherever your internet users need them.'),(0,r.kt)("h2",{id:"files-repositories-video-decentralized"},"Files; Repositories; Video... Decentralized"),(0,r.kt)("p",null,"Most of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It's considered table stakes for these tools to do this in a ",(0,r.kt)("em",{parentName:"p"},"frictionless")," way."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," also provides a frictionless experience for sharing these kinds of network resources. However, we're taking it a step further... ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven't even thought of yet."),(0,r.kt)("p",null,"Combine this kind of resource sharing with our private peer-to-peer capabilities, and you've got the recipe for very powerful decentralized services. Imagine using ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms."),(0,r.kt)("p",null,"We're still just getting started on building out these aspects of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," already provides built-in single-command file sharing. You can ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok/blob/main/docs/v0.3_getting_started/getting_started.md"},"get started")," using these powerful tools today!"),(0,r.kt)("h2",{id:"production-zrok"},"Production zrok"),(0,r.kt)("p",null,(0,r.kt)("a",{parentName:"p",href:"https://netfoundry.io"},"NetFoundry")," is offering ",(0,r.kt)("a",{parentName:"p",href:"https://zrok.io"},"zrok.io"),", a managed ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," service instance you can use to try out ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit ",(0,r.kt)("a",{parentName:"p",href:"https://zrok.io"},"zrok.io")," for details about requesting an invite."),(0,r.kt)("p",null,"Once ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," and ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok.io")," are out of beta, we'll be opening this service up to the public."),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok.io")," runs on top of the open-source version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". We're building on top of the same open-source codebase that's ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"available")," today."),(0,r.kt)("h2",{id:"open-source-self-host"},"Open-Source; Self-Host"),(0,r.kt)("p",null,(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," is committed to being open-source. You've got everything you need to host your own ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," instance on top of your own private OpenZiti network. We've even streamlined this process, and we're including a simple ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok/blob/main/docs/v0.3_self_hosting_guide.md"},"guide")," to getting this running in minutes, including the OpenZiti portions."),(0,r.kt)("p",null,"You can ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"access")," the open-source version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," today."),(0,r.kt)("h2",{id:"a-start"},"A Start"),(0,r.kt)("p",null,"I'm really excited about sharing ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," with you. As of this writing, we're at ",(0,r.kt)("inlineCode",{parentName:"p"},"v0.3.0"),", and there is still a ton of work to do to get ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," to where I know it can go. ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," is open-source, and we're going to be developing it in public, just like the rest of the OpenZiti products (check out the ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti"},"OpenZiti GitHub"),")."),(0,r.kt)("p",null,"Starting with ",(0,r.kt)("inlineCode",{parentName:"p"},"v0.4"),", I'm planning on producing a set of regularly-released \"development notebooks\", documenting the development process and giving you a look at the work we're doing with ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok"),". I'm also planning on producing a set of videos that work through some of what's involved in building your own tiny version of ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," on top of OpenZiti; these will be a great introduction to building a ",(0,r.kt)("em",{parentName:"p"},"Ziti Native Application")," from the ground up. These videos will also be a comprehensive look at how ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," works."),(0,r.kt)("p",null,"We'd love your participation in the ",(0,r.kt)("inlineCode",{parentName:"p"},"zrok")," project! You can find us on GitHub at ",(0,r.kt)("a",{parentName:"p",href:"https://github.com/openziti/zrok"},"https://github.com/openziti/zrok"),"."))}u.isMDXComponent=!0}}]); \ No newline at end of file diff --git a/assets/js/b2f554cd.59cf7689.js b/assets/js/b2f554cd.8e27fad1.js similarity index 99% rename from assets/js/b2f554cd.59cf7689.js rename to assets/js/b2f554cd.8e27fad1.js index 1b17d486..3796de9e 100644 --- a/assets/js/b2f554cd.59cf7689.js +++ b/assets/js/b2f554cd.8e27fad1.js @@ -1 +1 @@ -"use strict";(self.webpackChunkwebsite=self.webpackChunkwebsite||[]).push([[477],{10:e=>{e.exports=JSON.parse('{"blogPosts":[{"id":"/introducing_zrok","metadata":{"permalink":"/blog/introducing_zrok","source":"@site/blog/introducing_zrok.md","title":"Introducing zrok","description":"I\'m fortunate that I\'ve had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the \\"edge\\" layers. It\'s been quite exciting to watch OpenZiti blossom and grow over the years.","date":"2023-01-31T18:49:25.000Z","formattedDate":"January 31, 2023","tags":[],"readingTime":4.595,"hasTruncateMarker":false,"authors":[],"frontMatter":{}},"content":"I\'m fortunate that I\'ve had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the [OpenZiti](https://github.com/openziti/ziti) project back in 2017. Most of my work on OpenZiti centered on the [fabric](https://github.com/openziti/fabric), data and control plane design, and designing abstractions that would support a lot of what became the \\"edge\\" layers. It\'s been quite exciting to watch OpenZiti blossom and grow over the years. \\n\\nFor the last six months, I\'ve had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I\'m working from the perspective of usability and enabling an amazing end-user experience. I\'m excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent.\\n\\nThis new project is called... `zrok`.\\n\\n`zrok` focuses on streamlining sharing for both developers and end users alike. `zrok` takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, `zrok` adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti.\\n\\nHere are some of the things that make `zrok` different...\\n\\n## Private Sharing\\n\\nMost of the offerings in this space allow you to easily create \\"tunnels\\" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you\'ve got a public URL that you can share to allow access to your endpoint.\\n\\n`zrok` expands on this model by supporting something that we\'re calling \\"private sharing\\". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You\'re still sharing with a single command, but your resources are only available to other `zrok` users through the zero-trust overlay network.\\n\\nIn this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. `zrok` handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect.\\n\\nAnd if you want public sharing, `zrok` has that also. Our private sharing modes are an additional capability that `zrok` adds to the recipe. `zrok` supports fleets of \\"public frontends\\" that can be geographically deployed wherever your internet users need them.\\n\\n## Files; Repositories; Video... Decentralized\\n\\nMost of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It\'s considered table stakes for these tools to do this in a _frictionless_ way.\\n\\n`zrok` also provides a frictionless experience for sharing these kinds of network resources. However, we\'re taking it a step further... `zrok` will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven\'t even thought of yet.\\n\\nCombine this kind of resource sharing with our private peer-to-peer capabilities, and you\'ve got the recipe for very powerful decentralized services. Imagine using `zrok` as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms.\\n\\nWe\'re still just getting started on building out these aspects of `zrok`. `zrok` already provides built-in single-command file sharing. You can [get started](https://github.com/openziti/zrok/blob/main/docs/v0.3_getting_started/getting_started.md) using these powerful tools today!\\n\\n## Production zrok\\n\\n[NetFoundry](https://netfoundry.io) is offering [zrok.io](https://zrok.io), a managed `zrok` service instance you can use to try out `zrok` and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit [zrok.io](https://zrok.io) for details about requesting an invite.\\n\\nOnce `zrok` and `zrok.io` are out of beta, we\'ll be opening this service up to the public.\\n\\n`zrok.io` runs on top of the open-source version of `zrok`. We\'re building on top of the same open-source codebase that\'s [available](https://github.com/openziti/zrok) today.\\n\\n## Open-Source; Self-Host\\n\\n`zrok` is committed to being open-source. You\'ve got everything you need to host your own `zrok` instance on top of your own private OpenZiti network. We\'ve even streamlined this process, and we\'re including a simple [guide](https://github.com/openziti/zrok/blob/main/docs/v0.3_self_hosting_guide.md) to getting this running in minutes, including the OpenZiti portions.\\n\\nYou can [access](https://github.com/openziti/zrok) the open-source version of `zrok` today.\\n\\n## A Start\\n\\nI\'m really excited about sharing `zrok` with you. As of this writing, we\'re at `v0.3.0`, and there is still a ton of work to do to get `zrok` to where I know it can go. `zrok` is open-source, and we\'re going to be developing it in public, just like the rest of the OpenZiti products (check out the [OpenZiti GitHub](https://github.com/openziti)).\\n\\nStarting with `v0.4`, I\'m planning on producing a set of regularly-released \\"development notebooks\\", documenting the development process and giving you a look at the work we\'re doing with `zrok`. I\'m also planning on producing a set of videos that work through some of what\'s involved in building your own tiny version of `zrok` on top of OpenZiti; these will be a great introduction to building a _Ziti Native Application_ from the ground up. These videos will also be a comprehensive look at how `zrok` works.\\n\\nWe\'d love your participation in the `zrok` project! You can find us on GitHub at [https://github.com/openziti/zrok](https://github.com/openziti/zrok)."}]}')}}]); \ No newline at end of file +"use strict";(self.webpackChunkwebsite=self.webpackChunkwebsite||[]).push([[477],{10:e=>{e.exports=JSON.parse('{"blogPosts":[{"id":"/introducing_zrok","metadata":{"permalink":"/blog/introducing_zrok","source":"@site/blog/introducing_zrok.md","title":"Introducing zrok","description":"I\'m fortunate that I\'ve had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the \\"edge\\" layers. It\'s been quite exciting to watch OpenZiti blossom and grow over the years.","date":"2023-01-31T18:51:15.000Z","formattedDate":"January 31, 2023","tags":[],"readingTime":4.595,"hasTruncateMarker":false,"authors":[],"frontMatter":{}},"content":"I\'m fortunate that I\'ve had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the [OpenZiti](https://github.com/openziti/ziti) project back in 2017. Most of my work on OpenZiti centered on the [fabric](https://github.com/openziti/fabric), data and control plane design, and designing abstractions that would support a lot of what became the \\"edge\\" layers. It\'s been quite exciting to watch OpenZiti blossom and grow over the years. \\n\\nFor the last six months, I\'ve had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I\'m working from the perspective of usability and enabling an amazing end-user experience. I\'m excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent.\\n\\nThis new project is called... `zrok`.\\n\\n`zrok` focuses on streamlining sharing for both developers and end users alike. `zrok` takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, `zrok` adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti.\\n\\nHere are some of the things that make `zrok` different...\\n\\n## Private Sharing\\n\\nMost of the offerings in this space allow you to easily create \\"tunnels\\" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you\'ve got a public URL that you can share to allow access to your endpoint.\\n\\n`zrok` expands on this model by supporting something that we\'re calling \\"private sharing\\". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You\'re still sharing with a single command, but your resources are only available to other `zrok` users through the zero-trust overlay network.\\n\\nIn this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. `zrok` handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect.\\n\\nAnd if you want public sharing, `zrok` has that also. Our private sharing modes are an additional capability that `zrok` adds to the recipe. `zrok` supports fleets of \\"public frontends\\" that can be geographically deployed wherever your internet users need them.\\n\\n## Files; Repositories; Video... Decentralized\\n\\nMost of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It\'s considered table stakes for these tools to do this in a _frictionless_ way.\\n\\n`zrok` also provides a frictionless experience for sharing these kinds of network resources. However, we\'re taking it a step further... `zrok` will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven\'t even thought of yet.\\n\\nCombine this kind of resource sharing with our private peer-to-peer capabilities, and you\'ve got the recipe for very powerful decentralized services. Imagine using `zrok` as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms.\\n\\nWe\'re still just getting started on building out these aspects of `zrok`. `zrok` already provides built-in single-command file sharing. You can [get started](https://github.com/openziti/zrok/blob/main/docs/v0.3_getting_started/getting_started.md) using these powerful tools today!\\n\\n## Production zrok\\n\\n[NetFoundry](https://netfoundry.io) is offering [zrok.io](https://zrok.io), a managed `zrok` service instance you can use to try out `zrok` and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit [zrok.io](https://zrok.io) for details about requesting an invite.\\n\\nOnce `zrok` and `zrok.io` are out of beta, we\'ll be opening this service up to the public.\\n\\n`zrok.io` runs on top of the open-source version of `zrok`. We\'re building on top of the same open-source codebase that\'s [available](https://github.com/openziti/zrok) today.\\n\\n## Open-Source; Self-Host\\n\\n`zrok` is committed to being open-source. You\'ve got everything you need to host your own `zrok` instance on top of your own private OpenZiti network. We\'ve even streamlined this process, and we\'re including a simple [guide](https://github.com/openziti/zrok/blob/main/docs/v0.3_self_hosting_guide.md) to getting this running in minutes, including the OpenZiti portions.\\n\\nYou can [access](https://github.com/openziti/zrok) the open-source version of `zrok` today.\\n\\n## A Start\\n\\nI\'m really excited about sharing `zrok` with you. As of this writing, we\'re at `v0.3.0`, and there is still a ton of work to do to get `zrok` to where I know it can go. `zrok` is open-source, and we\'re going to be developing it in public, just like the rest of the OpenZiti products (check out the [OpenZiti GitHub](https://github.com/openziti)).\\n\\nStarting with `v0.4`, I\'m planning on producing a set of regularly-released \\"development notebooks\\", documenting the development process and giving you a look at the work we\'re doing with `zrok`. I\'m also planning on producing a set of videos that work through some of what\'s involved in building your own tiny version of `zrok` on top of OpenZiti; these will be a great introduction to building a _Ziti Native Application_ from the ground up. These videos will also be a comprehensive look at how `zrok` works.\\n\\nWe\'d love your participation in the `zrok` project! You can find us on GitHub at [https://github.com/openziti/zrok](https://github.com/openziti/zrok)."}]}')}}]); \ No newline at end of file diff --git a/assets/js/runtime~main.59b4f93e.js b/assets/js/runtime~main.59b4f93e.js new file mode 100644 index 00000000..375beeb8 --- /dev/null +++ b/assets/js/runtime~main.59b4f93e.js @@ -0,0 +1 @@ +(()=>{"use strict";var e,t,r,a,o,n={},d={};function f(e){var t=d[e];if(void 0!==t)return t.exports;var r=d[e]={id:e,loaded:!1,exports:{}};return n[e].call(r.exports,r,r.exports,f),r.loaded=!0,r.exports}f.m=n,f.c=d,e=[],f.O=(t,r,a,o)=>{if(!r){var n=1/0;for(b=0;b=o)&&Object.keys(f.O).every((e=>f.O[e](r[c])))?r.splice(c--,1):(d=!1,o0&&e[b-1][2]>o;b--)e[b]=e[b-1];e[b]=[r,a,o]},f.n=e=>{var t=e&&e.__esModule?()=>e.default:()=>e;return f.d(t,{a:t}),t},r=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,f.t=function(e,a){if(1&a&&(e=this(e)),8&a)return e;if("object"==typeof e&&e){if(4&a&&e.__esModule)return e;if(16&a&&"function"==typeof e.then)return e}var o=Object.create(null);f.r(o);var n={};t=t||[null,r({}),r([]),r(r)];for(var d=2&a&&e;"object"==typeof d&&!~t.indexOf(d);d=r(d))Object.getOwnPropertyNames(d).forEach((t=>n[t]=()=>e[t]));return n.default=()=>e,f.d(o,n),o},f.d=(e,t)=>{for(var r in t)f.o(t,r)&&!f.o(e,r)&&Object.defineProperty(e,r,{enumerable:!0,get:t[r]})},f.f={},f.e=e=>Promise.all(Object.keys(f.f).reduce(((t,r)=>(f.f[r](e,t),t)),[])),f.u=e=>"assets/js/"+({53:"935f2afb",55:"613b9d03",60:"0774a47f",89:"a6aa9e1f",103:"ccc49370",161:"04b79425",195:"c4f5d8e4",212:"8ae7f3b1",218:"8d0344ba",451:"af60b64a",474:"3953c40d",477:"b2f554cd",514:"1be78505",533:"b2b675dd",535:"814f3328",543:"05a04aa0",608:"9e4087bc",711:"9a9d4214",759:"6dca1809",817:"14eb3368",918:"17896441"}[e]||e)+"."+{4:"ad6148c8",53:"a94a4db4",55:"70520b78",60:"e3fc285d",89:"fbce15d2",103:"7060b92b",161:"5ec6e66b",195:"6798201d",212:"e5110459",218:"a58186b9",451:"ebf6bd06",474:"5fb27c08",477:"8e27fad1",514:"3c788369",533:"962454e8",535:"e5f343b0",543:"9b268186",608:"cb7c0455",639:"fc858d1d",711:"1eaae2f3",759:"b1dedb29",817:"83e9c257",918:"d88a4a03",972:"a74fd964"}[e]+".js",f.miniCssF=e=>{},f.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),f.o=(e,t)=>Object.prototype.hasOwnProperty.call(e,t),a={},o="website:",f.l=(e,t,r,n)=>{if(a[e])a[e].push(t);else{var d,c;if(void 0!==r)for(var i=document.getElementsByTagName("script"),b=0;b{d.onerror=d.onload=null,clearTimeout(s);var o=a[e];if(delete a[e],d.parentNode&&d.parentNode.removeChild(d),o&&o.forEach((e=>e(r))),t)return t(r)},s=setTimeout(l.bind(null,void 0,{type:"timeout",target:d}),12e4);d.onerror=l.bind(null,d.onerror),d.onload=l.bind(null,d.onload),c&&document.head.appendChild(d)}},f.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},f.p="/",f.gca=function(e){return e={17896441:"918","935f2afb":"53","613b9d03":"55","0774a47f":"60",a6aa9e1f:"89",ccc49370:"103","04b79425":"161",c4f5d8e4:"195","8ae7f3b1":"212","8d0344ba":"218",af60b64a:"451","3953c40d":"474",b2f554cd:"477","1be78505":"514",b2b675dd:"533","814f3328":"535","05a04aa0":"543","9e4087bc":"608","9a9d4214":"711","6dca1809":"759","14eb3368":"817"}[e]||e,f.p+f.u(e)},(()=>{var e={303:0,532:0};f.f.j=(t,r)=>{var a=f.o(e,t)?e[t]:void 0;if(0!==a)if(a)r.push(a[2]);else if(/^(303|532)$/.test(t))e[t]=0;else{var o=new Promise(((r,o)=>a=e[t]=[r,o]));r.push(a[2]=o);var n=f.p+f.u(t),d=new Error;f.l(n,(r=>{if(f.o(e,t)&&(0!==(a=e[t])&&(e[t]=void 0),a)){var o=r&&("load"===r.type?"missing":r.type),n=r&&r.target&&r.target.src;d.message="Loading chunk "+t+" failed.\n("+o+": "+n+")",d.name="ChunkLoadError",d.type=o,d.request=n,a[1](d)}}),"chunk-"+t,t)}},f.O.j=t=>0===e[t];var t=(t,r)=>{var a,o,n=r[0],d=r[1],c=r[2],i=0;if(n.some((t=>0!==e[t]))){for(a in d)f.o(d,a)&&(f.m[a]=d[a]);if(c)var b=c(f)}for(t&&t(r);i{"use strict";var e,t,r,a,o,n={},f={};function d(e){var t=f[e];if(void 0!==t)return t.exports;var r=f[e]={id:e,loaded:!1,exports:{}};return n[e].call(r.exports,r,r.exports,d),r.loaded=!0,r.exports}d.m=n,d.c=f,e=[],d.O=(t,r,a,o)=>{if(!r){var n=1/0;for(b=0;b=o)&&Object.keys(d.O).every((e=>d.O[e](r[c])))?r.splice(c--,1):(f=!1,o0&&e[b-1][2]>o;b--)e[b]=e[b-1];e[b]=[r,a,o]},d.n=e=>{var t=e&&e.__esModule?()=>e.default:()=>e;return d.d(t,{a:t}),t},r=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,d.t=function(e,a){if(1&a&&(e=this(e)),8&a)return e;if("object"==typeof e&&e){if(4&a&&e.__esModule)return e;if(16&a&&"function"==typeof e.then)return e}var o=Object.create(null);d.r(o);var n={};t=t||[null,r({}),r([]),r(r)];for(var f=2&a&&e;"object"==typeof f&&!~t.indexOf(f);f=r(f))Object.getOwnPropertyNames(f).forEach((t=>n[t]=()=>e[t]));return n.default=()=>e,d.d(o,n),o},d.d=(e,t)=>{for(var r in t)d.o(t,r)&&!d.o(e,r)&&Object.defineProperty(e,r,{enumerable:!0,get:t[r]})},d.f={},d.e=e=>Promise.all(Object.keys(d.f).reduce(((t,r)=>(d.f[r](e,t),t)),[])),d.u=e=>"assets/js/"+({53:"935f2afb",55:"613b9d03",60:"0774a47f",89:"a6aa9e1f",103:"ccc49370",161:"04b79425",195:"c4f5d8e4",212:"8ae7f3b1",218:"8d0344ba",451:"af60b64a",474:"3953c40d",477:"b2f554cd",514:"1be78505",533:"b2b675dd",535:"814f3328",543:"05a04aa0",608:"9e4087bc",711:"9a9d4214",759:"6dca1809",817:"14eb3368",918:"17896441"}[e]||e)+"."+{4:"ad6148c8",53:"a94a4db4",55:"70520b78",60:"e3fc285d",89:"fbce15d2",103:"7060b92b",161:"5ec6e66b",195:"6798201d",212:"e5110459",218:"a58186b9",451:"ebf6bd06",474:"5f9cba1b",477:"59cf7689",514:"3c788369",533:"962454e8",535:"e5f343b0",543:"53525c2e",608:"cb7c0455",639:"fc858d1d",711:"1eaae2f3",759:"b1dedb29",817:"83e9c257",918:"d88a4a03",972:"a74fd964"}[e]+".js",d.miniCssF=e=>{},d.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),d.o=(e,t)=>Object.prototype.hasOwnProperty.call(e,t),a={},o="website:",d.l=(e,t,r,n)=>{if(a[e])a[e].push(t);else{var f,c;if(void 0!==r)for(var i=document.getElementsByTagName("script"),b=0;b{f.onerror=f.onload=null,clearTimeout(s);var o=a[e];if(delete a[e],f.parentNode&&f.parentNode.removeChild(f),o&&o.forEach((e=>e(r))),t)return t(r)},s=setTimeout(l.bind(null,void 0,{type:"timeout",target:f}),12e4);f.onerror=l.bind(null,f.onerror),f.onload=l.bind(null,f.onload),c&&document.head.appendChild(f)}},d.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},d.p="/",d.gca=function(e){return e={17896441:"918","935f2afb":"53","613b9d03":"55","0774a47f":"60",a6aa9e1f:"89",ccc49370:"103","04b79425":"161",c4f5d8e4:"195","8ae7f3b1":"212","8d0344ba":"218",af60b64a:"451","3953c40d":"474",b2f554cd:"477","1be78505":"514",b2b675dd:"533","814f3328":"535","05a04aa0":"543","9e4087bc":"608","9a9d4214":"711","6dca1809":"759","14eb3368":"817"}[e]||e,d.p+d.u(e)},(()=>{var e={303:0,532:0};d.f.j=(t,r)=>{var a=d.o(e,t)?e[t]:void 0;if(0!==a)if(a)r.push(a[2]);else if(/^(303|532)$/.test(t))e[t]=0;else{var o=new Promise(((r,o)=>a=e[t]=[r,o]));r.push(a[2]=o);var n=d.p+d.u(t),f=new Error;d.l(n,(r=>{if(d.o(e,t)&&(0!==(a=e[t])&&(e[t]=void 0),a)){var o=r&&("load"===r.type?"missing":r.type),n=r&&r.target&&r.target.src;f.message="Loading chunk "+t+" failed.\n("+o+": "+n+")",f.name="ChunkLoadError",f.type=o,f.request=n,a[1](f)}}),"chunk-"+t,t)}},d.O.j=t=>0===e[t];var t=(t,r)=>{var a,o,n=r[0],f=r[1],c=r[2],i=0;if(n.some((t=>0!==e[t]))){for(a in f)d.o(f,a)&&(d.m[a]=f[a]);if(c)var b=c(d)}for(t&&t(r);i Archive | Zrok - +
Copyright © 2023 NetFoundry Inc. Built with Docusaurus.
- + \ No newline at end of file diff --git a/blog/atom.xml b/blog/atom.xml index 7ee1b96f..2fd80958 100644 --- a/blog/atom.xml +++ b/blog/atom.xml @@ -2,7 +2,7 @@ https://zrok.io/blog Zrok Blog - 2023-01-31T18:49:25.000Z + 2023-01-31T18:51:15.000Z https://github.com/jpmonette/feed Zrok Blog @@ -11,7 +11,7 @@ <![CDATA[Introducing zrok]]> /introducing_zrok - 2023-01-31T18:49:25.000Z + 2023-01-31T18:51:15.000Z I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the "edge" layers. It's been quite exciting to watch OpenZiti blossom and grow over the years.

For the last six months, I've had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I'm working from the perspective of usability and enabling an amazing end-user experience. I'm excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent.

This new project is called... zrok.

zrok focuses on streamlining sharing for both developers and end users alike. zrok takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, zrok adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti.

Here are some of the things that make zrok different...

Private Sharing​

Most of the offerings in this space allow you to easily create "tunnels" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you've got a public URL that you can share to allow access to your endpoint.

zrok expands on this model by supporting something that we're calling "private sharing". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You're still sharing with a single command, but your resources are only available to other zrok users through the zero-trust overlay network.

In this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. zrok handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect.

And if you want public sharing, zrok has that also. Our private sharing modes are an additional capability that zrok adds to the recipe. zrok supports fleets of "public frontends" that can be geographically deployed wherever your internet users need them.

Files; Repositories; Video... Decentralized​

Most of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It's considered table stakes for these tools to do this in a frictionless way.

zrok also provides a frictionless experience for sharing these kinds of network resources. However, we're taking it a step further... zrok will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven't even thought of yet.

Combine this kind of resource sharing with our private peer-to-peer capabilities, and you've got the recipe for very powerful decentralized services. Imagine using zrok as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms.

We're still just getting started on building out these aspects of zrok. zrok already provides built-in single-command file sharing. You can get started using these powerful tools today!

Production zrok​

NetFoundry is offering zrok.io, a managed zrok service instance you can use to try out zrok and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit zrok.io for details about requesting an invite.

Once zrok and zrok.io are out of beta, we'll be opening this service up to the public.

zrok.io runs on top of the open-source version of zrok. We're building on top of the same open-source codebase that's available today.

Open-Source; Self-Host​

zrok is committed to being open-source. You've got everything you need to host your own zrok instance on top of your own private OpenZiti network. We've even streamlined this process, and we're including a simple guide to getting this running in minutes, including the OpenZiti portions.

You can access the open-source version of zrok today.

A Start​

I'm really excited about sharing zrok with you. As of this writing, we're at v0.3.0, and there is still a ton of work to do to get zrok to where I know it can go. zrok is open-source, and we're going to be developing it in public, just like the rest of the OpenZiti products (check out the OpenZiti GitHub).

Starting with v0.4, I'm planning on producing a set of regularly-released "development notebooks", documenting the development process and giving you a look at the work we're doing with zrok. I'm also planning on producing a set of videos that work through some of what's involved in building your own tiny version of zrok on top of OpenZiti; these will be a great introduction to building a Ziti Native Application from the ground up. These videos will also be a comprehensive look at how zrok works.

We'd love your participation in the zrok project! You can find us on GitHub at https://github.com/openziti/zrok.

]]> diff --git a/blog/index.html b/blog/index.html index e368205b..534ea7be 100644 --- a/blog/index.html +++ b/blog/index.html @@ -5,13 +5,13 @@ Blog | Zrok - +
-

· 5 min read

I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the "edge" layers. It's been quite exciting to watch OpenZiti blossom and grow over the years.

For the last six months, I've had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I'm working from the perspective of usability and enabling an amazing end-user experience. I'm excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent.

This new project is called... zrok.

zrok focuses on streamlining sharing for both developers and end users alike. zrok takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, zrok adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti.

Here are some of the things that make zrok different...

Private Sharing​

Most of the offerings in this space allow you to easily create "tunnels" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you've got a public URL that you can share to allow access to your endpoint.

zrok expands on this model by supporting something that we're calling "private sharing". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You're still sharing with a single command, but your resources are only available to other zrok users through the zero-trust overlay network.

In this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. zrok handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect.

And if you want public sharing, zrok has that also. Our private sharing modes are an additional capability that zrok adds to the recipe. zrok supports fleets of "public frontends" that can be geographically deployed wherever your internet users need them.

Files; Repositories; Video... Decentralized​

Most of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It's considered table stakes for these tools to do this in a frictionless way.

zrok also provides a frictionless experience for sharing these kinds of network resources. However, we're taking it a step further... zrok will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven't even thought of yet.

Combine this kind of resource sharing with our private peer-to-peer capabilities, and you've got the recipe for very powerful decentralized services. Imagine using zrok as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms.

We're still just getting started on building out these aspects of zrok. zrok already provides built-in single-command file sharing. You can get started using these powerful tools today!

Production zrok​

NetFoundry is offering zrok.io, a managed zrok service instance you can use to try out zrok and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit zrok.io for details about requesting an invite.

Once zrok and zrok.io are out of beta, we'll be opening this service up to the public.

zrok.io runs on top of the open-source version of zrok. We're building on top of the same open-source codebase that's available today.

Open-Source; Self-Host​

zrok is committed to being open-source. You've got everything you need to host your own zrok instance on top of your own private OpenZiti network. We've even streamlined this process, and we're including a simple guide to getting this running in minutes, including the OpenZiti portions.

You can access the open-source version of zrok today.

A Start​

I'm really excited about sharing zrok with you. As of this writing, we're at v0.3.0, and there is still a ton of work to do to get zrok to where I know it can go. zrok is open-source, and we're going to be developing it in public, just like the rest of the OpenZiti products (check out the OpenZiti GitHub).

Starting with v0.4, I'm planning on producing a set of regularly-released "development notebooks", documenting the development process and giving you a look at the work we're doing with zrok. I'm also planning on producing a set of videos that work through some of what's involved in building your own tiny version of zrok on top of OpenZiti; these will be a great introduction to building a Ziti Native Application from the ground up. These videos will also be a comprehensive look at how zrok works.

We'd love your participation in the zrok project! You can find us on GitHub at https://github.com/openziti/zrok.

Copyright © 2023 NetFoundry Inc. Built with Docusaurus.
- +

· 5 min read

I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the "edge" layers. It's been quite exciting to watch OpenZiti blossom and grow over the years.

For the last six months, I've had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I'm working from the perspective of usability and enabling an amazing end-user experience. I'm excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent.

This new project is called... zrok.

zrok focuses on streamlining sharing for both developers and end users alike. zrok takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, zrok adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti.

Here are some of the things that make zrok different...

Private Sharing​

Most of the offerings in this space allow you to easily create "tunnels" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you've got a public URL that you can share to allow access to your endpoint.

zrok expands on this model by supporting something that we're calling "private sharing". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You're still sharing with a single command, but your resources are only available to other zrok users through the zero-trust overlay network.

In this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. zrok handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect.

And if you want public sharing, zrok has that also. Our private sharing modes are an additional capability that zrok adds to the recipe. zrok supports fleets of "public frontends" that can be geographically deployed wherever your internet users need them.

Files; Repositories; Video... Decentralized​

Most of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It's considered table stakes for these tools to do this in a frictionless way.

zrok also provides a frictionless experience for sharing these kinds of network resources. However, we're taking it a step further... zrok will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven't even thought of yet.

Combine this kind of resource sharing with our private peer-to-peer capabilities, and you've got the recipe for very powerful decentralized services. Imagine using zrok as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms.

We're still just getting started on building out these aspects of zrok. zrok already provides built-in single-command file sharing. You can get started using these powerful tools today!

Production zrok​

NetFoundry is offering zrok.io, a managed zrok service instance you can use to try out zrok and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit zrok.io for details about requesting an invite.

Once zrok and zrok.io are out of beta, we'll be opening this service up to the public.

zrok.io runs on top of the open-source version of zrok. We're building on top of the same open-source codebase that's available today.

Open-Source; Self-Host​

zrok is committed to being open-source. You've got everything you need to host your own zrok instance on top of your own private OpenZiti network. We've even streamlined this process, and we're including a simple guide to getting this running in minutes, including the OpenZiti portions.

You can access the open-source version of zrok today.

A Start​

I'm really excited about sharing zrok with you. As of this writing, we're at v0.3.0, and there is still a ton of work to do to get zrok to where I know it can go. zrok is open-source, and we're going to be developing it in public, just like the rest of the OpenZiti products (check out the OpenZiti GitHub).

Starting with v0.4, I'm planning on producing a set of regularly-released "development notebooks", documenting the development process and giving you a look at the work we're doing with zrok. I'm also planning on producing a set of videos that work through some of what's involved in building your own tiny version of zrok on top of OpenZiti; these will be a great introduction to building a Ziti Native Application from the ground up. These videos will also be a comprehensive look at how zrok works.

We'd love your participation in the zrok project! You can find us on GitHub at https://github.com/openziti/zrok.

Copyright © 2023 NetFoundry Inc. Built with Docusaurus.
+ \ No newline at end of file diff --git a/blog/introducing_zrok/index.html b/blog/introducing_zrok/index.html index bc1e27c0..489cebcf 100644 --- a/blog/introducing_zrok/index.html +++ b/blog/introducing_zrok/index.html @@ -3,15 +3,15 @@ -Introducing zrok | Zrok +Introducing zrok | Zrok - +
-

Introducing zrok

· 5 min read

I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the "edge" layers. It's been quite exciting to watch OpenZiti blossom and grow over the years.

For the last six months, I've had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I'm working from the perspective of usability and enabling an amazing end-user experience. I'm excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent.

This new project is called... zrok.

zrok focuses on streamlining sharing for both developers and end users alike. zrok takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, zrok adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti.

Here are some of the things that make zrok different...

Private Sharing​

Most of the offerings in this space allow you to easily create "tunnels" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you've got a public URL that you can share to allow access to your endpoint.

zrok expands on this model by supporting something that we're calling "private sharing". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You're still sharing with a single command, but your resources are only available to other zrok users through the zero-trust overlay network.

In this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. zrok handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect.

And if you want public sharing, zrok has that also. Our private sharing modes are an additional capability that zrok adds to the recipe. zrok supports fleets of "public frontends" that can be geographically deployed wherever your internet users need them.

Files; Repositories; Video... Decentralized​

Most of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It's considered table stakes for these tools to do this in a frictionless way.

zrok also provides a frictionless experience for sharing these kinds of network resources. However, we're taking it a step further... zrok will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven't even thought of yet.

Combine this kind of resource sharing with our private peer-to-peer capabilities, and you've got the recipe for very powerful decentralized services. Imagine using zrok as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms.

We're still just getting started on building out these aspects of zrok. zrok already provides built-in single-command file sharing. You can get started using these powerful tools today!

Production zrok​

NetFoundry is offering zrok.io, a managed zrok service instance you can use to try out zrok and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit zrok.io for details about requesting an invite.

Once zrok and zrok.io are out of beta, we'll be opening this service up to the public.

zrok.io runs on top of the open-source version of zrok. We're building on top of the same open-source codebase that's available today.

Open-Source; Self-Host​

zrok is committed to being open-source. You've got everything you need to host your own zrok instance on top of your own private OpenZiti network. We've even streamlined this process, and we're including a simple guide to getting this running in minutes, including the OpenZiti portions.

You can access the open-source version of zrok today.

A Start​

I'm really excited about sharing zrok with you. As of this writing, we're at v0.3.0, and there is still a ton of work to do to get zrok to where I know it can go. zrok is open-source, and we're going to be developing it in public, just like the rest of the OpenZiti products (check out the OpenZiti GitHub).

Starting with v0.4, I'm planning on producing a set of regularly-released "development notebooks", documenting the development process and giving you a look at the work we're doing with zrok. I'm also planning on producing a set of videos that work through some of what's involved in building your own tiny version of zrok on top of OpenZiti; these will be a great introduction to building a Ziti Native Application from the ground up. These videos will also be a comprehensive look at how zrok works.

We'd love your participation in the zrok project! You can find us on GitHub at https://github.com/openziti/zrok.

Copyright © 2023 NetFoundry Inc. Built with Docusaurus.
- +

Introducing zrok

· 5 min read

I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the "edge" layers. It's been quite exciting to watch OpenZiti blossom and grow over the years.

For the last six months, I've had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I'm working from the perspective of usability and enabling an amazing end-user experience. I'm excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent.

This new project is called... zrok.

zrok focuses on streamlining sharing for both developers and end users alike. zrok takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, zrok adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti.

Here are some of the things that make zrok different...

Private Sharing​

Most of the offerings in this space allow you to easily create "tunnels" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you've got a public URL that you can share to allow access to your endpoint.

zrok expands on this model by supporting something that we're calling "private sharing". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You're still sharing with a single command, but your resources are only available to other zrok users through the zero-trust overlay network.

In this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. zrok handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect.

And if you want public sharing, zrok has that also. Our private sharing modes are an additional capability that zrok adds to the recipe. zrok supports fleets of "public frontends" that can be geographically deployed wherever your internet users need them.

Files; Repositories; Video... Decentralized​

Most of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It's considered table stakes for these tools to do this in a frictionless way.

zrok also provides a frictionless experience for sharing these kinds of network resources. However, we're taking it a step further... zrok will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven't even thought of yet.

Combine this kind of resource sharing with our private peer-to-peer capabilities, and you've got the recipe for very powerful decentralized services. Imagine using zrok as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms.

We're still just getting started on building out these aspects of zrok. zrok already provides built-in single-command file sharing. You can get started using these powerful tools today!

Production zrok​

NetFoundry is offering zrok.io, a managed zrok service instance you can use to try out zrok and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit zrok.io for details about requesting an invite.

Once zrok and zrok.io are out of beta, we'll be opening this service up to the public.

zrok.io runs on top of the open-source version of zrok. We're building on top of the same open-source codebase that's available today.

Open-Source; Self-Host​

zrok is committed to being open-source. You've got everything you need to host your own zrok instance on top of your own private OpenZiti network. We've even streamlined this process, and we're including a simple guide to getting this running in minutes, including the OpenZiti portions.

You can access the open-source version of zrok today.

A Start​

I'm really excited about sharing zrok with you. As of this writing, we're at v0.3.0, and there is still a ton of work to do to get zrok to where I know it can go. zrok is open-source, and we're going to be developing it in public, just like the rest of the OpenZiti products (check out the OpenZiti GitHub).

Starting with v0.4, I'm planning on producing a set of regularly-released "development notebooks", documenting the development process and giving you a look at the work we're doing with zrok. I'm also planning on producing a set of videos that work through some of what's involved in building your own tiny version of zrok on top of OpenZiti; these will be a great introduction to building a Ziti Native Application from the ground up. These videos will also be a comprehensive look at how zrok works.

We'd love your participation in the zrok project! You can find us on GitHub at https://github.com/openziti/zrok.

Copyright © 2023 NetFoundry Inc. Built with Docusaurus.
+ \ No newline at end of file diff --git a/blog/rss.xml b/blog/rss.xml index 82f6dd35..2cfacc07 100644 --- a/blog/rss.xml +++ b/blog/rss.xml @@ -4,7 +4,7 @@ Zrok Blog https://zrok.io/blog Zrok Blog - Tue, 31 Jan 2023 18:49:25 GMT + Tue, 31 Jan 2023 18:51:15 GMT https://validator.w3.org/feed/docs/rss2.html https://github.com/jpmonette/feed en @@ -12,7 +12,7 @@ <![CDATA[Introducing zrok]]> https://zrok.io/blog/introducing_zrok /introducing_zrok - Tue, 31 Jan 2023 18:49:25 GMT + Tue, 31 Jan 2023 18:51:15 GMT I'm fortunate that I've had the opportunity to work on many interesting projects throughout my career. I was one of the original developers who broke ground on the OpenZiti project back in 2017. Most of my work on OpenZiti centered on the fabric, data and control plane design, and designing abstractions that would support a lot of what became the "edge" layers. It's been quite exciting to watch OpenZiti blossom and grow over the years.

For the last six months, I've had the opportunity to re-approach the world of zero-trust and next-generation networking from the other side of the stack. Instead of working in the lowest layers of protocols and abstractions, I'm working from the perspective of usability and enabling an amazing end-user experience. I'm excited to introduce you to a new set of tools designed to empower users at the network edge to seamlessly and transparently share resources. Imagine network sharing that is equally secure and transparent.

This new project is called... zrok.

zrok focuses on streamlining sharing for both developers and end users alike. zrok takes inspiration from several other offerings that streamline developer endpoint sharing. Starting from that recipe, zrok adds powerful capabilities that are made possible by building on the foundation provided by OpenZiti.

Here are some of the things that make zrok different...

Private Sharing​

Most of the offerings in this space allow you to easily create "tunnels" that allow outbound-only access to local HTTP resources without punching any holes in a firewall. These tools make these kinds of tunnels effortless to create; with a single command, you've got a public URL that you can share to allow access to your endpoint.

zrok expands on this model by supporting something that we're calling "private sharing". Private sharing allows you to share securely on the zero-trust overlay network, without exposing anything to the public internet. You're still sharing with a single command, but your resources are only available to other zrok users through the zero-trust overlay network.

In this model, no user ever has to enable any inbound access. All network access is handled through the secure, zero-trust overlay network. zrok handles all of the control plane management of the overlay network, deeply simplifying the experience. This secure sharing model remains the single-command affair that users have come to expect.

And if you want public sharing, zrok has that also. Our private sharing modes are an additional capability that zrok adds to the recipe. zrok supports fleets of "public frontends" that can be geographically deployed wherever your internet users need them.

Files; Repositories; Video... Decentralized​

Most of the other offerings in this space are focused on sharing low-level network resources. These tools are often used by developers or operations staff to allow access to a private HTTP endpoint or to facilitate a callback to a private endpoint through a webhook. It's considered table stakes for these tools to do this in a frictionless way.

zrok also provides a frictionless experience for sharing these kinds of network resources. However, we're taking it a step further... zrok will also make this kind of frictionless, decentralized sharing possible for files, software repositories, video streams, and other kinds of resources we haven't even thought of yet.

Combine this kind of resource sharing with our private peer-to-peer capabilities, and you've got the recipe for very powerful decentralized services. Imagine using zrok as a decentralized, distributed replacement for large centralized file-sharing platforms. Or use it as a replacement for large, centralized video streaming platforms.

We're still just getting started on building out these aspects of zrok. zrok already provides built-in single-command file sharing. You can get started using these powerful tools today!

Production zrok​

NetFoundry is offering zrok.io, a managed zrok service instance you can use to try out zrok and run small production workloads. This service is currently in limited beta and is available through an invitation process. Visit zrok.io for details about requesting an invite.

Once zrok and zrok.io are out of beta, we'll be opening this service up to the public.

zrok.io runs on top of the open-source version of zrok. We're building on top of the same open-source codebase that's available today.

Open-Source; Self-Host​

zrok is committed to being open-source. You've got everything you need to host your own zrok instance on top of your own private OpenZiti network. We've even streamlined this process, and we're including a simple guide to getting this running in minutes, including the OpenZiti portions.

You can access the open-source version of zrok today.

A Start​

I'm really excited about sharing zrok with you. As of this writing, we're at v0.3.0, and there is still a ton of work to do to get zrok to where I know it can go. zrok is open-source, and we're going to be developing it in public, just like the rest of the OpenZiti products (check out the OpenZiti GitHub).

Starting with v0.4, I'm planning on producing a set of regularly-released "development notebooks", documenting the development process and giving you a look at the work we're doing with zrok. I'm also planning on producing a set of videos that work through some of what's involved in building your own tiny version of zrok on top of OpenZiti; these will be a great introduction to building a Ziti Native Application from the ground up. These videos will also be a comprehensive look at how zrok works.

We'd love your participation in the zrok project! You can find us on GitHub at https://github.com/openziti/zrok.

]]> diff --git a/docs/category/guides/index.html b/docs/category/guides/index.html index b61dd039..bf25eadf 100644 --- a/docs/category/guides/index.html +++ b/docs/category/guides/index.html @@ -5,13 +5,13 @@ Guides | Zrok - +
Copyright © 2023 NetFoundry Inc. Built with Docusaurus.
- + \ No newline at end of file diff --git a/docs/downloads/index.html b/docs/downloads/index.html index 96129004..17d1593e 100644 --- a/docs/downloads/index.html +++ b/docs/downloads/index.html @@ -5,13 +5,13 @@ Downloads | Zrok - +
Copyright © 2023 NetFoundry Inc. Built with Docusaurus.
- + \ No newline at end of file diff --git a/docs/getting-started/index.html b/docs/getting-started/index.html index ca0e6d90..951c39ee 100644 --- a/docs/getting-started/index.html +++ b/docs/getting-started/index.html @@ -5,7 +5,7 @@ Getting Started with zrok | Zrok - + @@ -13,7 +13,7 @@

Getting Started with zrok

zrok is a next-generation sharing platform built on top of OpenZiti, a programmable zero trust network overlay. zrok is an OpenZiti Native Application.

zrok facilitates sharing resources publicly and privately with an audience of your choosing.

As of version v0.3.0, zrok provides users the ability to publicly proxy local HTTP endpoints (similar to other offerings in this space). Additionally, zrok provides the ability to:

  • privately share resources with other zrok users; in private usage scenarios, your private resources are not exposed to any public endpoints, and all communication is securely and privately transported between zrok clients
  • use web sharing; easily share files with others using a single zrok command

Let's take a look at how to get started with zrok.

Downloading zrok​

Releases are also available from the zrok project repository on GitHub at https://github.com/openziti/zrok/releases/latest

Extract zrok Distribution​

Move the downloaded zrok distribution into a directory on your system. In my case, I've placed it in my home directory:

$ ls -lF zrok*
-rwxr-xr-x 1 michael michael 12724747 Jan 17 12:57 zrok_0.3.0-rc1_linux_amd64.tar.gz*

Create a directory where the extracted distribution will sit:

$ mkdir zrok
$ cd zrok/

Extract the zrok distribution:

$ tar zxvf ../zrok_0.3.0-rc1_linux_amd64.tar.gz
CHANGELOG.md
README.md
zrok

NOTE: On Windows platforms the distribution is shipped as a zip archive. Windows Explorer includes support for extracting zip archives natively.

Add zrok to your shell's environment.

For Linux or macos:

$ export PATH=`pwd`:$PATH

For Windows (using Command Prompt):

> set PATH=%CD%;%PATH%

For Windows (using PowerShell):

$env:path += ";"+$pwd.Path

With the zrok executable in your path, you can then execute the zrok command from your shell:

$ zrok version
               _    
 _____ __ ___ | | __
|_  / '__/ _ \| |/ /
 / /| | | (_) |   < 
/___|_|  \___/|_|\_\

v0.3.0-rc1 [0d43b55]

Configure Your zrok Service Instance​

note

Most users can safely skip this section and proceed to "Generating an Invitation" below.

This section is relevant if you want to use the zrok CLI with an alternate service instance (in the case of self-hosting, etc.).

zrok is both an installable utility that you interact with from your local computer, and also a service that exists on the network. NetFoundry operates the public service instance that is available at api.zrok.io, but because zrok is open source and self-hostable, you're free to create your own zrok service instance.

The zrok executable defaults to using the zrok service instance at api.zrok.io. Should you need to change the endpoint to use a different service instance, you can do that with the following command:

$ zrok config set apiEndpoint https://zrok.mydomain.com
[WARNING]: unable to open zrokdir metadata; ignoring

zrok configuration updated
note

The WARNING about zrokdir metadata is ignorable. Running the zrok config set command writes a small piece of metadata into a .zrok folder inside your home directory. This allows zrok to identify the version of its settings, providing a mechanism to upgrade your installation as new versions are released. This WARNING is letting you know that your current environment has not been initialized by zrok.

You can use the zrok status command to inspect the state of your local environment. zrok refers to each shell where you install and enable a copy of zrok as as an environment.

$ zrok status

Config:

 CONFIG       VALUE                      SOURCE 
 apiEndpoint  https://zrok.mydomain.com  config 

[WARNING]: Unable to load your local environment!

To create a local environment use the zrok enable command.
note

The WARNING about being unable to load your local environment will go away once you've successfully enabled (zrok enable) for your shell (we'll get to that below). For now, this warning is ignorable.

The zrok status command shows the configured API service that your environment is using, as well as the SOURCE where the setting was retrieved. In this case, config means that the setting was set into the environment using the zrok config command.

Generating an Invitation​

In order to create an account with the zrok service instance, you will need to create an invitation.

note

Some environments take advantage of invitation tokens, which limit who is able to request an invitation on the service instance. If your service uses invitation tokens, the administrator of your instance will include details about how to use your token to generate your invitation.

We generate an invitation with the zrok invite command:

$ zrok invite

enter and confirm your email address...

> user@domain.com
> user@domain.com

[ Submit ]

invitation sent to 'user@domain.com'!

The zrok invite command presents a small form that allows you to enter (and then confirm) your email address. Tabbing to the [ Submit ] button will send the request to your configured zrok service.

Next, check the email where you sent the invite. You should receive a message asking you to click a link to create your zrok account. When you click that link, you will be brought to a web page that will allow you to set a password for your new account:

Enter a Password

Enter a password and it's confirmation, and click the Register Account button. You'll see the following:

Successful Registration

For now, we'll ignore the "enable your shell for zrok" section. Just click the zrok web portal link:

Web Login

After clicking the Log In button, you'll be brought into the zrok web console:

Web Console; Empty

Congratulations! Your zrok account is ready to go!

Enabling Your zrok Environment​

When your zrok account was created, the service generated a secret token that identifies and authenticates in a single step. Protect your secret token as if it were a password, or an important account number; it's a secret, protect it.

When we left off you had downloaded, extracted, and configured your zrok environment. In order to use that environment with your account, you'll need to enable it. Enabling an environment generates a secure identity and the necessary underlying security policies with the OpenZiti network hosting the zrok service.

From the web console, click on your email address in the upper right corner of the header. That drop down menu contains an Enable Your Environment link. Click that link and a modal dialog will be shown like this:

Enable Modal Dialog

This dialog box shows you the zrok enable command that you can use to enable any shell to work with your zrok account with a single command.

Let's copy that command and paste it into your shell:

$ zrok enable klFEoIi0QAg7 
⣻  contacting the zrok service...

After a few seconds, the message will change and indicate that the enable operation suceeded:

$ zrok enable klFEoIi0QAg7 
⣻  the zrok environment was successfully enabled...

Now, if we run a zrok status command, you will see the details of your environment:

$ zrok status

Config:

 CONFIG       VALUE                SOURCE 
 apiEndpoint  https://api.zrok.io  env    

Environment:

 PROPERTY       VALUE        
 Secret Token   klFEoIi0QAg7 
 Ziti Identity  FTpvelYD6h

Excellent... our environment is now fully enabled.

If we return to the web console, we'll now see the new environment reflected in the explorer view:

New Environment in Web UI

In my case, the environment is named michael@ziti-lx, which is the username of my shell and the hostname of the system the shell is running on.

note

Should you want to use a non-default name for your environment, you can pass the -d option to the zrok enable command. See zrok enable --help for details.

If you click on the environment node in the explorer in the web console, the details panel shown at the bottom of the page will change:

Empty Environment

The explorer supports clicking, dragging, mouse wheel zooming, and selecting the nodes in the graph for more information (and available actions) for the selected node. If you ever get lost in the explorer, click the Zoom to Fit zoom to fit icon in the lower right corner of the explorer.

If we click on the Detail tab for our environment, we'll see something like:

Environment Detail

Your environment is fully ready to go. Now we can move on to the fun stuff...

Sharing​

zrok is designed to make sharing resources as effortless as possible, while providing a high degree of security and control.

Ephemeral by Default​

Shared resources are ephemeral by default; as soon as you terminate the zrok share command, the entire share is removed and is no longer available to any users. Identifiers for shared resources are randomly allocated when the share is created.

Public Shares and Frontends​

Resources that are shared publicly are exposed to any users on the internet who have access to the zrok service instance's "frontend".

A frontend is an HTTPS listener exposed to the internet, that lets any user with your ephemeral share token access your publicly shared resources.

For example, I might create a public share using the zrok share public command, which results in my zrok service instance exposing the following URL to access my resources:

https://h0fz2ts9c84t.share.zrok.io

In this case my share was given the "share token" of h0fz2ts9c84t. That URL can be given to any user, allowing them to immediately access the shared resources directly from my local environment, all without exposing any access to my private, secure environment. The physical network location of my environment is not exposed to anonymous consumers of my resources.

If we return to the web console, we see our share in the explorer:

Web Console Share

If we click on our new share in the explorer, we can see the share details: Share Details

If we click on the frontend endpoint a new browser tab opens and we see the content of our share: Share Frontend

If we click on the environment in the explorer, we're shown all of the shares for that environment (including our new share), along with a spark line that shows the activity:

Environment Spark Line

And as soon as I terminate the zrok share client, the resources are removed from the zrok environment.

If we try to reload the frontend endpoint in our web browser, we'll see:

Not Found

Private Shares​

zrok also provides a powerful private sharing model. If I execute the following command:

$ zrok share private http://localhost:8080

The zrok service will respond with the following:

access your share with: zrok access private wvszln4dyz9q

Rather than allowing access to your service through a public frontend, a private share is only exposed to the underlying OpenZiti network, and can only be accessed using the zrok access command.

The zrok access private wvszln4dyz9q command can be run by any zrok user, allowing them to create and bind a local HTTP listener, that allows for private access to your shared resources.

Proxy Backend Mode​

Without specifying a backend mode, the zrok share command will assume that you're trying to share a proxy resource. A proxy resource is usually some private HTTP/HTTPS endpoint (like a development server, or a private application) running in your local environment. Usually such an endpoint would have no inbound connectivity except for however it is reachable from your local environment. It might be running on localhost, or only listening on a private LAN segment behind a firewall.

For these services a proxy share will allow those endpoints to be reached, either publicly or privately through the zrok service.

Web Backend Mode​

The zrok share command accepts a --backend-mode option. Besides proxy, the current v0.3 release (as of this writing) also supports a web mode. The web mode allows you to specify a local folder on your filesystem, and instantly turns your zrok client into a web server, exposing your web content either publicly or privately without having to a configure a web server.

Reserved Shares​

zrok shares are ephemeral unless you specifically create a "reserved" share.

A reserved share can be re-used multiple times; it will survive termination of the zrok share command, allowing for longer-lasting semi-permanent access to shared resources.

The first step is to create the reserved share:

$ zrok reserve public --backend-mode web v0.3_getting_started
[   0.275]    INFO main.(*reserveCommand).run: your reserved share token is 'mltwsinym1s2'
[   0.275]    INFO main.(*reserveCommand).run: reserved frontend endpoint: https://mltwsinym1s2.share.zrok.io

I'm asking the zrok service to reserve a share with a web backend mode, pointing at my local docs folder.

You'll want to remember the share token (mltwsinym1s2 in this case), and the frontend endpoint URL. If this were a private reserved share, there would not be a frontend URL.

If we do nothing else, and then point a web browser at the frontend endpoint, we get:

Not Found

This is the 404 error message returned by the zrok frontend. We're getting this because we haven't yet started up a zrok share for the service. Let's do that:

This command:

$ zrok share reserved mltwsinym1s2

...results in a new share backend starting up and connecting to the existing reserved share:

zrok share reserved

And now if we refresh the frontend endpoint URL in the web browser, we'll see an index of the docs directory:

zrok docs share

With the reserved share, we're free to stop and restart the zrok share reserved command as many times as we want, without losing the token for our share.

When we're done with the reserved share, we can release it using this command:

$ zrok release mltwsinym1s2
[   0.230]    INFO main.(*releaseCommand).run: reserved share 'mltwsinym1s2' released

Concepts Review​

In summary, zrok lets you easily and securely share resources with both general internet users (through public sharing) and also with other zrok users (through private sharing).

Here's a quick review of the zrok mental model and the vocabulary.

Service Instance and Account​

You create an account with a zrok service instance. Your account is identified by a username and a password, which you use to log into the web console. Your account also has a secret token, which you will use to authenticate from the zrok command-line to interact with the service instance.

You create a new account with a zrok service instance through the zrok invite command.

Environment​

Using your secret token you use the zrok command-line interface to create an environment. An environment corresponds to a single command-line user on a specific host system.

You create a new environment by using the zrok enable command.

Shares​

Once you've enabled an environment, you then create one or more shares. Shares have either a public or private sharing mode. Shares share a specific type of resource using a backend mode. As of this writing zrok supports a proxy backend mode to share local HTTP resources as a reverse proxy. zrok also supports a web backend mode to share local file and HTML resources by enabling a basic HTTP server.

Every share is identified by a share token. Public shares can be accessed through either a frontend instance offered through the zrok service instance, or through the zrok access command. Private shares can only be accessed through the zrok access command.

You use the zrok share command to create and enable ephemeral shares.

Reserved Shares​

zrok supports creating shares that have a consistent share token that survives restarts of the zrok share command. These are considered non-ephemeral, and is callled a reserved share.

You use the zrok reserve command to create reserved shares. Reserved shares last until you use the zrok release command to delete them.

Self-Hosting a Service Instance​

Interested in self-hosting your own zrok service instance? See the self-hosting guide for details.

Copyright © 2023 NetFoundry Inc. Built with Docusaurus.
- + \ No newline at end of file diff --git a/docs/guides/v0.3_nginx_tls_guide/index.html b/docs/guides/v0.3_nginx_tls_guide/index.html index 49438914..6933ab69 100644 --- a/docs/guides/v0.3_nginx_tls_guide/index.html +++ b/docs/guides/v0.3_nginx_tls_guide/index.html @@ -5,13 +5,13 @@ Nginx Reverse Proxy for zrok | Zrok - +

Nginx Reverse Proxy for zrok

I'll assume you have a running zrok controller and public frontend and wish to front both with Nginx providing server TLS. Go back to Self-Hosting Guide if you still need to spin those up.

Choose a Reverse Proxy Address​

I'll use https://api.zrok.quigley.com:443 in this example, and assume you already set up wildcard DNS like *.zrok.quigley.com. This lets us elect api.zrok.quigley.com as the controller DNS name, and forward any other incoming requests to the zrok public frontend.

Obtain a Wildcard Server Certificate​

You must complete a DNS challenge to obtain a wildcard certificate from Let's Encrypt. I'll assume you know how to create the necessary TXT record in the DNS zone you're using with zrok.

  1. Install certbot: https://eff-certbot.readthedocs.io/en/stable/install.html

  2. Run certbot with the manual plugin: https://certbot.eff.org/docs/using.html#manual

    # install cert for *.zrok.quigley.com in /etc/letsencrypt
    sudo certbot certonly --manual

Install Nginx​

Configure Nginx​

server {
    listen              443 ssl;
    server_name         api.zrok.quigley.com;
    ssl_certificate     /etc/letsencrypt/live/zrok.quigley.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/zrok.quigley.com/privkey.pem;
    ssl_protocols       TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers         HIGH:!aNULL:!MD5;

    location / {
      proxy_pass      http://127.0.0.1:18080;
      error_log       /var/log/nginx/zrok-controller.log;
    }

}

server {
    listen              443 ssl;
    server_name         *.zrok.quigley.com;
    ssl_certificate     /etc/letsencrypt/live/zrok.quigley.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/zrok.quigley.com/privkey.pem;
    ssl_protocols       TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers         HIGH:!aNULL:!MD5;

    location / {
      proxy_pass       http://127.0.0.1:8080;
      proxy_set_header Host $host;
      error_log        /var/log/nginx/zrok-frontend.log;
      proxy_busy_buffers_size   512k;
      proxy_buffers    4 512k;
      proxy_buffer_size   256k;

    }

}

Restart Nginx​

Load the new configuration by restarting Nginx. Check the logs to make sure it's happy.

Started A high performance web server and a reverse proxy server.

Check the Firewall​

If you followed the non-TLS quickstart then you may have opened 8080,108080/tcp in your firewall. You can go ahead and replace those exceptions with 443/tcp because only Nginx needs to be reachable for zrok to function.

Update the zrok Frontend​

List available frontends to obtain the token identifier of the frontend named "public". You may need to set ZROK_ADMIN_TOKEN or ZROK_API_ENDPOINT before running zrok admin.

$ zrok admin list frontends

 TOKEN         ZID        PUBLIC NAME  URL TEMPLATE                              CREATED AT                         UPDATED AT                    
 2NiDTRYUww18  7DsLh9DXG  public       http://{token}.zrok.quigley.com:8080  2023-01-19 05:29:20.793 +0000 UTC  2023-01-19 06:17:25 +0000 UTC

Update the URL template to use Nginx.

$ zrok admin update frontend 2NiDTRYUww18 --url-template https://{token}.zrok.quigley.com:443
[   0.028]    INFO main.(*adminUpdateFrontendCommand).run: updated global frontend '2NiDTRYUww18'
Copyright © 2023 NetFoundry Inc. Built with Docusaurus.
- + \ No newline at end of file diff --git a/docs/guides/v0.3_self_hosting_guide/index.html b/docs/guides/v0.3_self_hosting_guide/index.html index a8c6a853..f305c9ad 100644 --- a/docs/guides/v0.3_self_hosting_guide/index.html +++ b/docs/guides/v0.3_self_hosting_guide/index.html @@ -5,13 +5,13 @@ Self-Hosting Guide | Zrok - +

Self-Hosting Guide

OpenZiti Quickstart​

https://openziti.github.io/docs/quickstarts/network/

I specifically used the "no docker" variant:

$ source /dev/stdin <<< "$(wget -qO- https://get.openziti.io/quick/ziti-cli-functions.sh)"; expressInstall
$ startController
$ startRouter

Keep track of the generated admin password when running the expressInstall script. The script will prompt you like this:

Do you want to keep the generated admin password 'XO0xHp75uuyeireO2xmmVlK91T7B9fpD'? (Y/n)

You'll need that generated password (XO0xHp75uuyeireO2xmmVlK91T7B9fpD) when building your zrok controller configuration.

Configure the Controller​

Create a controller configuration file in etc/ctrl.yml. The controller does not provide server TLS, but you may front the server with a reverse proxy. This example will expose the non-TLS listener for the controller.

#    _____ __ ___ | | __
#   |_  / '__/ _ \| |/ /
#    / /| | | (_) |   <
#   /___|_|  \___/|_|\_\
# controller configuration

v:                  1

admin:
  secrets:
    -               f60b55fa-4dec-4c4a-9244-e3b7d6b9bb13

endpoint:
  host:             0.0.0.0
  port:             18080

store:
  path:             zrok.db
  type:             sqlite3

ziti:
  api_endpoint:     "https://127.0.0.1:1280"
  username:         admin
  password:         "XO0xHp75uuyeireO2xmmVlK91T7B9fpD"

The admin section defines privileged administrative credentials and must be set in the ZROK_ADMIN_TOKEN environment variable in shells where you want to run zrok admin.

The endpoint section defines where your zrok controller will listen.

The store section defines the local sqlite3 database used by the controller.

The ziti section defines how the zrok controller should communicate with your OpenZiti installation. When using the OpenZiti quickstart, an administrative password will be generated; the password in the ziti stanza should reflect this password.

Environment Variables​

The zrok binaries are configured to work with the global zrok.io service, and default to using api.zrok.io as the endpoint for communicating with the service.

To work with a local zrok deployment, you'll need to set the ZROK_API_ENDPOINT environment variable to point to the address where your zrok controller will be listening, according to endpoint in the configuration file above.

In my case, I've set:

$ export ZROK_API_ENDPOINT=http://localhost:18080

Bootstrap OpenZiti for zrok​

With your OpenZiti network running and your configuration saved to a local file (I refer to mine as etc/ctrl.yml in these examples), you're ready to bootstrap the Ziti network.

Use the zrok admin bootstrap command to bootstrap like this:

$ zrok admin bootstrap etc/ctrl.yml 
[   0.002]    INFO main.(*adminBootstrap).run: {
    ...
}
[   0.002]    INFO zrok/controller/store.Open: database connected
[   0.006]    INFO zrok/controller/store.(*Store).migrate: applied 0 migrations
[   0.006]    INFO zrok/controller.Bootstrap: connecting to the ziti edge management api
[   0.039]    INFO zrok/controller.Bootstrap: creating identity for controller ziti access
[   0.071]    INFO zrok/controller.Bootstrap: controller identity: jKd8AINSz
[   0.082]    INFO zrok/controller.assertIdentity: asserted identity 'jKd8AINSz'
[   0.085]    INFO zrok/controller.assertErpForIdentity: asserted erps for 'ctrl' (jKd8AINSz)
[   0.085]    INFO zrok/controller.Bootstrap: creating identity for frontend ziti access
[   0.118]    INFO zrok/controller.Bootstrap: frontend identity: sqJRAINSiB
[   0.119]    INFO zrok/controller.assertIdentity: asserted identity 'sqJRAINSiB'
[   0.120]    INFO zrok/controller.assertErpForIdentity: asserted erps for 'frontend' (sqJRAINSiB)
[   0.120] WARNING zrok/controller.Bootstrap: missing public frontend for ziti id 'sqJRAINSiB'; please use 'zrok admin create frontend sqJRAINSiB public https://{token}.your.dns.name' to create a frontend instance
[   0.123]    INFO zrok/controller.assertZrokProxyConfigType: found 'zrok.proxy.v1' config type with id '33CyjNbIepkXHN5VzGDA8L'
[   0.124]    INFO zrok/controller.assertMetricsService: creating 'metrics' service
[   0.126]    INFO zrok/controller.assertMetricsService: asserted 'metrics' service (5RpPZZ7T8bZf1ENjwGiPc3)
[   0.128]    INFO zrok/controller.assertMetricsSerp: creating 'metrics' serp
[   0.130]    INFO zrok/controller.assertMetricsSerp: asserted 'metrics' serp
[   0.134]    INFO zrok/controller.assertCtrlMetricsBind: creating 'ctrl-metrics-bind' service policy
[   0.135]    INFO zrok/controller.assertCtrlMetricsBind: asserted 'ctrl-metrics-bind' service policy
[   0.138]    INFO zrok/controller.assertFrontendMetricsDial: creating 'frontend-metrics-dial' service policy
[   0.140]    INFO zrok/controller.assertFrontendMetricsDial: asserted 'frontend-metrics-dial' service policy
[   0.140]    INFO main.(*adminBootstrap).run: bootstrap complete!

The zrok admin bootstrap command configures the zrok database, the necessary OpenZiti identities, and all of the OpenZiti policies required to run a zrok service.

Notice this warning:

[   0.120] WARNING zrok/controller.Bootstrap: missing public frontend for ziti id 'sqJRAINSiB'; please use 'zrok admin create frontend sqJRAINSiB public https://{token}.your.dns.name' to create a frontend instance

The zrok bootstrap process wants us to create a "public frontend" for our service. zrok uses public frontends to allow users to specify where they would like public traffic to ingress from.

The zrok admin create frontend command requires a running zrok controller, so let's start that up first:

$ zrok controller etc/ctrl.yml 
[   0.003]    INFO main.(*controllerCommand).run: {
    ...
}
[   0.016]    INFO zrok/controller.inspectZiti: inspecting ziti controller configuration
[   0.048]    INFO zrok/controller.findZrokProxyConfigType: found 'zrok.proxy.v1' config type with id '33CyjNbIepkXHN5VzGDA8L'
[   0.048]    INFO zrok/controller/store.Open: database connected
[   0.048]    INFO zrok/controller/store.(*Store).migrate: applied 0 migrations
[   0.049]    INFO zrok/controller.(*metricsAgent).run: starting
[   0.064]    INFO zrok/rest_server_zrok.setupGlobalMiddleware: configuring
[   0.064]    INFO zrok/ui.StaticBuilder: building
[   0.065]    INFO zrok/rest_server_zrok.(*Server).Logf: Serving zrok at http://[::]:18080
[   0.085]    INFO zrok/controller.(*metricsAgent).listen: started

With our ZROK_ADMIN_TOKEN and ZROK_API_ENDPOINT environment variables set, we can create our public frontend like this:

$ zrok admin create frontend sqJRAINSiB public http://{token}.zrok.quigley.com:8080
[   0.037]    INFO main.(*adminCreateFrontendCommand).run: created global public frontend 'WEirJNHVlcW9'

Now our zrok controller is fully configured.

Configure the Public Frontend​

Create etc/http-frontend.yml. You must reiterate the pattern you expressed in the public frontend URL template as a host_match pattern, and you may change the default address where the frontend will listen for public access requests. The frontend does not provide server TLS, but you may front the server with a reverse proxy. It is essential the reverse proxy forwards the Host header supplied by the viewer. This example will expose the non-TLS listener for the frontend.

host_match: zrok.quigley.com
address: 0.0.0.0:8080

Start Public Frontend​

In another terminal window, run:

$ zrok access public etc/http-frontend.yml
[   0.002]    INFO main.(*accessPublicCommand).run: {
    ...
}
[   0.002]    INFO zrok/endpoints/public_frontend.newMetricsAgent: loaded 'frontend' identity

This process uses the frontend identity created during the bootstrap process to provide public access for the zrok deployment. It is expected that the configured listener for this frontend corresponds to the DNS template specified when creating the public frontend record above.

Invite Yourself​

$ zrok invite
New Email: user@domain.com
Confirm Email: user@domain.com
invitation sent to 'user@domain.com'!

If you look at the console output from your zrok controller, you'll see a message like this:

[ 238.168]    INFO zrok/controller.(*inviteHandler).Handle: account request for 'user@domain.com' has registration token 'U2Ewt1UCn3ql'

You can access your zrok controller's registration UI by pointing a web browser at:

http://localhost:18080/register/U2Ewt1UCn3ql

The UI will ask you to set a password for your new account. Go ahead and do that.

After doing that, I see the following output in my controller console:

[ 516.778]    INFO zrok/controller.(*registerHandler).Handle: created account 'user@domain.com' with token 'SuGzRPjVDIcF'

Keep track of the token listed above (SuGzRPjVDIcF). We'll use this to enable our shell for this zrok deployment.

Enable Your Shell​

$ zrok enable SuGzRPjVDIcF
zrok environment '2AS1WZ3Sz' enabled for 'SuGzRPjVDIcF'

Congratulations. You have a working zrok environment!

Copyright © 2023 NetFoundry Inc. Built with Docusaurus.
- + \ No newline at end of file diff --git a/index.html b/index.html index 201fb55e..42e722ae 100644 --- a/index.html +++ b/index.html @@ -5,13 +5,13 @@ Zrok - +
- + \ No newline at end of file