text stringlengths 0 1.8k |
|---|
Some of those things are defined today, but they are gonna change, and everyone participates into that. It's not the founders dictating how things should happen. It's really a teamwork. |
**Gerhard Lazu:** \[55:43\] I really like the way you're thinking about this, I really like the description that you put out there. I know it's really difficult to capture that ideal candidate; it's actually impossible, to be honest, because there's always wildcards and curveballs... But I really like the way you went ... |
So now, as we are wrapping up, I'm wondering, as a listener, which is the most important thing for me to take away from this conversation? Solomon, would you like to start? |
**Solomon Hykes:** Yeah. I think if you are involved in DevOps and CI/CD, life is painful, but it feels like the future is exciting, and we agree. So the pain is not mandatory; it's okay to solve it. \[laughs\] I think we're just in a temporary state as an industry where it's very early and very broken, but also very e... |
**Gerhard Lazu:** I see what you mean. How about you, Sam? |
**Sam Alba:** Well, I totally agree with Solomon, and I will just add, as an extra piece of information, that although Dagger is in closed beta right now, it's really easy to get access to it. We watch the queue pretty carefully every day and make sure that people are not waiting too long to get access to it... So feel... |
We are also allocating time every week with the team to make sure we are reactive on people's questions and in people asking help about building the internal platform, as well. So we can help writing and implementing internal platforms using Dagger, giving advice and all of that... So feel free to join the community. |
**Solomon Hykes:** Also, if you've signed up and you're wondering why you didn't get access yet, check your Spam box... Because it's probably there. |
**Gerhard Lazu:** As for my takeaway - we missed Andrea. We hope he gets better... And I'm looking forward to all four of us getting together soon, maybe after I have set up Changelog running Dagger, and there will be some learnings... |
**Solomon Hykes:** Ooh... |
**Gerhard Lazu:** I like the sound of that too, Solomon... |
**Solomon Hykes:** Let's see if you're still happy to talk to us after that. |
**Gerhard Lazu:** I'm pretty sure I will. There's something there. But thank you very much for joining me. This was a great pleasure, and I look forward to next time. |
**Solomon Hykes:** Thank you. |
**Sam Alba:** Thanks so much. |
• Marques is still involved with Crossplane, but not part of the current podcast |
• The version of Crossplane in November 2019 was 0.5.0, and now it's on 1.3.0 |
• There have been over 1,800 commits since 0.5.0 from 24 contributors |
• The user experience of Crossplane has changed significantly, with more flexibility and power in defining compositions and abstractions |
• Compositions are a way to combine resources to satisfy abstract types, and can be combined within each other |
• Configuration packages declare dependencies on providers and other configurations, allowing for the creation of complex platforms |
• Defining abstractions in Crossplane and enabling flexibility for users to define their own |
• Discovering and sharing abstractions through registries and repositories |
• Packaging and sharing of abstractions using OCI-compliant registries |
• Building a registry with rich discoverability features by Upbound |
• Creating a directed acyclic graph (DAG) to resolve dependencies and conflicts between configuration packages |
• Importance of Crossplane in providing a unified API for infrastructure management |
• Evolution of the story behind Crossplane, from storage orchestration to dynamic provisioning of various infrastructure resources |
• Business value of using Crossplane in shared services infrastructure platform teams and application teams |
• Challenges of managing infrastructure across different cloud services and providers |
• Overview of Crossplane's value proposition for building customized infrastructure platforms |
• Importance of discoverability and ease of use in onboarding with Crossplane |
• Role of Upbound Cloud in providing additional features and functionality beyond the open-source version |
• Reference platforms and documentation available to help users get started and learn more about Crossplane |
• Crossplane abstractions for defining entire infrastructure setup |
• Linode provider exists and can be used with Crossplane |
• Integrating CDN (Fastly) with Crossplane as a resource |
• Helm and Kubernetes providers available in Crossplane |
• Template or configuration package for deploying Phoenix web app possible through Crossplane registry |
• Relationship between Crossplane and Argo CD, including using GitOps to provision infrastructure and applications |
• Two options for managing control plane: running Crossplane on premises or using Upbound Cloud's hosted instance |
• Issues with Kubernetes are not relevant as long as Crossplane is always available and healthy. |
• The value proposition of Crossplane lies in its decoupling from infrastructure management, allowing users to focus on other tasks. |
• A hosted control plane is important for provisioning infrastructure and ensuring infrastructure health. |
• Automating infrastructure management through managed services can free up teams to work on more complex and interesting problems. |
• Crossplane's goal is to automate tedious tasks, not eliminate jobs, but rather enable teams to focus on higher-level tasks. |
• Open sourcing and community development for Crossplane |
• Extending Crossplane through APIs and providers for multi-cloud support |
• Comparison with Terraform, including differences in active reconciliation and permissioning at abstraction level |
• Crossplane's composition model and its benefits for infrastructure management and isolation |
• Hack week results, including new provider developments and tooling enhancements |
• Development of tools for integrating designers into the app development process |
• Hack week project: k8s container registry, allowing direct image pushing into Kubernetes without an external registry |
• WebAssembly and browser-based OCI image building |
• Community growth and contribution to Crossplane.io |
• Future vision of infrastructure management with higher-level abstractions and control planes |
**Gerhard Lazu:** This is another KubeCon 2019 follow-up, and that was episode (in Changelog) 375, when we talked with Dan and Jared about Crossplane; it was about two years ago, end of 2019. But Marques was here as well... So Jared, where is Marques? |
**Jared Watts:** Marques is actually still within the Crossplane ecosystem, which is actually pretty awesome. Equinix, \[unintelligible 00:02:57.02\] so he's over there, and still contributing to Crossplane a lot. We don't miss him too much, because we still get to see him. |
**Gerhard Lazu:** Should we have added him to this invite? Was it my fault for not adding him? I think it was, right? Marques, it's my fault. |
**Jared Watts:** Yeah, we definitely miss him on this episode here, but you could probably get him on a podcast that's more focused on what Equinix is doing as well too, specifically. |
**Gerhard Lazu:** Okay, it's great to know that I'm not the only one thinking that. That was like my follow-up thought; that's great, I love that. Okay, so many things happened since 2019... 2020 was a very interesting year, from so many perspectives... But let's just think about Crossplane. I would like to focus on th... |
**Dan Mangum:** That is a hard question, and my memory must not be that good. I would guess somewhere around 0.10, but that could be way off. |
**Gerhard Lazu:** Jared, what do you remember? |
**Jared Watts:** Yeah, I think Dan you're pretty accurate there. It was either like 0.8, 0.9 or 0.10 or so. Definitely not 1.0 yet, I know that for sure. |
**Gerhard Lazu:** \[04:09\] So before I checked, the only thing that I knew, it was pre 1.0. That's the only thing that I remembered... Because I checked, I know that it was 0.5.0. You'd just cut that a few days before KubeCon. |
**Jared Watts:** That early? |
**Gerhard Lazu:** Yeah, that early. So what version are we on now, just so that listeners have a point of reference. |
**Dan Mangum:** We're now on 1.3, and we have an official support policy as well for maintaining older branches... So our active branches right now are 1.1, 1.2 and 1.3. |
**Gerhard Lazu:** I love that. We'll come back to that later... But I still want to continue with this train of thought, 0.5.0, and 1.3.0. I did a GitHub Compare to see how many commits there have been between 0.5.0 and the latest tag. Do you wanna guess how many? |
**Dan Mangum:** Oh, I would say over a thousand, probably... |
**Gerhard Lazu:** Jared, what do you think? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.