 All right then, hello everyone. It's actually really awesome to see quite a few faces here today. Thank you for finding the time to join us in this session. Today, myself and Antonia will talk about all things environmental sustainability tag. So yeah, let's get started. My name is Kristina Devojko. I'm a platform engineer at Theatre Every, a CNCF ambassador and a technical lead at the Environmental Sustainability and Technical Advisory Group. Yeah, and I'm Antonia Ditturi. I'm a consultant at Data Reply and I'm also co-chair of the Working Group Green Reviews in the Tag and Sustainability. Yeah, so I assume that some of you here may be hearing about Environmental Sustainability Technical Advisory Group or shortly, Tag and for the first time today. And I think this talk can be a great opportunity to give a quick introduction about what Tag and is about and what things are we actually doing in the tag. Our tag is quite young and it was founded a bit under two years ago in May 2022. And I think that the title for this talk actually sums up pretty well the reason behind why this technical advisory group was created in the first place. We wanted to create an arena, a forum, a place where we could gather community members from cloud native and open source community that are passionate about the topic of environmental sustainability. So that together as part of the group we could advocate for and help support and help guide on how to evaluate environmental and help guide the environmental sustainability initiatives that are going on in the cloud native and open source space so that we could identify potential initiatives and activities that contribute to reducing the energy and resource consumption and the overall environmental sustainability footprint in the space so that we could raise awareness of importance of this topic and support the existing and upcoming projects that are making impactful contributions to improve the environmental sustainability footprint of the cloud native and open source space. And one message that you will hear throughout this session and also throughout everything we do and communicate in the tag is that all we do is done publicly in a transparent and open manner and this means that everyone of you sitting here today is very much welcome to join us and contribute and just become a part of this great group. And in order to be able to expand what we do and to kind of keep the live in this group and keep all the activities that we're doing kind of going on and doing it in a healthy manner there is of course some need for some kind of structure and governance where some of the contributors to the tag can take a little bit more responsibility to ensure that we keep things happening in a healthy manner and therefore there is of course the reason to have some governance and structure in the tag. That is pretty similar to any other tags that operate under the CNCF ecosystem. So this currently illustrates how we are structured in the group, we have some overall roles like technical lead and the chairs of the tag and these are community contributors that take a bit more responsibility on kind of driving the overall roadmap and ensuring that what we do is actually in scope of our mission and goals and technical lead support kind of also more of the technical decision-taking decision-taking across the different activities we do in the tag. We also have a technical oversight committee liaison who helps us to ensure that we have an efficient communication and collaboration between the tag and the technical oversight committee and we also help the talk and kind of help them and guide them on how we can take the roadmap of the environmental sustainability initiatives in the CNCF, take it further and kind of grow it over time. And we also have the same roles in the sub-entities that operate as part of the tag like working groups and projects which we're gonna talk a bit more about shortly. And one important thing to mention is that we don't have members in the group and we believe that everyone who actively participates in any kind of activities be it technical or non-technical like joining our meetings, suggesting things that we should focus on or suggesting some changes to the existing projects or initiatives, contributing code or documentation, everyone becomes a contributor of the tag and without our great contributors, everyone who does help us be small or bigger contributions, every one of these counts and we appreciate you and we value you. I think that's important to mention. And we also have a tag ambassador role in the works. This kind of will be the role that will be the same for all the tags in the CNCF project and that has as a goal to strengthen collaboration between the tags in the CNCF, the CNCF projects and also the CNCF ambassador program. So if you would like to learn more about that, we will also share the link to the GitHub issue where it's described in more details. And that's how the current tag environmental sustainability team looks like. At this point, we don't have the project leads illustrated on this slide because we have quite a few projects that we started up very recently, right before the KubeCon and CloudNativeCon, but if you would like to learn more, we also have a separate governance information in our repository which we will also share links to. And as I mentioned, we would like to expand our impact and do more and therefore we also believe that this team will grow over time because we would also like to give opportunity for our contributors to take a little bit more responsibility and to help each other and support each other so that we can grow and do it in a healthy manner. So I shared a little bit about like the technical advisory group overall, but I would also like to go more into details on what we do in the sub entities of the tag. And the first kind of type of sub entities I would like to talk about is the working groups. So while the tag end focuses a little bit overall on the mission and the goals of what we do as this bigger group, working groups, they have a little bit of a different goal. They're a little bit more narrowly scoped. Typically when there is a challenge, a known challenge that needs some kind of solution or we need to provide some kind of a document, a white paper or maybe a deliverable, a solution to cope with specific challenges in terms of environmental sustainability in the cloud native space, we are looking into possibilities to create a working group where you could work like more scoped on that over some longer period of time. And in the tech currently we have two groups. The first working group is Green Reviews, which Antonio will share a bit more about shortly. And the main goal of that group is more technical compared to the comms working group. So what the Green Reviews working group does is that they are working on building a workflow that can help measure the overall environmental sustainability footprint of all the projects in the CNCF landscape and guide the project maintainers on how this environmental sustainability footprint could be improved over time and also make this data publicly available for the community because we believe that's how it should be. This data should be available publicly and transparently so that we could also take it into evaluation during adopting the different projects and software and also improve over time. And the second working group is the comms working group which focuses maybe on more non-technical activities like helping us with sharing the content, supporting community members who would like to contribute content to the tech that is related to environmental sustainability and also spread the word about us so that next year we can see this audience being fully filled and to be able to do that we need to increase visibility. We need to be able to inspire you to share the word about us and what we do. And that's why this working group also helps with that during events like KubeCon and CloudNativeCon. And from when it comes to projects they are even more narrowly scoped than working groups and they have like a more short term duration so it is very scoped to a very specific deliverable that we would like to produce and that normally happens over a shorter period of time so that it's a little bit easier to manage and measure. And currently we have six projects, many of them kind of started just in terms of weeks before the KubeCon and CloudNativeCon and those that are marked in light green are currently in planning. And even if some of them are actively being developed or are in planning we are always looking for other community members, new community members to join as contributors in all of these projects. So if one of these, or maybe more of them, spark your interest you are very much welcome to check out the link to GitHub issues and let us know that you would like to be a part of that. And to shortly kind of give you an insight of what those projects are about we can start with the landscape documents. Currently we have a version of the landscape document available on our website and what this document actually is is that it basically describes the current challenges when it comes to environmental sustainability in the CloudNative space. What kind of initiatives, frameworks, standards, tools are available for us to kind of learn more about how they could help cope with some of these challenges and how we could integrate those into our own projects. But we would like to make it a bit more approachable, a bit more user friendly and maybe a bit more scoped to what role you are currently working with. And therefore we are rewriting the landscape document and making it even more reader friendly and also more approachable for the community that may have different levels of knowledge around the topic of CloudNative sustainability. And we have one of our awesome contributors here in the middle being a reporter, a journalist today, Jochen that has been putting a lot of time and effort in doing that and doing it by yourself is a tough work. Therefore if you have experience with some of the tools or maybe would like to learn more about that, we don't have any requirements in terms of your experience with that, we will help you get there. So it's not that scary as it seems to get started. So you can join Jochen on this exciting journey of rewriting the document and making it available soon. Thanks. Another project that we are currently planning, so we are looking for folks to help us drive that and also maybe who have some experience with that is the learning paths project where we would like to create a step-by-step overview of how you could learn more about the topic of environmental sustainability in the CloudNative space so that you could kind of learn and grow your skills and knowledge about that. So it somewhat may be like the green software for green software practitioner, just not a certification but more like of a material that you could use for to learn more about it. Another project we have been planning is to gather user stories from the companies out there that are adopting the tools or frameworks or for example, specifications like software carbon intensity specification or tools like Kepler that we are utilizing as well in the working group. And we would like to hear those real life stories that we could share so that other companies and other end users, for example of CNCF, tools can learn from that. So if you are for example, doing something around the environmental sustainability where you work, if you are adopting some of these tools, we would like to know about that and we would like, we would love if you could reach out to us and help us share these stories to help others on their journey with adoption of such tools. Benchmarking white paper is also something we're working on. We would like to provide a white paper that could help you measure the efficiency of your deployments and it's quite a challenging one when it comes to the technicalities. In terms of how you could measure the efficiency of deployments, what is the scope of such measurement and what kind of metrics could we use? So for instance, things like embodied carbon could be a little bit more concrete to measure without making too many assumptions compared to metrics like networking. So there is a good discussion going on in the issue on what kind of metrics could be used to perform such measurement of efficiency of the deployment. So if you are interested in more deep dive on the technical side of things around this topic, we would love to hear from you as well. Kubernetes best practices for sustainability is a document that we are also working on actively as we speak right now. So we have folks who have been doing concrete things in their projects and their companies in terms of running more resource and energy efficient workloads on Kubernetes and also making the Kubernetes itself to be more resource efficient. And we would like to make this concrete information on how you could do that as well available for the community. So we are actively working on that project and have regular discussions in the meetings which if this is something that interests you and you would like to help us share this and help others to do that, you're also welcome to join. And the last one is a smaller project that we're working on and that's a green scraper tool. So one of our community contributors built a tool that basically will help us to create an automated workflow to scrape data about environmental sustainability, cloud native environmental sustainability sessions and events happening in the community and automatically make this list available on our website and keep it continuously updated so that you could have an easy access in one place to learn more and get more content from other community members who are sharing knowledge around the topic of cloud native environmental sustainability. And one last thing that I would like to mention is not a project or a working group in itself but an event that we have done for the very first time in collaboration with CNCF in October last year and that is a cloud native sustainability week. And we wanted with that event to create a place over some time where both local communities but also the global community could come together, share knowledge and their experiences, stories on the topic of environmental sustainability, learn from each other, discuss this topic and the challenges and how we could cope with these challenges and also raise awareness about the things we are doing in the tag. And we got an overwhelmingly positive feedback from the community. We had daily blog posts and live streams and the virtual mini conference and we had more than 22 local meetups that were done by the local organizers in 17 countries spread over four continents. I find it amazing for a first time event and I think the community really appreciated that based on the feedback. So we have a wrap up blog post sharing the findings from the survey about community appreciating that. Yeah, it deserves that. And based on that we would like to make it an annual event. So if you would like to help us in any way like organizing a local meetup in the city where you live help us with artworks, with blog posts on the topic, with engagement, just by sharing the information about the Cloud Native Sustainability Week you are very much welcome to join us. We have a GitHub issue for that as well where you could share that you're interested and we'll get you involved. All right, Antonia, I think it's time for you to share a few exciting details about what you're doing in the GreenReviews working group and how far you've come for the last six months. Yeah, but first a big round of applause to Christina because like this, like she was an incredible contributor and I don't know how many hours she spent. Like she's giving applause to everybody but really like she did a lot of this work. So let's get started. So we all know that computing power is gonna be more and more. So AI, crypto, metaverse, computing power is gonna grow and we need a sustainability approach, we need a sustainability assessment. This awareness is there for the CNCF projects as well and our vision would be to do something like a sustainability assessment, CO2 footprint calculation in the reliefs lifecycle. So to set the scene and understand what we would like to do in practice we have to understand that our working group works under the umbrella of the TAG and what we would like to do is to produce sustainable metrics with respect to the projects that are willing to have a GreenReviews. We will decide when to accept a GreenReviews. This is mainly because like we are voluntarily led association so we don't wanna like burn out too quickly and we know this might be a problem in CNCF and we are not like we are completely independent and that's why we would like to use existing tools, plug it in together and try to be a point of contact for every CNCF project that would like to be a sustainability footprint to be assessed. So it's also important to have a clear statement of the goals and own goals when we talk about sustainability footprint. So our goal is to have this assessment, right? Like to build together a platform that uses existing tools and be a point of contact in communicating with a sustainability footprint publicly. So we'll have public Grafana dashboard that everybody can access and we will not provide individual contribution to others repo. We will not provide consultancy that is under the scope of like what we told what I showed you right now and I think this is important. And another important thing to mention is the shared responsibility model and since like our work is mainly about building bridge between different CNCF projects so like we use a platform that other projects can use to evaluate their carbon footprint availability. Yeah, like it's important to mention that under the responsibility of a CNCF project there is like the main rebel. So like they give us a release and they give us some use cases and we in our platform, we would like to use infrastructure as software to produce these metrics. So like there will be a GitHub action which is triggered and it's mainly its main job would be to yeah, install the project, produce the metrics and publish them. So let's get a bit more technical and let's try to understand what happens when we would like to produce such metrics. Here you can recognize on the top the CNCF projects, X, Y, whatever and there you can see on the right on yellow our equinix based infrastructure. We decided to go bare metal because we think that it's more important to access low level hardware metrics related to energy to have a more like precise measurement about what's going on in the cluster. We have of course a Kubernetes cluster some observability tools. Yeah, I would like to mention Kepler which is an important CNCF projects that's providing energy metrics at container level using EBPF and we also have Prometheus to collect all the metrics and Grafana to publicly share this metrics. And then you can see a relief of the CNCF project will via web book. This is our vision. We'll trigger a GitHub action that will start a benchmarking pipeline and this pipeline could provision real time and benchmarking nodes. And like here we had an example of two benchmarking nodes one for idle usage of a software and another one for any benchmark that you can think of like we call it that star in this case. Everything is managed with a GitHub's praxis and yet like we hope that this will be done soon. So let me first introduce the SCI score. So this is this answer. Okay, like what metrics exactly are we publishing? And this is the software carbon intensity score. It's a soon to be ISO standard which calculates the carbon footprint emissions of a software use case and it has as a main factor the energy multiplied by the intensity of this energy. This is like in our case a constant. And then we add on top the embodied carbon used for the hardware. And then we have a functional unit. You can think of a functional unit on a factor that scales your software. It's usually API or usage. In this case we used a 15 minutes a 15 minutes time for the software to be used. And it's with great pride that we can show you today like our first metrics produced. This was our first milestone to be concrete and do some data. You can already see that the SCI is highly dominated by the embodied carbon which may be a problem, right? Because software or like CNCF projects are not really interested about the carbon which is embodied in the software we are running as a platform. And this raises some questions which are open that we are willing to discuss with anybody who is willing to take a look at this data and improve our pipeline. But still it has been a big effort to produce this metric. So yeah, like a big positive community. So this is our roadmap. The working group was founded in September 2023. FALCO was the first project we requested officially a green review. And in February we had our Kubernetes platform up and running. And here today we have shown you the first sustainability metrics that we have produced. And for Q2 we would like to have workflow automated. So like everything that you saw that you saw about the GitHub action called via web hook from the release of another CNCF project is not there yet. We have manually deployed the release and the project but we believe that we can get there within the next milestone. And then we would like to see what will be the new project the next project that we will evaluate the sustainability footprint assessment. Yeah, so overall this has been quite quick. In only six months we reached a plus 100 commits and we resolved the first 10 issues might look like small numbers but yeah, there was really a lot of work behind and the platform is up and running. The first sustainability metrics have been produced and yeah, this wouldn't be possible also without Niki and Ross. So yeah, I think Leo everybody basically but yeah, like there has been a huge effort voluntarily based effort to do this. So yeah, it's great to see so many people and yeah, to share these results with you. Awesome, thank you, Antonio. And there is still more to do. So if you would like to contribute, it's not only cold we are looking for, we're also doing a lot of efforts on documenting that so that others can use this reference architecture for inspiration and maybe for further improvement of that. So you're welcome to join that. And we also released right before the start of KubeCon and CloudNativeCon, a blog post that goes more deeply into the technical details as well of how these reference architecture is built. So you could also read it in our blog section on the website to learn even more about this platform. And to round a bit up, I would also like to share some reflections of what we have achieved as a tag for the last less than two years, which I find to be quite impressive. I have been a part of many communities through the last two years. And personally, I felt quite lonely, often especially at work, trying to communicate the message of why we as developers or platform engineers or technical resources should care about environmental sustainability and why it's not an isolated issue or a political issue. It's something bigger that for us who are interested in the science-based data and empirical data, it is available for us to look at to understand that this is a real challenge that is backed up by real empirical data. And that's important for us to care about it. And it felt really lonely for me for quite some time until I just joined the TAG project meeting in last KubeCon and CloudNativeCon in Amsterdam. And since then, I don't know, I am biased, I guess, but this has been for me the most diverse, inclusive and open and warm and welcoming community. And I would, I don't know, I'm like really getting emotional about that because I have never been a part of a community like that that is really passionate and where we support each other. And together can make things happen, like getting that blog post out in terms of a few days where like 10 people just put their effort to make this happen, to make it available for the community. So if you also feel like that, if you would like to be a part of the community that makes an impact, this is the place. And we have grown during this time to more than 1,000 contributors across of the different TAG channels. And we checked our repositories and we have more than 70 contributors who also did some kind of contribution to our repositories. We now have two active working groups and six projects that are either in planning or are active. All or parts of our content on our website is now available in four languages. And we even had students contributing to the translations and we are currently working on automating the kind of the need for translations in case we get changes to the content so that we can keep it updated and scale even further. So if you would like to help us reach other, a broader community in the globe with our content and you would like to contribute to some other language than English, please join us, we would welcome that very much. And there was also a great lightning talk on Tuesday about the need for having this multiple, content in multiple languages available to reach more people and convey our message. And we had a successful Cloud Native Sustainability Week event for the first one with more than 3,000 participants, like I said, across 17 countries and four continents. And we have content that keeps growing. We get blog posts, contributions, we get live streams, recordings, and we have documents to reference by the community like Cloud Native Sustainability Landscape and Cloud Native Environmental Sustainability Glossary. And to round it up, all of this would not have been possible without all of you, everyone who contributed, everyone who has been supporting us, who has been sharing what we do or contributing directly to that. We are quite international, quite diverse. So that's how from our tag end of meetings and that's from the Cloud Native Sustainability Week and the different meetups. But I also, in the last minute, did put in a few pictures of us from KubeCon and Cloud NativeCon from this year, we gathered ourselves here. We have a booth that is still open where you can come talk to us to our contributors. Still open today for some time till half past one and it's also open tomorrow. So if you would like to learn more, have any additional questions, come join us. And we also got an interview today also. So hopefully we can get it to spread the message even more. So we are a very nice community to join, very biased information. So how can you contribute? If this sounds like something that could interest you, we have simple steps, how you could start and join us. We have a contributor guide available in our repository where you could, which we would recommend to read. We have issues that are marked as help wanted or good first issue that should also help some, some of you to start picking that up and maybe helping us out on those. We have regular meetings in the tag but also in the working groups and projects and the projects. So you could choose from those that interest you most. We have, yeah, our Slack channels as well for the working groups for some of the projects and our tag environmental sustainability Slack channel under CNCF workspace. You could also help us with the events like cloud native sustainability. We can basically just share suggestions or ideas you may have on what we should focus on. We have also recordings for how to start contributing from previously, but we will also have live sessions like that again, a few weeks after KubeCon and cloud native console. You could follow our calendar for the tag which is publicly available and we will announce those sessions soon that you could join live. Yeah, and I think that's it. We have a few links that are gathered in one place on how you could reach out to us and how you can get access to all the activities we're working on. So you could just scan that QR code and you'll get all those links in one place. And we are open for questions. So don't be shy if you would like to learn something. Yeah, awesome. Are you planning to open it up to projects that are not part of the CNCF or that are applying to be part of the CNCF? And if I can, another thing is if I understood correctly, you will measure how a project, the cost of running a certain project, but do you also plan to measure the building and processing of that project before it reaches a user? Are you thinking? Who will answer that? If there are questions. If there are questions? I will answer that? Okay. Can I just please queue, yeah, with your hand. You want to answer that or shall? Yeah, like the two answers that I don't know. So I guess first would be CNCF projects, right? Like to give presidents. And we are just, we haven't drawn a fully detailed roadmap yet. What do you saw like about the new project is still like in the next quarter. So first we'll have to fully automate the current solution. Be sure that we have something that scales and then we'll open up the discussion for what would be the next project, either CNCF or non-CNCF. I don't think that matters too much. Yeah, and in terms of measurement, I think the second question was like if we measure before the execution, what's that before the execution of the, yeah. Yeah, that's a very good point. There are many aspects that we haven't touched like pipelines, also we haven't assessed the sustainability of the benchmarking. There is an issue basically for everything actually in the repo, but we have to do a careful planning and we have to use our energy wisely and try to see like what we can address step by step. Yeah, but I think one thing that we are doing in the working group as well is that we also assess how a resource efficient is our own workflow that we are building. So we are also looking into ways how we could measure the pipeline or the workflow that is running. So we would like to document that information as well so that it could be available and applicable also outside of the CNCF. It's not, we have not decided yet if we can like make this workflow assist companies outside of the CNCF with use utilizing that workflow, but you can gain a lot of inspiration and kind of concrete information how we do that in scope of the CNCF ecosystem. Yes, and regarding to the metrics and the choice of units and the values that you are collecting, are these going to change eventually? Are there coming new metrics into play regarding embodied or emissions that you are collecting because I've been talking with people from Honeycomb in open telemetry and also having a sustainability data working group that's looking for a lead. So anyone who likes to build standards that others can build upon. Like what's coming from the science side of things, yeah. Yeah, so it's also this has been there is room for discussion. So there was an issue open like what kind of sustainability metrics should we use? And then we were, yeah, maybe we like the SCI standard because it's going to be ISO standard. And however, as I showed, I think like there are some complexities. For example, the embodied carbon dominates a lot and maybe it doesn't really capture what we would like to capture in a green review. It would be interesting for sure to start a discussion and see how this can take place into the roadmap. Yeah, we had to start with some metrics. So we made some of them available that we kind of know and could like relatively easy start with, but I think it's in scope in the discussions on which metrics we're gonna open up for also going forward. And SCI, it was also discussed that SCI will not be the only one, not the only methodology we're gonna use potentially. But it's also if you have like some experience, you're welcome to share that in the discussions. Will there be some documentation on maybe how to run the benchmark yourself? So if you're not a project that's under a CNCF or a company, so you can at least like assess how you're doing without having like maybe an official batch or whatever the result from the reviewers? Yeah, this is a great idea. We are not at that point yet. It would be super nice to have a self-served platform that everybody could run. You're more than welcome to join us and contribute to make this happen. And one more question. Are you also looking for contributors to translate to German or? Yeah, yeah, we don't have German language. As part of that, we actually have Korean and Mandarin if I'm not mistaken and Spanish. So if you would like, we would love that. Yes, let us know. Sorry for the overtime. So I think there's some similarities between CNCF activities and also the green software foundation, right? So I think how do you have a plan, try to collaborating them with closely? Is that our strategy or something? I think there's some like in-house this project that might be kind of ends up having kind of similarity. So I think as you said, we shouldn't waste our time or resources, right? In that kind of mentality. So one might be good, you know, our approaches. So let's say, I think energy measurement is not the end of the equation, right? So I think we have to have like a carbon intensity and also a lot of other equation. You have to put it together and then to get to this carbon footprint, right? So just wanna have your thought. Yeah, that was actually a great, that was really great that you brought it up because when I talk without notes, of course that's something I missed on mentioning. We do collaborate with organizations like Green Software Foundation and this is the part of our overall strategy in the tech. So we had folks from Green Software Foundation, for example, coming and sharing about the impact framework that they now have a carbon hack hackathon around. So how they're developing this project to be able to kind of measure the energy and carbon emissions, I think, through like a single way to configure that type of measurement workflow. So they were present at our project meetings and presenting on that. And we have also folks in the tag who also contribute in the Green Software Foundation. So we have like contact points there as well and it's not only Green Software Foundation but also Green Coding, I think, that when they shared about the Green Matrix tool recently at one of our project meetings. And we have been talking also about water consumption, for instance, and the challenges there and how AI impacts it. So we have these discussions ongoing and as well if you have, for example, some suggestions or you maybe are contributing to a neighboring organization and would like to strengthen that collaboration as well, it's of course open. But to answer your question, yes, we have initiatives ongoing there with the other organizations. Yeah, we're already contributing to some of the Kepler project already. Awesome, cool. I think we're in a quick question. Yeah. Just wanna have a quick talk, thank you. Thank you. Then thank you so much. Thank you.