text stringlengths 0 1.8k |
|---|
• Discussion of Erlang VM's just-in-time compiler and perf.maps implementation |
• Comparison view feature in Parka, with interpretation of results regarding CPU cycles and observations of stack traces. |
• Discussion of color scheme for visual representation |
• Attempt to diagnose an issue with Parka Agent symbolization, specifically a memory address that doesn't match any executable code |
• Investigation into procfs and process maps to understand memory-mapping behavior |
• Theoretical explanation of potential issues with stack trace snapshots in eBPF |
• Decision to seek further expertise from Lukas Larsson on Erlang runtime behavior |
• Discussion of using Crossplane to provision a Linode Kubernetes cluster for Changelog.com setup |
• Discussion about an upcoming Easter Egg in a project |
• Review of control plane and Kubernetes cluster versions (K 1.3.1 and patch updates to 1.3.3) |
• Terrajet setup and requirements for Crossplane version (version 1.3 sufficient) |
• Pairing session on setting up a new repository using the Provider Jet template |
• Troubleshooting issues with Terraform provider source and Terraform download name in the Docker file |
• Discussing a GitHub issue with a Linode Terraform provider |
• Resolving an issue with the provider's version and import path |
• Understanding how to set up credentials for the Linode provider in a Terraform configuration |
• Introduction to Terrajet, a code generator that creates Crossplane providers from Terraform providers |
• Explanation of how Terrajet was used to create a Linode provider for Crossplane |
• Discussion of the number of providers generated with Terrajet and where they can be found |
• List of new providers added to Crossplane, including Equinix, Exoscale, and Jet Linode |
• Discussion on TerraJet's ability to handle large numbers of CRDs (custom resource definitions) with APIs |
• Introduction of a new provider for AWS that has 765 CRDs |
• Explanation of how a Crossplane provider was added in just 12 commits |
• Announcement of upcoming changes for Terrajet, including stabilized API groups and commercial WebHooks |
• Demonstration of how easy it is to create a new Crossplane provider using TerraJet |
• Installation of Crossplane and the Linode provider in production |
• Explanation of how small images can be used to pull larger images with metadata |
• Crossplane used to provision a new Linode Kubernetes Engine (LKE) cluster |
• The CRD (Custom Resource Definition) in Linode Jet Crossplane IO v1 Alpha 1 group is used for provisioning clusters |
• Terrajet uses Terraform's tfstate and exports it as a secret, which is then decoded by Crossplane to generate the kubeconfig |
• The goal is to create a self-updating, self-provisioning system where Crossplane can provision resources within the cluster without needing external kubeconfig |
• If a resource (in this case, the cluster) is deleted, Crossplane will reconcile and try to recreate it after a 1-minute wait period |
• Crossplane recreates a cluster and its nodes after it is accidentally deleted |
• Composite resources allow for the creation of multiple resources in one composition |
• The "batteries included" concept allows for installing base system components with a single composition |
• Compositions can be used to define custom APIs and manage applications across multiple clusters |
• Future plans include moving Crossplane from being hosted on a cluster to being hosted on Upbound cloud, allowing for centralized management of multiple clusters and other resources. |
**Gerhard Lazu:** The first present this Christmas is a CI/CD LEGO set that Changelog.com is already using for production. The entire story, including code and screenshots, are available in our GitHub repository; see pull request \#395. Our new pipeline gets coding to prod at least twice as fast as before, and you can ... |
Since we recorded this, we made it over a minute quicker, which is a big deal when everything used to take less than five minutes in total. And there is one more pull request open, which will improve it even more. Check the name of the person that opened PR \#401. If you like the CUE language and understand the potenti... |
So in episode \#23 we were talking to Sam and Solomon about this new universal deployment engine called Dagger - that's how it was introduced - and one of the things which I mentioned towards the end is that I would like to make it part of the Changelog infrastructure. So - hi, Joel, hi Guillaume. |
**Joel Longtine:** Hello. |
**Guillaume de Rouville:** Hi. |
**Gerhard Lazu:** How are you doing today? |
**Joel Longtine:** Good. Excited to be here with you. |
**Guillaume de Rouville:** Yeah, same for me. |
**Gerhard Lazu:** How was it for you to work on this? ...because we didn't have a lot of time, really; we tried to squeeze it around all sorts of things... What was it like the last month working on this? Tell us about it. |
**Joel Longtine:** For me, it was fun. It gave me an opportunity to dig into Dagger, in the tool, and the way that we use it, more than I had thus far. I'm relatively new to Dagger, so this was part of my learning about how our system actually works... And it was fun to kind of begin to grok how we use CUE, how we use ... |
It was also fun to work with you and Guillaume and try to figure out how to replicate what you've done in CircleCI inside of Dagger... Like you said, in part so that we could actually transition it over to GitHub Actions, or wherever else you wanted to run it. |
**Gerhard Lazu:** Right back at you. What about you, Guillaume? |
**Guillaume de Rouville:** \[03:58\] For me, it was really fun working with you. One of the things maybe, some of headaches because I didn't know CircleCI, and it's quite interesting to -- because as I was helping you... I know Dagger, I don't know this technology, so to help you port it, I had to learn a lot of things... |
**Gerhard Lazu:** That is actually my key takeaway as well. I wasn't expecting to learn as much. I was hoping, but I wasn't expecting it... And then with you two - it was great; we went on such a journey... And I think what helped is that we didn't have a lot of time, but we had long gaps between us working together. S... |
**Joel Longtine:** Yeah, I think that's one of the things that I got out of this too, was just the where we are now, and what's possible with Dagger today, and some of the difficulties that we currently have... Interesting interactions between CUE, and BuildKit, and how we're interpreting that CUE, and applying it Buil... |
So that was part of what was fun for me, was learning what our current state is, while learning where we're headed, and seeing where that delta is actually gonna be an immense improvement in the tool. |
**Gerhard Lazu:** So what does the new pipeline look like? We get and compile the dependencies, and we do this in parallel. So we do tests, and we do prod. The tests - we need to compile them, then we use a cache, and this is something to do with the volumes, like to copy all the layers. We don't need to go into too mu... |
Now, in parallel, we resolve the assets. These are like the CSS, the JavaScript, all that in development... It's like a step towards production. Then we digest them, and that is one of the inputs to the production image. |
On the right-hand side we have to compile the dependencies for production. We have the same caching mechanism, and this is like -- it's a necessary step based on the current version of Dagger, which by the way, this is something which will improve. And how do I know that? Well, Joel has been telling me all about it and... |
**Joel Longtine:** Yeah, so we're basically improving the developer experience around the low-level interactions that Dagger has with BuildKit. So we're basically changing the API to BuildKit. Right now we have kind of an implicit, kind of spread all over the place API to BuildKit, instead of our CUE packages. And the ... |
\[08:07\] So yeah, I think this is gonna get a lot better. We'll be able to actually use some of the features that we weren't able to use this time around, of BuildKit, like mounting volumes in a much cleaner way. |
**Gerhard Lazu:** Okay. And then when that is done, the last step is obviously assemble the image and push it to Docker Hub. The one step which we don't have here, and we would want, is to git commit the digest of the image that was deployed, so that we can do like a proper GitOps way, so that rather than our productio... |
**Guillaume de Rouville:** These are -- I think it's actions. An action represents a step, so in general, it lies inside a definition in Dagger... So how do you build a Dagger pipeline? You just assemble actions all together. And at run time we built a dag that's a little above. That's how you have parallel dependency ... |
**Gerhard Lazu:** Okay. What is an action? If you had to describe it, Joel, how would you describe an action? |
**Joel Longtine:** An action typically would be like a collection of BuildKit steps. So the people familiar with Docker - a specific command within a Docker file, like a copy, or an exec, an env - those sorts of things... They basically represent a stage within BuildKit. And typically, one of these actions is gonna be ... |
**Gerhard Lazu:** They all run in the context of a container, right? |
**Joel Longtine:** Yes. |
**Gerhard Lazu:** So when you think of a step, there's a container which gets created, that step runs, and there's some inputs and outputs for that one step, is that correct? |
**Joel Longtine:** Yeah, that's a great way of describing it. So you have the set of inputs - that could be a file system state, that could be a volume mount, it could be secret mounts as well... This is something that's a piece of BuildKit and some of the new features that docker build got as a result of BuildKit. |
So you have all these inputs coming into this node, which is that file system state plus some action... And then something results from that. If you're doing an echo hello to world.txt, then that new file system state has that new file on top of it. |
**Gerhard Lazu:** Right, yeah. So if you can see here, these steps - I mean, there's no cache, right? If you remember the Docker file, if you think about that, and how some of those commands could be cached, and then they're really quick... For example, the app image - you can think of it almost like a command in the D... |
\[12:14\] And by the way, this will run against any Docker daemon. That's the only requirement. You need Build Kit, and the easiest way of getting Build Kit is just in your Docker. It already has it. So there's no special CI setup required; you can run this anywhere, whether it runs the same way, whether it runs in Git... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.