text stringlengths 0 1.8k |
|---|
• instructions on how to use the ProviderJet template to create a new repository |
• Specifying provider name lower and upper case in a command |
• Replacing all instances of template with the specified commands |
• Understanding Terraform provider source and download name in Docker files |
• Clarifying that Terraform provider source and download name are not the same thing |
• Identifying the correct URL for the Linode Terraform provider |
• Finding the changelog for the Terraform provider Linode |
• Examining GitHub as a potential example of the V4 version |
• Discussion about determining if a Linode provider is using an old version |
• Importance of checking the Git repo for the Terraform provider to confirm version |
• Realization that the V4 version is available as a Go package and can be imported |
• Identifying the line in the Go module that needs to be updated or replaced |
• Understanding how to use replace statements in the Go module to update dependencies |
• Setting up credentials for Linode using environment variables and CLI tokens |
• Clarification on where the Linode token is obtained |
• Key username and its origin |
• Inv token and its use |
• TerraJet, a tool for utilizing the Terraform community's work in Crossplane |
• Creating a Linode provider using TerraJet and Terraform |
• TerraJet's design and functionality as a code generator and controller |
• The history of Marcus's involvement with Terraform and Linode |
• The current state of providers generated with TerraJet, including AWS, Azure, GCP, and others. |
• ProviderJet AWS has 765 custom resource definitions (CRDs), which is too many for the Kubernetes community |
• Another provider was added in the last week, which generated a ProviderJet Linode with 12 commits to Crossplane Contrib |
• The previous Linode provider in Crossplane had not been maintained and may not work with the latest versions of Crossplane |
• A single resource (LKE cluster) is currently available for provisioning in TerraJet, but additional resources are needed |
• Future plans include announcements about stabilized providers (AWS, Azure, GCP), versioned resources, and conversion webhooks |
• Implementing a cross-plane provider using TerraJet |
• Ease of use with TerraJet compared to other implementations |
• Example of a community-written provider (Exoscale) in 6 hours |
• Adding an instance resource to JetLinit provider as simple as 10-15 lines of code |
• Step-by-step process for creating a Crossplane Linode provider |
• Installing Crossplane and the Linode provider using Helm |
• Discussion of crossplane RBAC manager and pods |
• Using Canines as a CLI for quick tasks |
• Creating new clusters with Linode jet crossplane IO V1 alpha 1 group |
• Provisioning new clusters using crossplane LKE |
• Overview of how crossplane continuously reconciles requests |
• Creation of a new LKE instance and cluster in Linode and Kubernetes |
• Obtaining kubeconfig for the newly created cluster |
• Discussion of using Crossplane to target a Kubernetes cluster without exposing the kubeconfig |
• Exploring self-automated system where Crossplane provisions resources and updates application |
• Demonstration of deleting a cluster and observing the controller's behavior in reconciling the absence of the cluster |
• Explanation of how the controller will try to create a new cluster if it detects that one is missing, with a wait period of up to 1 minute |
• Discussion of a custom resource that triggers a Kubernetes event |
• Cluster creation and reconciliation process |
• Issue with Linode node pool being deleted when cluster was deleted from UI |
• Introduction to composite resources and their benefits in managing multiple resources as one |
• Explanation of how composite clusters can recreate nodes, installations, and other dependencies automatically |
• Example scenario where accidental deletion of a cross-plane cluster led to discussion on the importance of automated recreation of dependent resources |
• Idea of improving current functionality by installing base components and using two compositions with XRDs to define APIs for multiple resources. |
• Clusterscoped does not have any namespaces |
• Creating a composition with base system components for a cluster |
• Using a central production cluster with its own claim, similar to PVC, and referencing it from other namespaces via XRD |
• Publishing a new API instead of manually configuring cloud-specific fields |
• Moving Crossplane from being hosted on the current cluster to a seed cluster on a cloud like AWS or GCP |
[0.36 --> 5.90] You are listening to ShipIt, a podcast about operations, infrastructure, and Christmas |
[5.90 --> 6.36] presents. |
[6.82 --> 11.92] I'm your host, Gerhard Lazu, and today we have a special Christmas episode, which sums |
[11.92 --> 15.18] up two months of very early mornings and a few late nights. |
[15.78 --> 21.58] We have pull request 395, a CICD Lego set with Guillaume de Reville and Joel Longtime, |
[22.46 --> 28.70] continuous CPU profiling with Frederic Brancic, which is PR396, as well as auto-restoring |
[28.70 --> 33.04] Kubernetes clusters with Dan Mangum and Muvafak Onush, PR399. |
[33.84 --> 38.62] While I initially intended us to have five Christmas presents in total, only three got |
[38.62 --> 39.38] delivered in time. |
[39.84 --> 44.16] We planned, worked hard, and eventually shipped the best version just in time for Christmas. |
[44.88 --> 49.76] My hope is that the latest additions to our changeup.com GitHub repository will help you |
[49.76 --> 52.36] just as much as they will help our 2022 setup. |
[53.10 --> 54.24] Merry Shipmas, everyone. |
[54.62 --> 58.46] Big thanks to our partners Fastly, LaunchDarkly, and Linode. |
[58.70 --> 60.56] Thank you for the great band with Fastly. |
[60.80 --> 62.78] You can learn more at Fastly.com. |
[63.32 --> 67.44] Ship new features with confidence by getting your feature flags powered by LaunchDarkly.com. |
[67.92 --> 70.92] And thank you, Linode, for keeping our Kubernetes fast and simple. |
[71.38 --> 75.28] Run your setup as we do via linode.com forward slash changelog. |
[75.28 --> 86.64] We are going to ship in three, two, one. |
[86.64 --> 107.18] The first present this Christmas is a CI CD Lego set that changelog.com is already using for production. |
[107.18 --> 114.16] The entire store, including code and screenshots, are available in our GitHub repository, cPullRequest395. |
[114.68 --> 120.72] Our new pipeline gets coding to prod at least twice as fast as before, and you can see it running in GitHub Actions. |
[121.40 --> 128.68] Since we recorded this, we made it over a minute quicker, which is a big deal when everything is take less than five minutes in total. |
[128.68 --> 132.90] And there is one more pull request open, which will improve it even more. |
[133.52 --> 136.26] Check the name of the person that opened PR401. |
[137.08 --> 142.10] If you like the queue language and understand the potential of direct-to-cyclical graphs for pipelines, |
[142.60 --> 145.84] this present will take your CI CD to a whole new level. |
[145.84 --> 154.08] So in episode 23, we were talking to Sam and Solomon about this new universal deployment engine called Dagger. |
[154.44 --> 155.42] That's how it was introduced. |
[156.08 --> 163.02] And one of the things which I mentioned towards the end is that I would like to make it part of the changelog infrastructure. |
[163.56 --> 164.70] So, hi, Joel. |
[164.88 --> 165.62] Hi, Kiong. |
[166.32 --> 166.58] Hello. |
[167.26 --> 167.80] How are you? |
[167.84 --> 168.52] How are you doing today? |
[168.78 --> 168.98] Good. |
[169.16 --> 170.06] Excited to be here with you. |
[170.52 --> 171.26] Yeah, same for me. |
[171.26 --> 173.80] How was it for you to work on this? |
[173.92 --> 178.94] Because we didn't have a lot of time, really, and we tried to squeeze it around all sorts of things. |
[179.26 --> 181.82] What was it like the last month working on this? |
[182.42 --> 183.12] Tell us about it. |
[183.72 --> 185.96] For me, it was fun. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.