text stringlengths 0 1.8k |
|---|
[2263.04 --> 2265.94] the actual resource that you're creating in your Kubernetes cluster. |
[2266.66 --> 2270.22] And so generally what folks will do is they'll go through that process and they'll start to |
[2270.22 --> 2271.60] kind of see the bigger picture. |
[2272.00 --> 2277.62] And then honestly, a lot of the way that folks continue to dive into the project is number |
[2277.62 --> 2281.44] one, looking at some of the content that we put out there on YouTube and that sort of |
[2281.44 --> 2281.70] thing. |
[2281.92 --> 2286.14] Victor joined Upbound and the Crossplane community and has been putting out some great content |
[2286.14 --> 2286.92] around that. |
[2287.28 --> 2292.26] And then also just our Slack workspace has exploded over the past six months or so. |
[2292.26 --> 2296.88] And there are countless folks in there just asking questions, learning more about it. |
[2297.16 --> 2302.58] One of the really rewarding things to see as a maintainer is community members helping other |
[2302.58 --> 2303.40] community members. |
[2303.86 --> 2307.20] Because, you know, earlier on, it was mostly community members coming along. |
[2307.20 --> 2310.12] And asking maintainers questions and then answering those. |
[2310.20 --> 2311.42] And that didn't scale super well. |
[2311.90 --> 2316.94] Now that we have end users helping each other use Crossplane and talking about what features |
[2316.94 --> 2320.76] they'd like to see, what things work for their organizations, how that would affect others. |
[2321.16 --> 2325.18] That's really where we see folks really get into the weeds of Crossplane and start to understand |
[2325.18 --> 2328.36] how they can extend it for their specific use cases. |
[2328.66 --> 2330.34] Yeah, building that community is super important. |
[2330.46 --> 2335.06] I know that is such a huge and important part of what you do every day, right? |
[2335.06 --> 2339.54] I mean, I see you everywhere, Twitter, YouTube, Slack, so much activity. |
[2339.76 --> 2341.22] And now that will only pick up. |
[2341.66 --> 2342.04] And you're right. |
[2342.10 --> 2346.60] There's a point where people have to start helping one another out because it can't be |
[2346.60 --> 2348.12] on you, the project maintainers. |
[2348.38 --> 2352.48] So I think that is one important thing for people listening to this to try and help others. |
[2352.48 --> 2356.76] If you're into Crossplane and you know something, you know, help your friend that you may not |
[2356.76 --> 2359.20] know yet, but get to know him or her. |
[2359.20 --> 2362.30] And yeah, see how you can help one another out. |
[2362.60 --> 2367.88] One thing which I would like to say is that the GCP provider, there was a very recent version, |
[2368.02 --> 2369.66] I think 0.18 or 0.19. |
[2369.76 --> 2370.70] I can't remember exactly. |
[2371.12 --> 2373.12] That upgrade was very interesting. |
[2373.64 --> 2377.94] And I think that those things will become when you deprecated the GKE cluster for the cluster. |
[2378.48 --> 2381.58] So there was like an export to be made and then reimport to be made. |
[2381.74 --> 2383.34] There was a fairly involved process. |
[2383.34 --> 2387.46] So I'm wondering that going forward, is that something that you're thinking about, Jared, |
[2387.60 --> 2390.02] in terms of how to make it smoother for users? |
[2390.28 --> 2396.00] Because if people will keep spending a lot of time on figuring that out or even performing it, |
[2396.02 --> 2398.98] to be honest, what I've done, I just didn't bother with the upgrade. |
[2399.10 --> 2402.62] I deleted all the clusters, remove, reinstall because it was too involved. |
[2402.72 --> 2407.34] I tried it, but like step number five or six, I said, it's just too much work. |
[2407.34 --> 2414.16] So I'm wondering how you're thinking about the continued usage and the upgrades going forward |
[2414.16 --> 2416.96] so that users, their lives are easier. |
[2417.28 --> 2418.84] Yeah, that's a really, really good question. |
[2419.50 --> 2421.50] There's a couple of thoughts come to mind on that. |
[2421.62 --> 2424.52] First is that there was a lot of thought put into that. |
[2424.86 --> 2429.52] It wasn't an easy decision of, oh, hey, let's just make this change here and roll it out. |
[2429.78 --> 2431.68] Dan drove that effort to begin with. |
[2431.94 --> 2434.50] And so he made a proposal about it, explained it very thoroughly, |
[2434.50 --> 2441.78] and gave the entire community a sense of what the situation is with GCP having kind of |
[2441.78 --> 2445.34] beta API that some people may want to depend on and then a stable API, |
[2445.54 --> 2447.08] which other people may want to depend on. |
[2447.20 --> 2450.62] So kind of supporting two different APIs from the cloud provider itself |
[2450.62 --> 2455.32] with different varying levels of guarantees around breaking changes and things like that. |
[2455.70 --> 2458.72] So Dan did a really good job laying all that out, putting it out to the community, |
[2458.72 --> 2464.02] and then spending a couple of months actually with getting feedback and kind of understanding it, right? |
[2464.50 --> 2465.36] So that was a good thing there. |
[2465.42 --> 2468.76] And then Hassan did a really good job of writing up a migration guide. |
[2469.08 --> 2470.80] So something I learned from the Rook project, |
[2471.10 --> 2473.58] the storage orchestration for Kubernetes that I'm also involved with, |
[2473.64 --> 2476.54] is that migrations are one thing. |
[2476.74 --> 2481.08] But if you don't provide any path at all for people, then that could be a failure. |
[2481.64 --> 2485.10] And so there are some manual steps with that upgrade or the migration. |
[2485.10 --> 2489.26] And, you know, having the guide to do that, to give people the opportunity, |
[2489.26 --> 2495.16] it was something I was definitely proud that we paid attention to that and had some empathy for the community to go ahead and invest in that. |
[2495.62 --> 2498.52] And then the last comment I'll make there is that, you know, |
[2498.54 --> 2502.88] there's different levels of maturity and guarantees within the Crossplane ecosystem itself also. |
[2503.32 --> 2505.76] So Crossplane as a core project, you know, |
[2505.76 --> 2509.64] the functionality and machinery and tooling to build your own custom platforms, etc. |
[2509.64 --> 2512.86] That is at, you know, a 1.0 or 1.5 almost now. |
[2513.20 --> 2514.62] That's stable, the API there. |
[2514.94 --> 2519.66] You know, there are some guarantees around breaking changes and, you know, backwards compatibility and things like that. |
[2519.80 --> 2525.68] So we don't anticipate and haven't done any, you know, difficult migrations in core Crossplane in quite a while. |
[2525.94 --> 2530.40] And we're going to stick to that, you know, unless we do like a 2.0 and then that'll be very explicit as well. |
[2530.50 --> 2534.08] But for the providers, they are not at that same level of stability yet. |
[2534.08 --> 2539.68] So they're still in a, you know, alpha, beta sort of phase where there are going to be some of those breaking changes, perhaps, |
[2539.84 --> 2542.94] as things are being figured out and matured along the way. |
[2543.22 --> 2545.28] But you won't, you shouldn't see that in core Crossplane. |
[2545.60 --> 2550.50] It's very nice that you've laid out all that background because I remember looking at the issue that Dan opened. |
[2550.82 --> 2552.72] It was really good, like really well thought out. |
[2552.84 --> 2554.70] There wasn't a lot of engagement on the issue. |
[2554.86 --> 2556.54] Maybe that happened on Slack or elsewhere. |
[2557.16 --> 2562.84] But I really like that I could follow the trail all the way to the source and see, well, this has been happening for a while. |
[2562.84 --> 2565.28] Well, thought has been put into this. |
[2565.44 --> 2565.74] You're right. |
[2565.82 --> 2566.76] That guide was really good. |
[2566.86 --> 2567.74] Like I followed it. |
[2568.02 --> 2568.78] It worked. |
[2569.14 --> 2570.78] But I was thinking, do I really want to do this? |
[2570.82 --> 2572.40] It's like there's like too much stuff here. |
[2572.44 --> 2574.84] And I have to like, I was like step number three or four. |
[2575.24 --> 2578.36] And I still have like to continue like four others or something like that. |
[2578.76 --> 2580.78] So I was like halfway through and I thought, you know what? |
[2580.96 --> 2582.44] It would be easier to do that. |
[2582.78 --> 2589.06] What I want to say is that having gone to the end, having gone like to the latest version of the GCP provider, |
[2589.54 --> 2592.06] everything that I thought it would have, it had. |
[2592.06 --> 2597.96] So the new cluster resource behaved a lot better than the GKE cluster one. |
[2598.04 --> 2599.30] So it was worth getting there. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.