my name’s toby bellwood i’m the product lead for lagoon um at the maisy io i’m not based in new zealand unfortunately but i am based in canberra australia um and amazing io has quite an extensive team all around the world but we’re particularly proud of our new zealand and australia teams we’ve got eight people now between australia new zealand and we do an awful lot of we’ve got an awful lot of work down here so um we view ourselves as having sort of two homes so i apologize for not being a true new zealander but i am in heart and spirit um so yeah we’ll be talking a little bit about kubernetes a little bit about lagoon a little bit about amazing io but as i said before more than welcome to sort of take questions if you want to try and interrupt my flow go for it i’m more than happy to do that um either ask a question in the chat or unmute yourself and butt in i’m happy either way
so quickly i’ll go through amazing i o amazio is a global managed service provider um delivering secure enterprise-grade web ops solutions and services and amazing io’s key platform is lagoon it’s a product called lagoon and it’s specifically built for kubernetes-based modern cloud environments um the company itself we we sort of pride ourselves on being able to host anything anywhere in the world so um we deal with a number of infrastructure providers vendors um our team is based all across the world so australia new zealand um europe south africa um north america we’ve even got a presence in the caribbean so um i’m not sure that was business driven but he uh he sends us lots of photos and we’re very jealous um we pride ourselves on our 24 24 hour a day chat based support so because we’re a global company because we’ve got people all around the world we do support our customers all over everything is open source we believe strongly in open source so lagoon product itself is open source a lot of the products we use inside lagoon are open source um and we think uh for our customers and our users having full visibility into what we’ve built and what we’re doing um is the only way to go so we’re fully committed to transparency um globally clients include governments healthcare financial services education media travel um you name it we’ve pretty much covered it um and we’ve worked really hard on being trusted for our security and our support and in the last few months we’ve also launched a partnership model to bring ourselves a lot closer to the people who are running sites on our platform and people who are working with their customers so um yeah we believe strongly in their collaboration cooperation so i’ll quickly from the top i’ll just quickly go through what kubernetes is for anybody that doesn’t understand what kubernetes is um this will be a very quick intro for anyone who does understand kubernetes i apologize if i’ve missed anything but it’s basically a it’s a portable open source platform for containerized workloads um facilitates declarative configuration automation so basically you the platform itself is all defined in code so everything you do in kubernetes is written down as a piece of code so you have to write every element you want to build in kubernetes you’re writing code it’s not pointy clicky draggy droppy like the um some of the systems of old it gives you a lot of flexibility um it’s a natural successor to virtualized environment so um in the old old days we used to have one server per site or one server per web presence we then went to virtualize so one server could host multiple vms and each vm could do multiple workloads kubernetes and containers are the natural six sectors of that so they can be you can have really really tiny sites or applications that only serve a static page and receive 500 hits a month up to sites that host millions and billions of page views and can scale off the charts sean hamlin one of our technical account managers did a really good talk yesterday about the need to scale during the covid19 um response for the australian government so there should be a recording somewhere around but if you can dig that out that’s a really good example of what kubernetes can do and how it can scale massively in a way that virtualized servers couldn’t and in a way that physical servers definitely couldn’t it’s used all around the world everyone’s talking about kubernetes everyone wants kubernetes it is not for the faint of heart it’s not something that’s easy and straightforward to deploy um we at amazio we’re a very big drupal um very big part of the drupal community and there’s a brilliant um slack channel in the drupal chat called kubernetes in which almost every month someone steps in and says hey i’m trying to deploy my site to kubernetes and i’ve come across this error and there’s sort of a collective sigh as everyone realizes that we’ve been doing this for two three four five years and we understand the nuances and someone coming in cold trying to deploy particularly a cms application into kubernetes is in for a whole world of learning um it’s a fairly comprehensive undertaking all the examples you see of kubernetes will be how to deploy a little node app or a little python app or um real-world implementations are far harder and far more complicated so kubernetes as i alluded to it’s based on containers so if you’re familiar with docker docker has this model of um building applications from containers each container has a specified purpose and those containers can interact with each other too so you’d have a database container you’d have a web application container and if you’ve got search you’d have a search container
so these containers they’re called pods they sort of host these individual components of the applications um kubernetes has deployments and sets which tell kubernetes how to deploy these pods so what ports should they open if they um whether that how many of them there should be whether they should tear them down when they die whether they should recreate them how much resources to give them and there’s a whole raft of things on the right hand side you can see a very small part of what a kubernetes deployment looks like um rolling updates unavailable search replicas templates there’s ready seconds and it’s there’s a whole lot of information there it’s really really controllable but it’s really hard to get right um services so if your application needs connecting to the outside world so um whether that’s a web service or whether that’s a database service or whether that’s a search service kubernetes controls all of those so it knows what ports are open it knows what external endpoints to give them what web domains etc storage every application needs well most applications need to store stuff somewhere when where do you store that data what kind of storage is it if you’ve got an application that has multiple pods because we’ve got massive traffic you’ve got lots of replicas you’ve got to have a way that that storage can be accessed by multiple people at the same time so um you might need multiple different um pods writing to an app to a storage at the same time so you might need to make that read write many read writes once if you’ve only got a single writing stream um where about does that go what kind of storage and how does that interface with the underlying provider communities has jobs a job is just a short running task it’s not necessarily a website it’s more a cron job or something small that you need particularly in the cms world um drupal wordpress laravel they all have short running tasks that could be used a little a little bit of gardening a little bit of tidy up behind the scenes and labels um kubernetes has a lot of labels and labels are what’s used to control all manner of things and they’ve also got annotations which can help kubernetes decide where it puts things a kubernetes install has multiple nodes and each node can have a certain amount of pods and those pods can go on nodes depending on what i’m trying to get at is that kubernetes is it’s really hard there’s a there’s a lot to understand and it’s a very different mental model um each of these applications that we build then live inside an individual namespace so a pod from one namespace board from your website can’t talk to someone else’s website unless you specifically allow it um there’s a lot to get your head around um and coming from a simple if you’ve got a simple web application lamp stack if you’re used to using apache mysql php um it’s very different it’s very different because you don’t have direct access you don’t have direct control to a lot of the environments that are running you can’t just go in and make a change to a production file the production files got to be deployed via one of those deployments um we you can make a change but the next time a deployment comes through it will overwrite whatever change you’ve made so you’ve got to put that change back through the process um application delivery in kubernetes is something that we have identified as being something that lagoon can solve so as we’ve just covered we’re talking about pods we’re talking about deployments and talking about storage there’s a lot of configuration needed to just run an application and that’s without any of the extras that you’d want to run in production so yeah when we’re talking about storage talking about ingress we’re talking about strategies we’re talking about replicas we’re talking about resource allocations there’s an awful lot that you need to do and web applications naturally are very complex if we’re looking at a typical drupal installation you might have a php process you might have an nginx to serve the site you’d have a maria mariadb or mysql or postgres database you might have solar or elasticsearch you might have redis to do caching you might have mem case you might have varnish you could have like easily seven or eight different services inside those applications and each of those services need all of that configuration they need to be configured to talk to each other they need to be configured you generally don’t scale your database the same way you’d scale your web in kubernetes and if you have kubernetes is built to be disaster tolerant it’s supposed to be fault redundant so a node that has pods in it if that node becomes unavailable or non-responsive those pods can automatically schedule somewhere else your application has to be able to handle that pod scheduling on a different node there may be a few seconds where kubernetes has to work to find out where that pods gone to so your application has to be that little bit tolerant of that um in order to do all this your developers need to know a lot about yaml um and for those that don’t know a lot about yaml don’t it’s horrible um it’s like jason but made complicated for um for reasons we’ll say um but yeah the slightest error in a yaml format um can cause things to not deploy in unintended circumstances etc there’s a few uis for managing a kubernetes cluster but not many for doing the sort of the configuration aspect of kubernetes a lot of it you’re in notepad you’re in visual studio you’re editing yaml or if you’re brave editing yaml directly in the the kubernetes ui um and while kubernetes knows about these strategies rolling strategies it knows about the pod failover it knows about the redundancy aspects this isn’t automated out of the box you still need to program and configure your applications to do this
and also the base images for applications are often very customized so drupal has custom elements inside it that it needs to have on top of php to work wordpress has similar mono silver stripe in new zealand that’s similar there need to be a couple of extensions enabled and um there’s sort of no real broad standard about how to do that kubernetes doesn’t come out the box with this stuff it’s something that you need to build you need to configure yourself and there are a lot of tools out there for anybody that’s ever looked at the cloud native compute foundation’s landscape the cncf landscape you’ll see there’s an awful lot of tools around application delivery around continuous delivery and we’ve looked at them i’ve got a super spreadsheet with about 100 tools on it at this stage that we regularly look through and try to identify what are they doing how they’re doing it the primary focus of a lot of these tools is for the deployment of a single site so if you’ve got an application um that you want to build and configure to put on the web if it’s a single app you can use flux argo techton waypoint there’s almost a new tool every week that comes out these are really good for individual applications where your devops team knows that app and it can make those changes as soon as you want to deploy more applications you’ve got to build an individual pipeline for every single application you deploy um for our point of view at amazing io as a managed hosting provider we host thousands of sites and managing thousands of pipelines for thousands of sites is a huge burden and while we could template some of it we’ve gone a different route and we’re really trying to sort of tailor application delivery to web applications and really look at what are the web applications most commonly in use and that’s why we’ve decided that a lot of the sensible defaults that come out of kubernetes aren’t the best for what we’re particularly doing so um we’re looking to add and augment those defaults with the settings that are best for our particular applications and the other aspect that comes to this is that once you’ve got your application running on kubernetes it comes with a bit of sort of infrastructure monitoring but it doesn’t come with application monitoring it doesn’t come with logging so if you need to collect logs um whether application logs or container logs or administration logs if you need to do backups you’re sort of raw backuping a kubernetes object so one of the things we’ve wrapped into as well as adapting those sensible defaults is we’ve put in what we think is the optimal monitoring logging and backup stack for web applications so enter lagoon um we we like to think that lagoon drastically reduces the time taken to bring web applications to kubernetes so we’ll provide that configuration tooling insights and we’ve got a lot of experience running these sites in production at scale securely so lagoon is developer focused the idea is we put the power back in the developer’s hand so not having to write kubernetes yaml if you’re a drupal or a wordpress or a silver stripe dev is going to be one less thing to worry about i know that a lot of our team here at amazio have spent a year two years getting to grips with kubernetes and this is all day every day this is their job and we learn and discover and understand stuff every day so having to learn kubernetes yaml on top of your job as a drupal developer or wordpress developer is a pretty big ask
one of the things we really pride ourselves on and that’s because we’re using that containerization method popularized by docker local development runs using those same base images that kubernetes does so you can do an awful lot of development work locally and be really confident that it’s going to work in production as it does on your local we’ve really worked to emulate to really streamline that local to production workflow for our developers to give them the confidence in that process but it’s all based on git ops and infrastructure as code so the same as kubernetes but we’ve brought it down to the application level so fundamentally all you need to do to make an application run on lagoon is add a couple of files and a couple of lines of configuration and it will do the rest obviously because we want to be configurable we do have options to control routes and to control storage and control some of those jobs but broadly what’s in the code base is what’s in lagoon so we’ve got a user interface so we can trigger those um so people who aren’t familiar with command line interfaces who haven’t maybe got the permissions on the git repo but as a project manager or as a product owner you can trigger a redeployment you can see how that has worked from straight from the ui
because it’s based on gitops when you’ve got pr branch at prs you’ve got git branches we can generate automated environments from those so if you’re doing a new piece of work on a new section of your website you can submit that as a pull request to your repo and lagoon will see that pull request and it will create a branch for you separate to your main one that you can then go through and you can look at and you can share with the client or the customer or the executive or your family member if you’re proud um and really show them what it looks like and that because that’s running in lagoon that’s as close to production as you’ll get so you can really iron out any last-minute kinks at that stage and that all comes automatically generated as part of the gitops pipeline um the ui has got um a large amount of the same functionality as the api and the cli do so that you’re able to see your deployments you’re able to see your environments you’re able to delete environments you can get a rich understanding of the the current state of where your application is at without having to dig into the code without having to go deep and part of what we do as lagoon is provide some of those base images i was talking about so if you want to run a php web application we’ve made a docker image for php that’s optimized towards running in docker and kubernetes that’s optimized to running in production securely and the sites on our platform don’t have to use our base images but well over 95 of them do because they’ve got that tooling they’ve got that configuration built in the how to send mail how to configure robot headers how to automate some tasks how to set up cron jobs
um so we’ve basically we’ve used we’ve put a lot of thought and knowledge into those base images to be able to automate the deployment process i’ll pick up quickly that question from rodney um how much logan is our product and how much of his packaging open source kubernetes tools so in terms of rancher we sit in a slightly different space to rancho rancher broadly is used to automate the clusters whereas we’re automating the deployments into the clusters so we i mean we do actually use rancher to manage our clusters but we use lagoon to manage the deployments within the clusters we do stand on the shoulders of um
other open a lot of open source tools so we use a kubernetes backup tool called k8 up we use um projects like scopio we use elasticsearch we use grafana prometheus
so i’ll read the next part of your question um when we talk about being a manual service provider are we meaning off the shelf apps or for customers that are bringing their own applications um broadly our strong preference is for sort of running off the shelf apps if you’re bringing your own application to kubernetes that’s got your own um sort of infrastructure setup and configuration that sort of
it’s going to be quite hard to massage that into the lagoon model the lagoon model is loosely opinionated we’ll say towards that sort of traditional web application structure the non-cloud native one if you can architect your application itself to be cloud native from day one you’re going to have a better experience in kubernetes but as yeah as we went through a lot of these web apps we’re talking about aren’t cloud native um right yeah sorry toby you’ll just get to the chase here you know we we have a containerized application that that does run under kubernetes i’m just i’m just wondering when you talk about being a managed service provider whether you are actually providing that option maybe this is a conversation a bit better to pick up later um with you guys um because it might not be fitting the mainstream of what you’re going through today yeah thanks anyway it’s it’s kind of it’s kind of similar it’s only a similar line um but yeah i think once you’re looking at the kind of application i think you’re talking about without seeing it i’d find it hard to know but um the we’re trying to simplify kubernetes for web application developers and if you’ve already got a devops process like certainly i’d like to have a look and see we can sort of tell quite quickly whether it’s we’re going to be listening let’s pick it up offline i don’t want to divert you from the mainstream talk that’s right um so yeah essentially we provide a similar function there’s a number of tools out there that can do something similar the where we’ve um targeted is the market that needs a bit of help sort of to cross that divide um and we are also capable of running and managing um lagoon works on multiple kubernetes clusters we’ve got dozens of them from an amazi point of view so we can sort of split and segregate workloads
so in the kubernetes stack basically we’ve got the underlying providers so we’ve got um aws google cloud azure um in new zealand we’ve also got catalyst cloud we’ve got a partnership um onshore in new zealand with catalyst we can also deal with on-premise kubernetes clusters so the kubernetes sits on top of that infrastructure and we’re using the managed kubernetes services from all of them so the infrastructure provisioning um comes as part of the aws google cloud so we’re not having to install our own um operating systems we’re not having to maintain uh patch levels and stuff like that that all comes out the box so kubernetes is there lagoon sits on top of that kubernetes and then running on lagoon you’ve got these sort of languages so php node python um and we’ve got the applications that then still on top of there so drupal wordpress um laravel silverstripe etc all sit on top of those applications also in some of those languages so yeah strongly focused on web applications such as cms’s because those cms’s are are a little bit more confusing but we would have a look at containerized applications um and yeah as i said we can sort of quite quickly judge whether it’s going to be a good fit for lagoon or not um depending on how much control basically the application wants and needs over the infrastructure so the only requirement essentially is kubernetes to run lagoon um so yeah we’ve got it tested and running on all of those clusters around the world we’ve built a large collection of templates for drupal wordpress laravel and silverstripe um on silverstripe particularly tom um is going to give a talk on silverstripe on lagoon on friday i think and that’s the process we went through to convert a silver stripe install to work on lagoon because essentially silver stripe is php nginx and mysql so it fits that mold quite nicely one of the extra values in here is that lagoon manages the database the cache and and that logging that we spoke about from a database point of view um the major cloud providers all provide managed databases so um whether it’s aurora or ids whether it’s cloud sql um or whatever the is your version is called we’ve built tools that can interface with those managed databases or services so if your project requires mysql requires postgres we can run that in a docker container on your local machine but lagoon will take that and instead of running a postgres container in production lagoon will convert that to being a table in a database as a service offering so you get the large scale scalability you get the performance and it makes it a lot more manageable for for from our point of view because database scaling is one of the hardest things to do um in kubernetes so we’ve basically put a layer in there that will help be able to run those at scale for you caching again we can interface with um elasticase or whatever the version for google and azure are we can provision tables and entries inside there so we can run redis caches um logs so the lagoon installs run by maze io all have open distropholitic search running and cabana and we can ship logs to there but we’ve also got plugins to be able to ship logs to um anywhere else so datadog sumo logic um splunk we’ve built a logging system that can put the logs that you want where you need them to be and yeah as i covered in the slide before we provide those base images we would strongly encourage people to use them if they’re running a application on lagoon because they’ve got a lot of the configuration built in there already in the sensible defaults but there’s a lot of people that use our base images outside of lagoon because we’ve got a rigorous process behind releasing them we’ve got a lot of experience in in making them and in running these kind of applications
so lagoon has been around for a surprisingly long time um lagoon zero was launched in december 2016 because someone needed to run a node application in openshift about eight nine months later lagoon 0.5 was released and that’s where it was released publicly that’s when the decision was made to make lagoon an open source project um a lot of work went in between august 27 2019 um and over in australia the australian government federal government and the government victoria made a lot of investment into lagoon lagoon one included a full rbac support so role-based access control so users and customers can really easily control what permissions their users have what their users are available to do in the in the application itself so you can give finally granular find granular permissions to people um last year april 2020 kubernetes support came you’ll see initially that lagoon worked on openshift openshift is red hat’s implementation of kubernetes we went with native kubernetes support just over a year ago and that was a lot of our customers were looking for that real managed kubernetes option so being able to run on azure community service or elastic communities or google kubernetes engine having the abstraction of openshift in there for some of our customers who had existing kubernetes installs or existing um relationships it was really important to them and we’ve taken that one step further and um there’s little tilde may 2021 lagoon 2. lagoon 2 has basically been re-architected to run natively on kubernetes so lagoon itself runs in kubernetes um which means that people who are wanting to build and deploy their own lagoon and we now have a number of customers we’re working with who are deploying their own lagoons managing themselves um he’s really facilitated that and it’s a lot easier and simpler to deploy a lagoon on kubernetes now than it was before um token architecture slide um because i wouldn’t feel i was being um authentic if i didn’t have a at least some confusing looking slide with arrows and pictures all over the place but basically as we’ve said the developer pushes code to get git tells lagoon about this code push lagoon tells a kubernetes cluster that there’s something to do that we’ve got to do a build so lagoon goes ahead checks out that git repo looks through it works out what services it needs pulls those images builds those images
looks at what deployments what services what storage what databases it needs configures the logging sets up backup sets up security if you’ve got additional jobs or tasks to run lagoon will do that in this stage um we’ll watch the build going through and once the build is ready the cluster will tell lagoon that yep that build’s ready it’s good to go and the developer gets a slack message or an email or a microsoft teams or a notification that says hey your site’s deployed you’re good to go um it’s a lot more complex than that obviously but that gives an idea of you basically as a developer you push the code and lagoon does the rest when it comes back to you the notification comes back and says hey your site’s been deployed hopefully your site’s been deployed successfully if it hasn’t lagoon will provide you with logs that should provide an understanding of what’s gone wrong um and
90 of the time the problem is with the application itself um that a rush config import hasn’t worked or some wordpress startup process hasn’t worked but because it’s git you can check out that code and you can deploy it yourself locally and you can try and replicate the problem and most of the time it does um those problems are replicatable if not slack support is there to try and help people over this um one of our strongest things that we think lagoon is really good for is portfolio management so um although lagoon was built to run a single site it’s capable of managing multiple sites so from some of our customers have one site some of our customers have hundreds we think um one of the things that’s really that we really like about lagoon and we’ve um worked on with our users is trying to get easy to understand intelligence about your site so what are your sites doing how are they looking how are they running if you’re running multiple drupal sites what version of drupal are they running if you’re running drupal laravel wordpress sites can you easily tell which ones which and what kind of information can we collect about those so um can we collect the version information obviously how can we use that and part of the work we’re doing at the moment is around making it easier to surface that kind of information if there’s a vulnerability announced in a certain module or a certain package how do we find out about that one of the things that lagoon does is integrate with image scanning tool so um trivi for example um is a docker image scanner and that can scan a docker image and it can pull out all the um components in there and it can identify which ones have security vulnerabilities and that information could come straight out of trivia and go into lagoon so lagoon user will be able to see hey there’s a critical vulnerability with this package i wonder where that’s come from how do i fix that and they can then understand that that’s something that needs to be remedied um if there’s a drupal vulnerability being able to alert someone that the version of drupal they’re running is compromised um having a task system is another thing we’re working on so having this really extensible task system so when you’re doing routine tasks and it could be clearing your caches or it could be doing a database dump or it could be synchronizing a database between a production and a development environment or the other way around having a task system that can do that kind of work for you without you having to manually ssh into a remote server and dump a database to your local and then push it back up to the remote and hope everything works we’ve built this kind of functionality into lagoon so you can do that kind of work in lagoon itself um so we’d spoke about facts there’s the ability to add metadata to project so if you’ve got a way of classifying projects or a way you need to record additional information about them we can do that we can collect those problems and vulnerabilities from a number of sources
and it works across frameworks so it’s not just php and drupal it could be python and django it could be node and express it could be gatsby it could be ghost it could be silver stripe it could be any one of a number of things we’re trying to build a tool that can really deploy anything
um continuous development is something that we’re really proud of in our team it’s we do a lot of work with our customers building features our customers want um a lot of people in our team are former customers um so we’ve also got a fairly strong insight into what we wanted and how we used the tool and the product um but yeah we do a lot of work with our existing customers to take feedback on features to seek and solicit ux research and a number of our customers because it’s an open source project have identified um opportunities to add additional functionality add additional features um someone the other day picked up that the created date of an ssh key is incorrect in our ui found out where it is and submitted us a pull request to fix the ssh key display date in our ui and that’s brilliant that’s the kind of relationship that we want with our customers
in the wild so i think i’ve already said that lagoon um powers all of the amazing i o websites um from amazing io that’s over 2000 production environments um 5 000 development environments um there’s about two and a half thousand developers developing sites built on lagoon on amazing io we’re doing um almost a thousand deployments a day it’s probably slightly more than that at the moment but these are um across our 40-something clusters all over the globe so there’s a there’s a fair amount of use of this tool um in the wild and yeah as i said there’s two or three other customers who are running their own websites and their own hosting platforms using lagoon separate to amaze the io and they’re part of our community and they’ve helped contribute towards the product as well we’re strongly open source so yeah we use a number of other um cloud native tools under the hood so yep helm fluentd grafana open policy agent k8 up it’s almost exclusively it is exclusively open source tools that make up a lagoon install um we do as i said integrate with a few other non-open source so when we’re talking about splunk or data dog for logging but the primary concept of lagoon is that it’s all open source so we’ve made a commitment to donate um lagoon to the cloud native compute foundation as a sandbox product so we’ve got a dedicated product lead and team building and developing lagoon um amazing io is going to help do the marketing and yeah we’re working with non-amazing organizations on making it a bigger broader open source thing
so briefly um up ahead we’re gonna do more on the sandbox process we’re going to um because lagoon was released four years ago it makes it a little harder to entwine from amazing there’s still a lot of amazing i o defaults in it but that’s a process we’re going through so um lagoon will be standing up as a as a standalone product um with its own website socials etc um but raisio is still the strong number one supporter of lagoon and will be continuing to provide the bulk of the developer work for the foreseeable future um so that we can go through that sandbox process um we’re always looking at expanding the applications so whilst a lot of our examples have been talking about drupal and wordpress and laravel we are looking to push into other applications we’ve got some work on ccan the data management system we’ve got a bit more work in the python space that some customers are looking for us to do so to build out that set of templates so that people can build and deploy their applications using our sensible defaults more simply um never any security push as we provide lagoon to a lot of government customers particularly in australia and around the world there’s a never-ending sort of circle of compliance and audit so we’re looking strongly at sort of rootless policies how to apply network policies um more and more work in application image scanning um to try and ensure the continual compliance of workloads running in lagoon and on kubernetes that work in mass application management that we covered so more work on facts more work on intelligence more work on automation and our team will keep managing and maintaining lagoon we’ve got grand ideas about where we want to go and what we want to do with this um we do so for people that um i’ll put the links up to the github organization but there’s a couple of github orgs there and we do operate sort of discussions and we do have a lot of engagement with customers through those channels to find out what they’re doing whether they can help us whether we can help them and whether we’re going in that right direction
um so yeah website lagoon.sh our twitter handle is used lagoon we’ve got some docs there um we’re currently split across those two github organizations um the i mean the lagoon project itself is currently an amazing io that will be in used lagoon in the next um week or so so it’s very much a work in progress moving that across um thank you very much for listening
deploying web apps on kubernetes
deploy web app on kubernetes
deploy app on kubernetes
deploying web apps on kubernetes aws
deploying web apps on kubernetes architecture
deploying web apps on kubernetes app
deploying web apps on kubernetes application
deploying web apps on kubernetes browser
deploying web apps on kubernetes bridge
deploying web apps on kubernetes building
deploying web apps on kubernetes cluster
deploying web apps on kubernetes confluent
deploying web apps on kubernetes cli
deploying web apps on kubernetes client
deploying web apps on kubernetes dashboard
deploying web apps on kubernetes deployment
deploying web apps on kubernetes docker
deploying web apps on kubernetes desktop
deploying web apps on kubernetes example
deploying web apps on kubernetes edge
deploying web apps on kubernetes ec2 instance
deploying web apps on kubernetes ecs
deploying application on kubernetes
deploying web apps on kubernetes for dummies
deploying web apps on kubernetes for windows
deploying web apps on kubernetes for mac
deploying web apps on kubernetes free
deploying web apps on kubernetes github
deploying web apps on kubernetes gcp
deploying web apps on kubernetes gateway
deploying web apps on kubernetes grid
deploying web apps on kubernetes helm
deploying web apps on kubernetes home assistant
deploying web apps on kubernetes hub
deploying web apps on kubernetes home
deploying web apps on kubernetes homebase
deploying web apps on kubernetes host
deploying web apps on kubernetes ingress
deploying web apps on kubernetes interview questions
deploying web apps on kubernetes install
deploying web apps on kubernetes io
deploying web apps on kubernetes interview
deploying web apps on kubernetes job
deploying web apps on kubernetes job scheduler
deploying web apps on kubernetes java
deploying web apps on kubernetes jenkins
deploying web apps on kubernetes js
deploying web apps on kubernetes jupyter notebook
deploying web apps on kubernetes kubernetes
deploying web apps on kubernetes load balancer
deploying web apps on kubernetes logs
deploying web apps on kubernetes linux
deploying web apps on kubernetes master
deploying web apps on kubernetes mac
deploying web apps on kubernetes machine
deploying web apps on kubernetes mobile
deploying web apps on kubernetes node
deploying web apps on kubernetes network
deploying web apps on kubernetes operator
deploying web apps on kubernetes on rancher
deploying web apps on kubernetes online
deploying web apps on kubernetes office
deploying web apps on kubernetes os
deploying web apps on kubernetes offline
deploying web apps on kubernetes persistent storage
deploying web apps on kubernetes pyspark
deploying web apps on kubernetes persistent volumes
deploying web apps on kubernetes pc
deploying web apps on kubernetes pro
deploying web apps on kubernetes phone
deploying web apps on kubernetes pipeline
deploying web apps on kubernetes provider
deploying web apps on kubernetes quickly
deploying web apps on kubernetes queue
deploying web apps on kubernetes quick
deploying web apps on kubernetes quest
deploying web apps on kubernetes query
deploying web apps on kubernetes rbac
deploying web apps on kubernetes restart pod
deploying web apps on kubernetes readiness probe
deploying web apps on kubernetes router
deploying web apps on kubernetes remote
deploying web apps on kubernetes service
deploying web apps on kubernetes secrets
deploying web apps on kubernetes statefulset
deploying web apps on kubernetes server
deploying web apps on kubernetes station
deploying web apps on kubernetes site
deploying web apps on kubernetes tutorial
deploying web apps on kubernetes the right way
deploying web apps on kubernetes terminal
deploying web apps on kubernetes terraform
deploying web apps on kubernetes tv
deploy service in kubernetes
deploying web apps on kubernetes using helm
deploying web apps on kubernetes ubuntu
deploying web apps on kubernetes using docker
deploying web apps on kubernetes ui
deploying web apps on kubernetes vs yarn
deploying web apps on kubernetes vpn
deploying web apps on kubernetes v6
deploying web apps on kubernetes vm
deploying web apps on kubernetes vlan
deploying web apps on kubernetes vs docker
deploying web apps on kubernetes with kublr
deploying web apps on kubernetes with statefulsets
deploying web apps on kubernetes work
deploying web apps on kubernetes workflow
deploying web apps on kubernetes xcode
deploying web apps on kubernetes xfi
deploying web apps on kubernetes yaml
deploying web apps on kubernetes yaml reference
deploying web apps on kubernetes yaml file
deploying web apps on kubernetes youtube
deploying web apps on kubernetes yam
deploying web apps on kubernetes zero
deploying web apps on kubernetes zscaler
deploying web apps on kubernetes zs
deploying web apps on kubernetes 0.5
deploying app in kubernetes
deploying web apps on kubernetes 101
deploying web apps on kubernetes 11
deploying web apps on kubernetes 10
deploying web apps on kubernetes 12
deploying web apps on kubernetes 1080
deploying web apps on kubernetes 2022
deploying web apps on kubernetes 2021
deploying web apps on kubernetes 2.0
deploying web apps on kubernetes 3.0
deploying web apps on kubernetes 3.5
deploying web apps on kubernetes 3.4
deploy simple app kubernetes
deploying web apps on kubernetes 4.0
deploying web apps on kubernetes 4k
deploying web apps on kubernetes 5g
deploying web apps on kubernetes 64 bit
deploying web apps on kubernetes 6.0
deploying web apps on kubernetes 600
deploying web apps on kubernetes 64
deploying web apps on kubernetes 7.1
deploying web apps on kubernetes 7.0
deploying web apps on kubernetes 7.3
deploy sample application on kubernetes
deploy web application on docker
deploying web apps on kubernetes 900
deploy app in kubernetes