 Hey folks, it's Jim. Good morning Jim, how are you? Very good. Hey Robert. Hi, and Kirsten here from Red Hat. Hi Kirsten. Hey. Hi Kirsten. Nice to meet you. Nice to meet you. Looks like we may not have much of a quorum today, huh? I suppose it's early. Right. Yeah, I didn't have too much to cover either. Just, uh, I can give a few updates in terms of PRs and changes were made on the policy reports. Seems reasonable. I know Jay is on vacation. She's on this week. She often joins. All right, let's wait. We can give him a couple more minutes and then we'll just go through. I think at least what I can cover what I have. Um, Robert, are you. Set up or are you, can you maybe take the notes and update the doc for today? Thank you. Hey folks, we're just waiting a couple of minutes to let more people join and we'll get started. See a couple more people. All right. So I think we're at five minutes past. Should we get started? Robert Erica, any. Yes, definitely. I don't think I ever got a response from the network policy people unless someone hears on the call. I don't think I recognize most people. Uh, do we have other items on the agenda? So the only other item I mentioned towards the top of the hour that I could quickly cover is just some, um, pull requests which, uh, were merged in this last couple of weeks. So I'll just give a quick update on the policy report, CR. Um, and then I think Kirsten said, uh, Jaya is out this week. So I don't think we have any updates from her or her team. Um, yeah. So that's, I think those were the only items on the agenda. Well, does anyone else have anything? Sorry. I missed the first five minutes. All right. Well, maybe short meeting today. So go ahead, Jim. Okay. Um, all right. So in terms of the policy, you know, report and the custom resource definition, a few, the small changes that were introduced that I can quickly highlight. Um, one is in the, in the policy report itself, if you recall, there was a scope selector. And at one point this got dropped because we didn't have a good use case for it. But then as we have been implementing the report in various places, uh, one of the use cases that came up is if there's, um, you know, like if you're running an application from a helm chart, uh, typically there's some standard labels like, uh, application name, application instance. Um, those are recommended labels and the helm automatically injects those. So one of the use cases was to use the selector to actually highlight that the policy report was for a workload run, um, through a helm chart, right? And that seemed like a pretty nice way of tying in or selecting a set of, you know, resources that belong to a workload. So we brought back the, the scope selector. So that's this field, uh, which is now in the policy report. Um, so that, that's part of the CR. And another change that, uh, you know, somewhat related, but also in the policy report result instances, um, there, we have a resource selector. So the idea is the report could, could, um, you know, be built for a group of resources, but then each result may be specifically pointing to one resource within that group. Um, so the, uh, previously what we had was just a resource with an object reference, but the feedback was if the same result, um, so like if the same violation applied to five different resources, there was a lot of duplication in terms of the, um, the type of data which we wanted to show in the policy result element, right? So like the rule details, the message, things like that. So to try and keep things more, more condensed, uh, what we did was we changed this resources field to be a list. So that way you could have one result element, which has a list of resources, or you could also use a selector here if labels are applicable. Um, but in some cases it seemed like these could be heterogeneous resources where labels may not apply. So just having a list provides a lot of flexibility and that way a particular result, like for example, if there's a violation with like some, you know, let's say a pod, uh, is running as root user, you could have a list of pods in, in that namespace which violate that particular policy rule. So just helps keeps the report more condensed and cleaner. Uh, so that's, that was another change that was introduced. So those were the two, two main things, uh, just looking at the list of issues. I haven't seen any updates. Uh, I know we discussed some of these with, uh, JL, last time, but I think we need to, uh, figure out what we do with the time fields. And then again, if we want to put more data in the policy status, like a reason or remediation and some more, um, uh, more information there. So yeah. And then adding things like again, category, severity, et cetera. So we can, uh, quickly close those as we see examples. So those are the main updates from my side. Um, uh, also like in terms of using the report in more places, um, we need to decide, uh, how we, you know, we had talked about, uh, whether you picking something like Falco or also, uh, potentially coup bench. And then starting to look at transforming or, uh, reporting the, the policy, creating the policy report from those tools. So I think, uh, those would be good to revisit and see how we can, you know, uh, start using the standard report structure there. And I don't know what Rackham, Erica, if you know if there's any updates or from folks who have been using this, uh, or any examples that we can highlight and include in the repo. I'm not sure I have any, maybe Kirsten, do you have any updates? I don't at the moment. I know that, um, so I think without Jaya here, uh, and, and we don't have Oz either. So, so it may be, um, that we'll need to wait for feedback there. Okay. Yeah. Uh, do we, so we should reach out to some people. Um, I don't know what the good, like deadline for that would be or anything. My schedule is a little wonky these next few weeks. So I don't want to overly promise. Yeah. Maybe. Erica, if you want to start like a thread on Slack, maybe that's the best way to communicate. I know Oz was on there. I haven't, I don't have the. Usernames for some of the other folks from the team, but, uh, perhaps, uh, we can just kick off some discussions on Slack and that way, uh, get, uh, quicker feedback than waiting for the next call. That sounds good. And, and I don't do, we want to, you know, paying, uh, folks like Liz Rice from Aqua. I mean, I know they joined one of our calls. Um, right. And then, uh, who else? Uh, It's just, does Sistig ever join any of these calls? Just, I'm wondering, cause you mentioned Falco. That's all. I, I know that we had some folks on the list. I know some of the folks who were on the list have transitioned into different roles and companies. So. Well, so maybe that's, like you say, Slack will hit whoever is really interested in paying attention. Or if you do email these people, they'll be able to tell you who's transitioned. Right. And they might have. Tends to be informal, which is, which is why the, I think the Slack chat in this case will probably be a good, a good one. One of these things. I have to figure out how to get myself signed into the Slack. I haven't figured out what is gating me. So, yeah. Erica, maybe I'll ping you. Maybe you can help me. I can do my best. Okay. Thanks. Yeah, I think there's a, I don't remember the process. It was a while ago that I signed up. I. I think it was fairly straightforward though, once you find the link to sign up on. I found something in it. And it was like, I had to add anyway, I'll try again. Okay. Christina, I'm not sure if I've seen you on our, some of our prior calls, but would love to. My first time. Oh, welcome. Who are you with and, you know, any particular interest in terms of topics, et cetera, that we can. So other moments, finding my feet around the NCF. Okay. I with red hat. Okay. So I, I'm just generally interested around. And it's, it's progress towards. Security. Awesome. Yes. So certainly a lot of work on discussions we've been having. So Erica. And Kirsten are also from, you know, red hat or IBM. And so you guys probably know each other then or. Yeah. Yeah. And then she and I have worked with some. She works pretty closely with some of our customers who are security focused. So she's coming from that angle. And I don't know what that Erica and Christina have met. I don't think we have. Yeah, I don't think so. Well, welcome. Thank you. Great to have more perspectives. I don't know if you're also interested. Yeah. So we have six security chat later today as well. If that's something you're interested in, you can check out. So it depends on, so it depends on how later, if it's an hour later, that's probably okay. If it's three to four, I'm UK time. So it is going to be quite difficult managing it with everything else. Two hours. It looks like. Yeah. Yeah. Yeah. Yeah. Yeah. You can link to it or I'll find it. What's it called? Sig. Sig security. Yeah. I'll see what I can do. Okay. Yeah. And you're our focus has been so there's a couple of projects. We've been working on the policy report, which I was just sharing some updates briefly on that's been one of the topics. Yeah. Yeah. Yeah. So at this point, you know, what we're most interested in is getting more use cases, getting more traction on the policy report. And then that's some point we'll go back to a couple of the six, say God, then six security. And. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. So at this point, you know, what we're most interested in is getting more use cases, getting more traction on the policy report. See how we can, you know, publish this as a more standard resource that could, that can be adopted. So. If you think of any other use cases, any, any other teams that might be interested in creating and reporting in a standard manner. And could be run time policies, could be admission controls, or any other, I guess. Incidents of interest to her. events in the cluster is what we're capturing here. Yeah, I've got, so I've got an idea, but I'm not entirely sure if this is relevant, right? No, it's not relevant to Kubernetes, it's more relevant to OpenShift. So I'll keep that one to myself because of the OAuth server. So we'll keep that one. Sure, or it might be that we can, we can chat with Erika and see whether it's useful for the OAuth SIG. And I added the link to our GitHub repo so you can browse through there and see some of the current activity. Thank you. Sure, you're welcome. All right, so I think if there's nothing else, then we can probably wrap early today and let's start some, Kirsten, if you have any issues on the Slack side, feel free to reach out to me or just email me. I think you have my email, right? We can help get you set up and then let's get some of the others from the team also on there so we can have some discussions in between meetings. Sounds good. Great. Thanks everyone. All right, take care. Bye. Bye. Bye, thanks. Bye.