 Okay, welcome to Securing and Scaling Drupal with Kubernetes. This is a panel of a few folks here. So I'll just start by introducing our panelists and then introducing our sponsors. So first is Jeremy. Jeremy is a Development Manager with Doghouse Agency and Technical Architect for District CMS. He's been developing and tinkering with Drupal and everything related for over a decade. He's a mentor and a big fan of open source, contributed on many open source projects including Codi, where he designed and developed the applications, web interface, the logo, and public website. Wow, that's pretty cool. There is Scott. You know he's a real developer because his entire profile is in dark mode. So Scott's with Systems Engineer with AMAZE, where he works with a global team of Kubernetes-based open source hosting platform, Lagoon. His background is in UNIX System Software Development and Administration with a focus on GNU Linux containers and Kubernetes. So welcome Scott. And next we have Nick. Hello Nick. Nick is the Operations Lead at Previous Next and Architect for the Cloud Hosting Platform Skipper. He's passionate about technology, developer with deep knowledge of running Drupal on cloud-native infrastructure. So welcome Nick. And you're the DevOps Lead, the Track Lead for this conference as well. I am, yes. Well thank you. And finally, yeah. And finally about me, I am the founder and CEO of DevPanel. It's a control panel like Pantheon, Acquia, and the like that runs all the sites in your AWS account. I'm also an ambassador with CNCF, the Cloud Native Computing Foundation. And I also run the Drupalops Meetup. You can sign up there. Okay, now about our sponsors, District CMS. So I just want to do a quick poll of how many people know of District CMS. So if you can do a quick, if you can respond to how many people know of District CMS already, that'll give us an idea of how many people know of it so we can. Okay, so it looks like a third of the people know about it. I'll end the poll and show the results. Okay, so great. So about District CMS, we have Jez here from District CMS. So Jez, you want to give us a little slides with the intro on District CMS. Yeah, absolutely. So I think nutshell, District is a council focused, local council focused distribution of Drupal. Very similar to GovCMS, but more tailored towards local council. And we're sort of trying to pull in all the things that councils are going to need, including hosting, which we'll talk about more, but also integrations and common requirements and administrative tools. So just trying to help out the councils by providing them a platform which is ready to go essentially out of the box for them. That's about it in a nutshell. Very good. Thank you. All right, I'm going to stop my screen share so we can all just talk freely here. Okay, so I'm just going to go around and ask you guys about Kubernetes, and you guys are going to be doing most of the talking. So Jez, first of all, I know you guys are running, District CMS is a pretty nice distribution. I've seen it and you want to talk about why you guys are running it on. First of all, what is your experience with Kubernetes and why you chose Kubernetes for it? Well, my experience has very much been tinkering with it at this stage. I've done a lot of playing around with Docker in the past and anyone who's dealt with web development in the last few years that that's pretty much the way to go for all aspects of development, CI and production. And yeah, I suppose we wanted something which is sort of high availability, can withstand basically anything that's thrown at it, can auto scale and repair itself, and basically compete with the best out there. So Kubernetes sort of ticks all of those boxes and it works very well with Drupal. So it's kind of why we've been sort of going in that direction. Essentially, we wanted just to compete with the best out there and provide a robust solution. Yeah, I'm going to fire up another quick poll just to see how many people actually know about Kubernetes. So if you guys can click just a quick yes or no, if you guys know of Kubernetes so we can actually talk about or go into details. And while you're taking a poll, do you want to, Scott, do you want to tell us a quick, give us a quick intro on Kubernetes? Sure. You guys do all the hosting using Kubernetes, right? Yeah, we do, that's right. So I mean, I guess there have been a few talks already that I've seen so far, people talking about containers, all the advantages you get with those, the sort of the dependency management and portability, and the fact that there's less overhead than a VM. But I guess getting that into production is the difficult bit. Because I mean, it is so easy to spin up Docker on your laptop and get something running. But then, you know, how do you make this sort of really robust? And that's where Kubernetes kind of comes in and really provides that kind of platform for doing the orchestration, helps automate sort of operations and all those sort of day two kind of production operational aspects. Yeah, it really provides just that level of reliability and that ability to just get containers off your laptop and into production. Yeah, well, a lot of folks here already know of Kubernetes, but it allows you to run containers at scale. So basically it'll take Docker containers and it'll allow us to take those and run those essentially on any cloud provider, or even on your laptops and things like that. So it's that level of that type of a technology. And Scott, you're with AMAZE. I just want to clarify that. That's right. So, Nick, you want to jump in and tell us what is your experience with Kubernetes and how you guys use it? Yeah, for sure. I might pull out a thread that Jeremy put down just before around competing with the big boys. The bigger clouds, like Kubernetes is an applications platform, applications management platform, and the APIs that it provides, it provides you everything from deployments to routing traffic to running background tasks to providing storage and then it even has an extension mechanism so then you can make those APIs look integrated into Kubernetes as well. So, like, give me a database or give me an SMTP backend. It really has raised the playing field when it comes to this and raised the bar. We're not just working off VMs anymore and we're using these APIs to deploy our applications. And that really shines with agencies. Like a lot of us, we started off with just like us, we started off with a lot of sites and they were running on VMs and it was very hard to provide HA capabilities. So then Kubernetes comes into the picture and gives us not only APIs for managing that fleet of applications, but then it also allows us to then provide a smaller footprint for HA capabilities or autoscale capabilities. When you say HA, I just want to clarify what HA is. Yeah. When you say HA, I just want to clarify HA. Yeah, absolutely. Highly available. What is HA? I don't know if everybody knows HA, so I just want to clarify that HA is high availability. Yeah, high availability infrastructure. So if we go back to my analogy, we had sites on single VMs. So that was a very standard way, low budget way to host folks sites. But if that virtual machine goes down, then it has to be nurtured and brought back up. What Kubernetes does is takes all those machines and makes it one big computer and then it means if that site goes down, it can get migrated to the next and the next. So giving you a higher availability for your application. Yeah. But yeah, I think a lot of these things, like a lot of these APIs have really raised the bar and allowed folks to build their own bespoke clouds or build their own tools on top of it. Where it would have been a very sizable investment from cloud providers in the past. Jazz, from your perspective, from a distribution provider perspective, what do you see the benefits that Kubernetes brings to you and specifically to your customers? I suppose one of the big things is due to containerization is being able to have a consistent underlying application which can then be modified per customer. And that means that we can easily deploy updates and test updates across a vast range of different clients. So I guess every site is going to be extending a core image which we're able to thoroughly test and update as required and not just update the application, but also essentially update the infrastructure. So update versions of PHP and everything else. And then have confidence, I suppose, when you're rolling that out that you're not having to do as much. There's not the overhead of having to deal with individual operating systems and individual code bases because you're kind of extending this base platform. So it benefits, I suppose, the people, the customers using it with less cost involved with maintenance. It benefits our developers as well with the less effort that's required and it benefits the application by making it more robust. So that's probably one of the key things, I think, for us. But of course, there's the other things that were mentioned as well is you never want the site to sort of go down or have any sort of availability issues. So that's another thing I suppose Kubernetes is bringing in. Yeah, no matter what quantity of traffic is hitting that site, it's just going to automatically scale and handle whatever gets thrown at it. So it's not just scaling up, it's also scaling down, right? So it's also cost benefit. Yeah, absolutely. Yeah, so rather than having, I suppose, in traditional where you've got VMs or even just bare metal, it's a very ineffective way of utilizing hardware, you're kind of slicing it up into certain sizes. And even if the application isn't using all of those resources, it's still sort of put aside. Whereas with Kubernetes, very much like how it's only using what it needs to and scale down, freeing up resources and scale up only when it needs to. Yeah, in the traditional, I think in the traditional hosting environments, the VMs and stuff, you always have to have enough VMs to accommodate all your maximum spikes, right? And versus Kubernetes. And I think that's a good benefit from that perspective that Kubernetes can bring not just to the application, the scalability, but also to the customers for the cost savings. You had also, when we were talking earlier, you had also mentioned security aspects of it. So from a security aspect, can you talk about like, what do you see Kubernetes bringing to the table from a security perspective? I suppose this sort of goes to a bit to Docker's features, but the fact that you're dealing with essentially a read-only platform with only certain parts of it, and expose this read-write, so that provides a bit of security in itself. And also, like I mentioned before, the ability to deploy security, not just sort of application updates, but security updates, whether it be at the operating system level or in the application, sort of easily and rapidly, and being able to sort of wrap some good tests into that as well to make sure that you're constantly sort of up to date. And even, yeah, having that sort of automated, so you've got sort of security tests running sort of each night or something like that, which could be benefiting potentially hundreds of customers is really good. So it's something which you can't really do without containers or Kubernetes. Yeah, I want to encourage the folks that are here to ask questions. So please go ahead and put in your questions so we can get to those two. Go ahead, Scott. Thanks. I was just going to add just on the security aspect, from an operational point of view, Kubernetes has really robust role-based access control framework that it's built on, which really is a powerful abstraction that allows you to do some really like really locked down what the sort of actions that containers and things can take on the platform. So it's not just sort of from a developer's point of view, but also from an operational side. Yeah. We've got 50 seconds left. Oh, the time goes by really fast. All right. Go ahead, Nick. I just wanted to, like, one observation with this whole conference around tying into scale is product. With VicDPC, with their distribution like Tide and Ripple, GovCMS with its distribution, and then here also with DistrictCMS and its distribution, the common underlying thread for this is that their products and they're being carved out and deployed. So I'm sure that Kubernetes is, like you've said, very integral and the ability to be able to not just scale with requests, but scale with carving out sites and carving out that repeatable product over and over again for different users, different clients. Yeah. And all the platforms, including GovCMS, they're all running on Kubernetes. So it's a solid platform to build on. Okay. Well, with that, the time went by really fast. With that, I want to thank you all. And hopefully the folks here learned something about Kubernetes and feel free to reach out to the panelists if you have questions. So thank you all. Take care. Thanks. Bye.