text stringlengths 0 1.8k |
|---|
[1352.32 --> 1353.28] It's been an absolute pleasure. |
[1353.62 --> 1353.94] Thank you. |
[1354.10 --> 1354.94] Thank you for having me. |
[1370.62 --> 1374.40] This episode is brought to you by our friends at Incident.io. |
[1374.80 --> 1379.06] Every software team on the planet has to manage incidents and a very large percentage of those |
[1379.06 --> 1381.00] teams are using Slack to communicate. |
[1381.18 --> 1382.16] That includes us. |
[1382.48 --> 1387.42] With Incident.io, you can create, manage, and resolve incidents directly inside Slack. |
[1387.70 --> 1388.62] Here's how it works. |
[1388.88 --> 1390.96] Head to Incident.io and sign up for free. |
[1391.18 --> 1392.60] Then add it to your Slack. |
[1392.76 --> 1396.62] From there, you have a brand new incidents channel where all incidents get announced. |
[1397.00 --> 1399.56] Use the slash incident command to create and manage incidents. |
[1399.98 --> 1404.36] This command lets you share updates, assign roles, set important links, and more, |
[1404.68 --> 1406.54] all without ever leaving the Incident channel. |
[1406.94 --> 1411.94] Each Incident gets their own Slack channel plus a high-res dashboard at Incident.io |
[1411.94 --> 1414.42] with the entire timeline from report to resolution. |
[1414.96 --> 1418.16] Get everyone on the same page from the moment they join the Incident and help stakeholders |
[1418.16 --> 1419.02] stay in the loop. |
[1419.38 --> 1423.52] Add Incident, IO to your Slack today and prove to yourself and your team that they have everything |
[1423.52 --> 1425.12] you need to streamline your incident management. |
[1425.60 --> 1428.02] Learn more and sign up for free at Incident.io. |
[1428.32 --> 1429.38] No credit card required. |
[1429.38 --> 1431.38] Again, Incident.io. |
[1444.50 --> 1451.24] So, out of everyone that I spoke to so far, Dan, you're the first one that you're at KubeCon |
[1451.24 --> 1451.92] in person. |
[1452.30 --> 1455.18] So, tell us what's it like for everyone that couldn't make it. |
[1455.30 --> 1456.04] Yeah, absolutely. |
[1456.04 --> 1460.70] Well, first of all, it is incredibly nice to be able to see folks that I haven't been |
[1460.70 --> 1464.76] able to see in a number of years and also some folks I've never met in person before. |
[1464.96 --> 1469.94] So, regardless of the whole situation with COVID and all, I definitely feel very privileged |
[1469.94 --> 1472.06] to be here and don't take that lightly. |
[1472.38 --> 1478.00] In terms of, you know, comparing to previous KubeCons, I've actually been mostly to virtual |
[1478.00 --> 1481.70] KubeCons just because, you know, we've been in this pandemic stage for so long. |
[1481.70 --> 1486.86] I did have the opportunity to go to KubeCon in San Diego in person, which obviously you |
[1486.86 --> 1489.80] remember because we recorded a great podcast episode there. |
[1490.08 --> 1491.76] And it definitely feels different from that. |
[1491.90 --> 1496.98] The CNCF has done an incredible job of making this a very safe environment with their health |
[1496.98 --> 1497.94] and safety protocols. |
[1498.18 --> 1502.88] So, that's been very impressive in terms of spacing, in terms of making sure everyone's |
[1502.88 --> 1508.08] comfort levels with being close to people or being in proximity of others is adhered to. |
[1508.22 --> 1509.60] That's been very impressive. |
[1509.60 --> 1514.30] There's absolutely less attendance than there has been at past KubeCons. |
[1514.66 --> 1518.84] And one of the things that I've noticed is there's a lot more just community members |
[1518.84 --> 1522.84] here rather than end users, I'd say, which has pros and cons, right? |
[1522.86 --> 1526.24] It's always really nice to talk to end users because they're the folks that really motivate |
[1526.24 --> 1530.18] product roadmaps and CNCF project roadmaps and that sort of thing. |
[1530.24 --> 1532.22] And it's really valuable to hear from them. |
[1532.36 --> 1535.68] But it's also really nice to be able to collaborate with other projects. |
[1535.68 --> 1540.18] So, I've been spending a lot of time just talking to other maintainers, talking to other companies, |
[1540.60 --> 1544.12] seeing what they're up to, talking about different integrations that could be possible. |
[1544.54 --> 1549.98] So, it's a different feel, but its unique atmosphere, I think, is really advantageous in some respects. |
[1550.54 --> 1551.50] That sounds great. |
[1551.60 --> 1553.62] So, how did you make it work, Jared? |
[1554.04 --> 1555.78] Because I know that you're remote, right? |
[1555.78 --> 1557.94] But you have the virtual office hours. |
[1558.14 --> 1559.34] How did you make those works? |
[1559.44 --> 1560.16] Did they help? |
[1560.68 --> 1561.84] How did that feel for you? |
[1562.08 --> 1563.38] Yeah, it's actually kind of interesting. |
[1563.50 --> 1566.24] I was just thinking about it and reflecting a little bit while Dan was answering. |
[1566.56 --> 1568.60] And so, you know, actually, so I live in San Diego. |
[1568.88 --> 1574.02] And so, I'm actually fairly close to, in proximity to where KubeCons is being held in Los Angeles. |
[1574.52 --> 1578.14] But then my schedule ended up getting booked up with so many virtual commitments |
[1578.14 --> 1583.70] that it didn't make it super possible to go up there and then do everything, you know, all at the same time. |
[1583.70 --> 1589.20] And so, yeah, so it's, I mean, the CNCF does a good job with organizing this and making all the virtual events possible |
[1589.20 --> 1594.18] to kind of be inclusive and make sure that as a hybrid event, people are getting opportunities to participate |
[1594.18 --> 1597.74] if they're either in person, but also back at home, wherever that may be. |
[1598.06 --> 1602.92] So, the virtual office hours that we ran yesterday was quite successful with, you know, a lot of people joining in, |
[1603.26 --> 1604.86] a lot of questions being asked also. |
[1605.06 --> 1611.34] And so, you know, the ability to connect with people virtually and not feel left out from the in-person event running on |
[1611.34 --> 1615.92] is, I think, actually working quite well and everyone's still feeling, as far as I can tell, |
[1616.04 --> 1619.28] pretty connected and getting lots of chances to participate, which is really good. |
[1619.58 --> 1623.94] Were there any questions that really stood out to you, something like really memorable that made you think |
[1623.94 --> 1626.52] or something really interesting that you weren't expecting? |
[1626.90 --> 1628.80] There were a lot of good questions yesterday. |
[1629.16 --> 1634.04] One of the things that's kind of, I've realized too, is that while I'm presenting and questions are flooding in, |
[1634.14 --> 1639.16] it's really, really good to have multiple people there to be able to support and answer questions |
[1639.16 --> 1642.22] and do that asynchronously in addition to the ones we answer on camera, |
[1642.28 --> 1645.74] because there's just too many questions to answer on camera and also get through all the material. |
[1646.22 --> 1649.12] So, you know, I was trying to focus on delivering the material, |
[1649.22 --> 1651.30] why everyone else was attacking all the questions. |
[1651.72 --> 1655.64] So, Dan, do you remember any specific ones that, you know, you were jumping on while I was presenting? |
[1656.08 --> 1656.62] Yeah, absolutely. |
[1656.82 --> 1659.16] Like you said, there were a lot of really great questions. |
[1659.32 --> 1664.70] The ones that really stuck out to me, and this is something that's kind of been a point of interest for folks |
[1664.70 --> 1668.52] throughout all of CrossPlan's lifecycle, and that's handling of sensitive data. |
[1668.52 --> 1672.78] So with CrossPlan, we have two major kind of sources of sensitive data, |
[1672.92 --> 1676.60] one of them being credentials to talk to cloud providers or external APIs, |
[1677.18 --> 1681.66] and the other being credentials to communicate with the infrastructure that you're provisioning |
[1681.66 --> 1683.36] using those external APIs. |
[1684.02 --> 1689.48] And so some of the progress we've made around being able to supply external API credentials |
[1689.48 --> 1694.46] via secret stores like Vault and injecting those into the file system of our providers |
[1694.46 --> 1699.60] and that sort of thing, as well as some of the proposals around how we publish connection details |
[1699.60 --> 1701.06] to that infrastructure that comes up. |
[1701.22 --> 1706.42] It's always really exciting when you go from one conference to, you know, the next iteration of it, |
[1706.60 --> 1710.90] and you have some solutions for the folks that had questions about that the previous time, |
[1710.90 --> 1715.10] or you at least have something where you have a design for what it's going to look like. |
[1715.10 --> 1719.56] So those kind of topic areas around security and credentials and that sort of thing |
[1719.56 --> 1722.60] was something that really stuck out to me in the questions that we got. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.