Hey guys, it's Nate, A.K. The Foot Accountant. Welcome back to the channel. We are gonna tackle a big question today on this very fine Monday in FIVA 22, when to buy Premier League team of the season. We are gonna be taking a close look at Premier League Tots cards today and that when I think it might be the best time to buy some of these items that have changed everything on the market. Quite literally, this whole entire market is crashing because of how cheap these cards are, but also so many people wanna get them for their teams because of how insane these cards are statistically, but also how cheap they are. There's a lot of demand for these cards. So I wanna take a look at time frames of when it might be the best time to buy some of these Premier League Tots team and the season players as we head throughout this week. And I know we're taking a look at this very early on in the week, but I feel like we need to because these cards are gonna be fluctuating day in and day out, especially today on Monday as it is a massive day on this game with the release or the hopeful release of what we would hope for is the 25K Premium Premier League Upgrade Packs, the same ones that we had during team of the year and the same ones that we have had in the past couple of years during team of the season. We're hoping for those upgrade packs today that could move the market a little bit. So we're gonna take a look at all of that and of course, speaking of the market, this prices on this game on other cards apart from like Premier League Tots and everything else are down horrendous. And we're gonna continue to look at why these cards are down so much like we talked about in yesterday's video and actually how I think there's a little bit of potential for some of these cards to start rising back up a little bit after the weekend because that even though the weekend league is still going on, it seems to be most people are still used to playing on the weekend so the markets revolve around the same schedule that it usually does on any normal given week in this game. So we'll talk about that. Of course, Monday content other than upgrade packs that we would expect to see on the game today as well. So if you're excited for upgrade packs today and hope you want to pack some blues, hit the thumbs up on the video and of course, subscribe if you're new. Now let's dive into that question, when to buy Premier League Tots because that is such a big question for so many people on this game. Whatever the card is that you want to buy, Bernardo, Van Dyke, Cancelo, Hyunmin Sun or it's maybe even Trent Alexander-Arnold for a four star, four star boost, 156,000 coins. One thing is the same with all these cards right now. They have dropped off a lot since they first came into packs. Trent was 232K on Saturday morning and now this guy is 150,000 coins. Yesterday on Sunday these cards dropped off a little bit more, you can see Trent hit his low point here at about 150 on this Sunday night into Monday morning. Now I'll say this, a lot of these cards have gotten pretty low in the past day. As you guys know, right? Sun was like 780 at his lowest. Van Dyke is currently at the lowest he's ever been. Salah is under 2.5 mil. Diogo Jota is 230,000 coins. This is one of the most popular cards in the game right now and you can tell base office price fluctuations every single day. Look at this, Diogo Jota 346 up to 390 all the way down to 260K. Last night, or sorry, this was actually Sunday, early Sunday morning, late Saturday night into Sunday. He goes from 240 up to 275 and here we sit on the market with Diogo Jota at 230,000 coins. These cards have so much demand, that's why they keep fluctuating up and down in price on the game because people are constantly buying them, trying them out in their teams and there's gonna become a point in the next couple of days where people are gonna buy these cards and then put them in their teams and not really sell them. So that's kind of what we're trying to get ahead of. We're trying to get ahead of the curve and time the buy so that we buy before a lot of other people do and of course people always try to buy cards like this before they go out of packs because again, people think that when cards go out of packs, they automatically rise. That doesn't always happen. I think it could happen here a little bit with these Premier League Tots cards into the weekend but that's what we're gonna talk about today. I think that we are in the low area for a lot of these Prem Tots cards and you're like, Nate, it's Monday morning. We don't have week-end league rewards today. Last week, the Community Tots cards like Zaha and Fred, they were near their lowest on Wednesday. Some of them were low on Sunday and Monday morning, so what gives? Why are we in the low now? Well, there's so much more demand for these cards since they're so cracked and they're so cheap. I think that there's going to be rises on these cards faster than what you would expect. So this is what I'm saying. If you see a card like this Diogo Jotas, 230,000 coins, this Trent is 150. With all the drop-offs that we have seen this weekend, Bernardo Silva is 178K. I think what you're gonna wanna do is before Wednesday of this week and again, I'm giving you a broad range in here because prices are gonna fluctuate every day. There's going to be rises, there's going to be falls every single day for each and every one of these teams and season cards. Of course, on Wednesday, that's why I'm giving you like a Wednesday cutoff date because when you're looking to buy one of these cards for your team, a lot of people look for that Wednesday date as the time to buy because that's when we should be getting the Premier League Guaranteed Tots upgrade pack. And last week, when we had the release of the community team in the season pack, the Guaranteed Pack, we had cards like Fred and Zaha right after that pack was released. People didn't pack them in their Guaranteed Pack. They ran to the market and bought them up and those cards started going up in price very, very quickly right after that. So to avoid that demand and those price spikes right away, I really think it's important to stay ahead of the game like I mentioned before and start looking at these cards today, tomorrow and even a little bit on Wednesday as well. There could be a bit of panic selling heading into that Guaranteed Upgrade Pack dropping on Wednesday. So that's what I would say for a lot of these cards. Again, you guys know the prices.  I sold two of these Van Dykes yesterday at 690,000 coins on Sunday, right? I bought him at 630, sold him at 690. He's back down even lower than what he was before.  Probably not, but that's the kind of thing you're looking at with these cards is we are kind of near that low point before everything starts to transition into more people buying later on in this week. Now, of course, we don't know what kind of SBCs that EA are going to drop.  There's always, and I mean always, opportunities for EA to drop content that could crash the market a little bit. And EA is gonna continue to run the lightning rounds this week as well. So that's one thing that helps, I guess, is you'll have a little bit of constant supply coming in. But I really think that your buy time for a lot of these Prem tots cards is going to be in the next two days, two to three days, to be completely honest. Now, one thing that's a bit interesting with this is if you take a look at the Weekend League timeframe, and I gotta point this out, I'm in the middle of my Weekend League right now. I'm five and two, seven games played. This Weekend League, it's kind of behind my face cam. You can't see it. Weekend League ends a day before it did last week. I wanna point this out, if you were not aware, take a look at the timer in the bottom left-hand corner of your screen there. Ends in one day, four hours. When I'm recording this, this is late Sunday night, early Monday morning. That means basically we're 24 hours away from Weekend League ending, so it's gonna end Tuesday morning instead of Wednesday morning from last week. I don't know why this was changed, but I think they must have just added on an extra 24 hours since last week was the first week. I don't know, but now I need to make sure that I get my games in. We noticed this just at the end of the livestream yesterday on Twitch. Chiki linked down below in the description if you wanna get involved with the livestreams there every day, but I did notice that. I think that's very worth pointing out because some of these cards for Premier League Tots might have a bit of a market rise even tomorrow on like Tuesday after rewards because we saw that last week on Wednesday with the rewards being given out for Community Tots. That caused a bit of market rise as well. Now last thing I wanna say is regardless of whether you're wanting to buy a Premier League Tots card for your team or for an investment, let me just show you something. These cards are not gonna maintain their prices that they're at, even some of the most expensive ones and even some of the cheaper ones. They're not all gonna maintain these prices and continue to rise for like a couple weeks to come. It's not like you can go buy one of these Tots Premier League cards, put it in your team and hold it there for three or four weeks and expect to make money on the card. This is what happens during the season. Since we're having so many top tier insane cards released every single week from these different leagues, take a look at Jim and Son. He got to his lowest in the first couple days of the week last year, right under two million coins, exploded the 2.3 mil on the weekend and then what happens the next Monday? He's back down at 1.8 mil and then a couple weeks later, he's down at 1.1 million coins because every single week we're getting more and more insane Tots cards. This is 100% gonna happen this year as well. It's already starting to happen with Tots community cards. Look at Luis Suarez. This dude was 1.3 or 1.2 million coins on Friday. He is 899,000 coins on the market right now. Some guys like Fred and Zaha are still up of it and La Porte are still up, but I just think that you can't be buying these permanent cards and expecting to hold onto them for a long time unless you don't care about losing coins. That's fine and dandy too. If you just wanna buy one of these and say screw it, this is my end game team and I'm going for it. I just wanted to point that out because the market is still gonna change drastically in the next couple of weeks with all these great leagues coming out with more Tots cards on the game as well. So I wanted to point that out, but that kind of should answer the question and give you a lot of insight, of course, on when to buy some of these team season permanent cards which are so in demand on this market and on this game. Now, let's talk about today on Monday and what a lot of people are getting very, very excited for. You can see the Tots counter is up to 19. I haven't packed any notables yet. Besides Trent Alexander Arnold, I did pack a Bruno from my 84 times 25 and an Allison, but what everybody's gonna be going after today are upgrade packs. That's what this day, this Monday on FIFA is so that there's so much anticipation and so much hype built into today because of this pack right here. These are the upgrade packs that we are hoping and expecting to get the premium Premier League upgrade pack, SBC. A lot of people are already preparing to buy, to build these packs by going out and buying rare golds. You do not have to buy Premier League rare golds. I would be absolutely shocked if EA required league specific rares for the upgrade pack SBC. Last year and this earlier this year in team of the year, they did not require specific league rares. It was just 11 rare players, 45 chemistry and that was it and that's a W. That would mean that these, this pack right here, what it is and the reason why it's so hype is because it's basically a 25K pack, 12 Premier League players, three of them rare. It's incredible for packing team in the seasons and the pack way it's gonna be flying.  We're gonna spend so many coins on this and a lot of people are ready to do the same. Now we don't have any confirmation that this pack is coming for sure. It's just kind of one of those unwritten rules and if EA don't do this today, then they are going to get so much hurt and so much, I guess hate is kind of the best word to describe it. People are gonna be so mad. This happened, I believe it was FIFA 19 or FIFA 20 or I think it was FIFA 20. EA didn't release the upgrade packs right away and the whole community rioted and almost forced EA to put out the packs because we were like, yo, where are these packs? We wanna spam them. So I think they're gonna come out today. Mondays have been upgrade pack days. Anyway, a lot of people have been buying rare golds. I think that's a great idea because when these packs come out, I would anticipate that most rare golds in this game are going to go up to around 900 to 1,000 coins per gold rare card. So right now, as you can see, you can get them for 750 for the Premier League rares. But then if you go to the other leagues too, like let's go to the La Liga, you can very easily get La Liga rares for 700 or 750 coins apiece. So that's a great opportunity to fill up your club, fill up your transfer list or even go unassigned if you want to and bid and buy it now, a lot of those cards to just get a head start if you wanna build a lot of upgrade packs. That's something that I have not done yet but I'm absolutely thinking about doing and we should see that content today. We should get two upgrade SBCs because we should get that main one, the 25K pack and then we should have another Premier League upgrade for people to like rinse into if that makes sense that would require more non-rares than the rares. So you can stock your club with non-rares as well. Those will become useful for the upgrade packs that should drop today but today really begins the hype and trying to pack as many blues as possible. That's, we're gonna spend so many coins doing that.  You're gonna be able to craft SBCs. If you haven't done Deliali, Harry Kane, it is leaked. Actually, I don't know if this is gonna be coming today but we have an icon moments, Wayne Rooney. He's evidently coming as an SBC as well. Perfect timing for E to drop this with all the English cards in the game but Wayne Rooney's icon moments card, he is going to be getting an SBC I believe this week on FIFA 22 as well. So just kinda keep an eye out for that if that's something that would interest you but today the big day and the big hype is for the upgrade packs. Now could we get a Rooney today? Maybe. Could we get an Akin Fenawa? Again, if you watched yesterday's video we talked about an Akin Fenawa end of an era card. That is something that could be coming today as well. It is leaked, it is confirmed. It's just a matter of time till when we get the SBC. I would also imagine like an 86 plus double upgrade or like an 85 plus type pack. We had one of those last Monday with the 86 double. I would anticipate an upgrade gamble type pack like that today on Monday as well in this game. It's gonna be a mad day of content.  I'm trying to get my games in so that we can start ripping packs and having a lot of fun that way. Now also I'm trying to make some coins and as you may tell the coin balance is down a bit. Now I have bought some cards. I've sold some cards as well. I did flip a Rooney. He was down in like the 550K range, bought one there, sold it at 620, flipped myself a little real Ferdinand and I have bought some team in the season cards to try to flip and to try to trade with because at the moment, these are the cards that are hyped, right? But the market in general, as I take a look, again, at like this Ben Yetter card, I bought two Ben Yetters yesterday at 700,000 coins thinking that it was too cheap. And now look at this guy, he's 670. Like it's crazy to see some of these cards and how low they've gotten. Like I'm watching the Suarez item right now as well because some of these cards, I understand that they've dropped off a lot in price but it just seems to be like compound panic selling and you guys know, we talk about it all the time that when cards are still pretty hyped because they're new, they're popular and they're rare, just like a guy like this Suarez, second owner, 55 games played, 65 goals scored. What a beast. I mean, not just this card in general but there's gonna be some cards that will bounce back in price from the low prices that we see right now this week even though today's a huge coin drain day for a lot of people going out and doing upgrade packs. Look at Debala, Debala's 560. I mean, yesterday we were like, man, this guy's cheap and he was 625,000 coins. So as I continue to scroll through the market, all I see is down bad. That's literally all that I see except for a few cards from the Premier League. Like Joe Cole is still up, Henderson is not really dropped at all but like Abeddi Pele was 1.2 million coins on Friday, right, 1.1 mil. He's now 875,000 coins. I feel like we're taking a look at some of the same cards each and every time we hop on a video but it's just crazy to see these price drop-offs. And again, a quick word of warning, if there's still a card that you own that is not down that much, especially like maybe a Coutinho because Premier League is hyped right now. Martinelli's down a little bit, but he's 548K. I would just be very careful holding on to stuff that is inflated in price. This Lucas Mora card at 1.1 million coins. I know he's really good. He is going to drop in price a lot over the next couple of weeks. The Premier League cards that are inflated in price right now, I would not hold on to them for too much longer because it just cannot last. The Mora's wrote to the final. I keep mentioning him too. These prices cannot last when the rest of the market is so cheap and the rest of the market is dropping because of all of these cards being so cheap. It's the same thing is going to happen this next Friday when we get Bundesliga team of the season. A lot of the Premier League Tots cards are going to drop off after the weekend and Premier League cards that were hyped in general are going to drop off as people say, oh my goodness, these Bundesliga cards are cracked. I want to go out and try some Bundesliga cards. So you can trade. Like we looked at Pedri yesterday, he was 750. Now he's back up over 800K. You can absolutely trade and make coins off of some of these cards. And again, like I mentioned, some of the ones that are just really, really rare that are still really popular and meta, you can absolutely make some coins off of, but you just have to be careful with the cards that you're trading with and the items that you're spending coins on because if the card that you're looking at is not very, oh my gosh, Keen for 756, that's an incredible bid. But like, look at this guy, he's so low. Bids at 750 and 600 back here too. It's just crazy. That's what I would say right now is be very careful because we get so many insane Tots cards every single week in this game and the market always goes towards what is hot and what is popular. And that right now is these Prem Tots cards. Now, speaking of new Tots cards, here's one that we had yesterday, Mitrovic. I picked up a couple of these because I think that he might go up a bit. I picked up some at 200K. Think he might go to like 230 or 240. Today on Monday we'll see if that happens or not. This card is not incredibly hyped, but it's brand new and it's rare. Pretty, this is like the best card from EFL Tots. Like we were talking about in yesterday's video. The EFL Tots squad is just, it's cool and no offense if you're an EFL fan, but EA just did not give these guys the juice that they gave to A, the Aeridivisi or any of the Tots leagues so far. Harry Wilson is not four star, four star unfortunately. He is three star skills, four star weak foot. If this card had the four star skills to it, I feel like he'd be an extra 50, 60,000 coins. He's 150, 160K right now. He's actually up like 15K, but these cards are rare. They do have a little bit of hype because they're brand new, but they're just not that great. I mean, completely honest, a lot of this team is fodder besides Twain, Mitrovic, Solanki and Wilson. So I do feel a bit bad. I wish they were a little bit better in terms of statistics, that's for sure. But that really didn't cause a lot of movements on the market yesterday because these cards are just, again, like I mentioned, they're not that cracked and they don't bring as much hype to the game as we would have really wanted to. Now, one of the last things we're gonna talk about in the video today is SBC fodder because fodder cards are in the bin once again because we did have the 92 plus icon moments pack yesterday, but it really didn't move fodder that much because it wasn't a player pick and we still were getting all of those lightning rounds and all of that supply. Now, there's gonna be gameplay, not gameplay demand, there's going to be demand this week for people to get SBCs done and crafted with the packs that we're gonna see added to the, or the upgrade packs that we're gonna see added to the SBC section today. So I do think there's gonna be some fodder movements later on this week. If you've bought 84s, 85s, 86s, especially on the low tier end of fodder, which is where I think I like it the most right now, if I'm being completely honest, I like that tier. Yeah, man, I just think that a lot of these cards are still going to rise up because we have got a lot of SBCs coming. Like I mentioned, the gamble packs, the guaranteed team of the season SBCs, I think those are all going to be coming here pretty soon this week and I think that creates a really, really good opportunity to make some coins and you will see those cards rise. Although, right now it seems kind of crazy with how cheap these cards are. If you guys remember last year actually, SBC fodder was its cheapest during Premier League Tots, then the content really ramped up and all of this fodder exploded in the weeks after the Premier League team of the season. So that's something to kind of consider as well is you might have some of these cards that will actually be their lowest this week and then if the content really starts to crank up, then you'll see these prices really balloon. Actually, as I was just looking at that, Harry Wilson, I checked him out on the market. I checked him out at 160 and there were two at 140. I picked both of those up and now the cheapest one in the market's 190. So I just listed mine up but these guys are really rare, man. And that's why I picked up a couple of this Wilson card and I picked up a couple of the Mitrovich as well is because yes, they're not the most insanely hyped cards ever, but they're really rare and rarity is one of the best things we like when trading on this market. So I think I'm gonna pick myself up as Suarez right here. 900, 897, can I get like an 896, a CDM position change. You know what, I'm gonna snag this one, man. I'm gonna snag this one. I think that's way too cheap. I think it's gonna rise up a little bit today. So that's an investment you guys can follow along with me, I suppose, since we bought it on the video. And yeah, hopefully we sell it tomorrow and make some coins off of it. But that's gonna be the video for today, lads. Again, if you're opening upgrade packs today, have fun, of course, be smart with your coins. Don't spend too many coins unless you can afford it. But hopefully you all pack some blues.  EA just dropped the right upgrade packs and we won't have an issue. We shouldn't have an issue, but you never know. It's EA Sports. So that's gonna be the video for today, boys. I hope it did help you out. If it did, leave a like on it. Comment down below if you have any questions and subscribe if you're new. It's been Nate the Foot Account and I'll catch you guys later. Peace out.


What's up everyone? It's your girl Kenzie here from Layton Sports Cards, and I'm ripping some personals here for Landon G We've got three of the 2022 Panini Select UFC H2 boxes. Best of luck Landon. Thank you so much for hopping in Just saw your order come through Iggy.  So Usman we've got speckle Izzy out of sony or disco speckle Where'd that come from? Disco concourse Izzy and silver rob fonts on the premiere level There was a there was a card last night. I can't remember who fought though Someone was saying it was a blood bath. Was it? Oh figuardo on the octagon side uh bisping Disco concourse and premiere level disco of sterling Vantage division Regas crooks and ghanu lingo and silver polo costa concourse Last pack box one Sean Brady rookie Frozen struck mine fell in is and red rookie premiere level disco of da woon jong Light heavyweight division 53 of 99 on that one All right, that'll do it for the first box there box two here, Landon Kenya, aloe vera, rosa. We've got a patty uh base here concourse Disco rookie Sean Strickland concourse and silver premiere level of Royce Gracie Craig sterling alvarez and silver jimmy crooks concourse Volk franklin Um yoke on the octagon side disco rookie concourse andre munis And disco premiere level rookie of phil hauls Last pack box two here's the silver Saint pierre and octagon side disco of anthony smith. All right box number three Last anomies There we go sterling jong silver concourse of crela Coming this way Rookie concourse disco of uh bontorn and premiere level disco amanda nunez silver Rockman off we've got blue of dustin porie Nice eight out of 49 on the blue disco concourse Nice Yeah, alabama. That's what uh a lot of people I've heard a lot of people say i'm i'm all for it We've got rookie concourse uh daniel rodriguez And silver is he adesanya on the premiere level? All righty landon that will do it for your three h2 boxes. Thanks as always for hopping in and we'll get these right out to you


Thanks Graeme and thanks everyone for having me. As Graeme mentioned, I'm Alison Scotland, I work for Standards Australia and I'm responsible for the building and construction sector. It's a real privilege to join you here today and thank you to the ABCB for inviting us along. It's a really great opportunity to connect with you all and to hear from you about what's important to you in the building sector. So my presentation, as Graeme mentioned, is going to be roughly around 20 minutes.  Then I'm going to go into an update on a selection of standards. As Graeme mentioned, there are so many changes to NCC 2019 and then give you a little bit of a snippet about what Standards Australia is doing into the future. So starting off, talking about how standards are referenced in the National Construction Code, the key point is, just like the verification methods, using or following a standard is just one tool to show that you meet the performance requirement. So standards support the implementation of building policy. They're not necessarily the be all and end all. And just like Graeme mentioned, about the masonry 3700, even if you just follow the standard, you might not actually be meeting regulation. So that's just an important thing to consider. Who develop standards? You do. We are a member-based organisation at Standards Australia. We have hundreds of technical committees developing standards across all sectors of the Australian economy. So in terms of how you can be involved, you can be involved through your membership of organisations that contribute to the drafting of technical committees. So it might be the HIAs or the Master Builders or the Institute of Building Surveyors. You can also comment on draft standards when they become available for public consultation. So on our website, we are continually advertising standards that are available for download and commenting. So you can provide your feedback on draft standards in that way. If you also have new ideas or feel that a standard needs to change in a way, you can actually develop and prepare a proposal and submit it to Standards Australia for either a new standard or a revised standard. And that's my day job. So you come and approach me for the building and construction sector. The development of standards that are referenced in the NCC, they need to go through a really robust process. That process does take some time. So what we do is we try to align where possible with ABCB processes because we have to follow their protocols. If you're changing a reference standard, by default you could be changing law. So we need to go through a really rigorous process. So just like anything, we need to prioritise our work. We need to focus on addressing issues and problems in the industry and provide solutions that will address those problems. We go through the same protocols. We need to meet rigorous protocols in terms of how those standards are drafted. We go through the same periods of public consultation where we go out to the community for comment and we need to resolve all of those comments when we receive them. And then we have the same approval mechanisms that we need to go through in terms of getting the document approved for referencing. So moving on to the actual reference standards, and as Graham alluded to, there are a significant number of changes to do with reference standards in the NCC 2019. I'm going to talk about the Australian standards only. As you know, there's other standards or technical specifications that get referenced like the FPAA documents. I'll just be focusing on Australian standards for now. Graham also mentioned there is a comprehensive summary of all of the changes to all the standards. That will be available on the ABCB website under the seminars link. So definitely check that out. That's the exhaustive list. I've only got 20 minutes, so I can't cover them all right now. I'll also link, you know, if you need to know what standards are referenced in 2019, Schedule 4 has the list. Schedule 4 also indicates any transition periods that apply or grandfather clauses. So Schedule 4 is your important reference there. In terms of Australian standards that have been referenced in NCC 2019, again, a significant number of changes. You might have standards referenced for the very first time, but might not necessarily be new. So the standard on earth retaining structures, that's actually a 2002 standard, but it's referenced for the first time in NCC 2019. We have a lot of standards that have been removed because they're no longer relevant to the performance requirements. We have changes, we might have new additions, so revisions of existing standards, and we also have recognition of some of the reference standards that have amendments to them. So again, a huge number of changes. I can't go through them all, but what I'm giving you is a snapshot of what's changed. With that in mind, in terms of how my slides will be presented today, I will be listing a main summary of changes on the screen. I'm not going to read that out because that's really boring. What I'll do is provide you a bit of context about the development of that standard. For a full list, rather than going out and buying the standard and then finding it's not relevant for you, you can actually go to our distributor's website and you can actually download a preview of every standard. And in that preview, if you actually go to the preface, especially of a revision, generally the preface will outline at least a general idea of what has changed. With the standards I'm talking about in this session, there's quite a significant list of changes that have occurred to some of the standards. If a standard is new, you can look at the contents page. So you do have the ability to seek out information yourself before you make any purchasing decisions. Okay, so moving into my slides, I realise I haven't structured my presentation like volume two in the theoretical order of constructing a house, but I'll do my best. I'm starting with structural standards, so I'm on the right track. Just like the ABCB slides in the corner, I will have reference to volume one or two if it's referenced there. As mentioned before, the standards referenced in volume three will be the subject of a separate webcast that will be available on the ABC website after the seminar series have finished. So I won't be dealing with volume three, but I know from the hands that didn't raise, we don't have any plumbers in the room, so that's okay. So moving on to concrete structures.  Obviously, on one PowerPoint slide, I can't list all the changes that have occurred to this standard, but what I can say is what has happened in this revision is the fruit of a vast amount of research that has occurred in the industry since the last edition. A lot of the research was tackling specific issues such as durability or acid sulfate soils, so there's a lot more sort of knowledge that has been incorporated into the standard. In addition, the standards of the technical committee preparing the standard, they've recognised a lot of advances in technology and they've attempted to provide users of the standard and practitioners with more options, more design options for design of concrete structures. They've also tried to cater for more products available in the market now, for instance, the fibre reinforced concrete, so hopefully the users of the standard will be able to see that there are a lot more solutions available for them to use as a DTS. Onto masonry, I did mention before that this standard is actually referenced in NCC 2019 with conditions. I won't repeat the conditions, but know that they exist, so take care to, when you're using the standard, to also note the National Construction Code requirements. Again, this committee was responding to a lot of industry research that's happened since the last edition. There's a lot more updated technology that the committee has absorbed into this revision. There's more realistic strength predictions and the committee tried to incorporate the growing use of practices such as dry stack and thin bed hollow masonry, so there's a lot more within the standard. This particular standard also aligns with what has already been published in 4773 for small buildings, so it's aligned with 4773. And if I do go too fast, these slides will be available on the website, so I know, yeah, no writing, you can take photos of course. Onto composite structures, so the design and construction of steel frame buildings. It requires continuous composite beams, composite columns, connections and slabs. The 2003 version of the composite structures standard only actually looked at simply supported beams, so the work that the technical committee did to produce this edition was quite significant. This list obviously isn't exhaustive, there's a lot of work that the committee did to incorporate these additional requirements around beams, connections, slabs. So again, I suggest you look at the preface because this committee has listed out all the changes one by one or at least a summary of the changes and inclusions. The main objective that the technical committee had in this instance was to develop a fit for purpose document that could be readily used by industry and, you know, achieving the minimum levels of safety needed, but also allowing for innovative materials that are now in the market. We also note that there are some really helpful appendices in this new edition with a few design flowcharts, so practitioners using this standard will hopefully be aided by those appendices. On to cold-form steel structures. We see in the market now that there is a continued or an increasing use of, say, flat-pack systems or modular constructions, so again, this committee did a lot of work to update 4600 to ensure that it reflects current practice. The committee did a lot of alignment with a US standard out there, and it's NASS 100 specification, but what they have done is incorporate a lot of Australian and New Zealand research because, obviously, we reference a vast number of Australian standards in the documents, so the research needs to align with what we know in our industry and use in our industry. Again, a lot more has changed than what I have put up on the screen, so I do suggest as a first instance to look at the preface if this relates to you. Now, on to fire standards, which is a hot topic to try and put in a few puns, dad jokes. So probably one of the most or one of the higher public interest standards that we have is 3959, so the construction of buildings in bushfire prone areas. With this standard, the technical committee is continually receiving feedback from industry, from the community, so there's a lot of work that goes into the development of this standard, and the committee is moving on a bit of an incremental approach, so with every new addition, they will incorporate a particular amount of research and development, but know that it's stage by stage, so just to let you know that there is still work underway on the next sort of list of priorities. Obviously, you know, we're right in the middle of bushfire season, so the particular purpose for this revision was to incorporate a lot of research on the performance of buildings in bushfires. There's a lot more knowledge about this now, and then reflecting on what's been happening with NCC 2019, a lot of the work done by the committee was actually about readability, hopefully phrasing the same requirements, but in a way that can be more consistently interpreted across the country, and in addition, the committee tried to again increase options available for practitioners, but achieved those same levels of safety that are needed with this important standard. Another item to note that this standard is also published in conjunction with updated test methods, so the 1530, 0.8, 0.1 and 0.8, 0.2, so those test methods are also updated at the same time, so if that is of interest to you, we've got 3959 as well as the test methods new additions. Moving on, because there was a lot happening in the fire space, our fire committees were extremely busy over the last three years. Obviously, some big changes to the 1670 series. We've got a lot of the work with the 1670 series particularly, was the alignment internationally with a lot of international product standards that are out there. The benefit of aligning internationally is obviously the reduction of costs, so if you're importing product that isn't manufactured in Australia, having to retest or recertified to Australian standards is obviously an imposter and a cost impulse, so the idea of alignment is that we can participate in the global market. A lot of the work was to fix ambiguities. With part one, there was a significant amount of work to deal with false alarm mitigation technologies, so there's a lot in these standards. Again, look to the preface for more information, and you'll also note part four with the new EWIS name that Graeme mentioned earlier in the session. Especially with these standards, there are transition periods in relation to the product standards and the testing, so look to schedule for more information about that. I didn't want to cover amendments because they're usually smaller than the significant revisions that are out there, but this is quite an important one to highlight for you. 5113, there has been a name change, so just be aware that that's happened. This amendment also included the addition of a new appendix, and the appendix outlines the relationship of the standard to the MCC, so that hopefully it can assist people to achieve compliance. I know there was a lot of discussion in the industry about debris criteria and what that meant for compliance with the performance requirements in the code, so if you've already purchased 5113, you should be able to access your copy of the amendment for free. If you're purchasing 5113 in the future, that amendment has already been incorporated into the content, including the name change. On to my catch-all. I know there's a lot more that I need to cover, but I'll do my best. The first one of the catch-all category is AS5216, so it looks like a brand new standard that's been incorporated into the code, but it's actually not. I don't know if any of you have been using the technical specification 101 for fasteners. That was referenced in the 2016 edition of the MCC. The reason it was a technical specification was to achieve speed to market to address a critical safety area about anchorage into concrete. Now that we've had another three years, we've been able, or the technical committee has been able to confirm that as an Australian standard and go through the robust process of an Australian standard development, in relation to changes, it's usually minor editorials, so not much has changed since SATS 101. On to the metal roofing standard. So we, Graham was mentioning all the work that the ABCB has done in relation to metal roofs and cladding. That required a significant piece of work with this particular standard and committee. The previous edition of this standard was in 1992. So we've had roughly 30 years without any changes. Metal roofs quadrupled in that time, so again this committee has a significant piece of work and a lot of changes to get the standard up to speed and actually to not or to reflect the testing requirements that are in the NCC. So the previous edition didn't even meet the testing requirements that the NCC required. So there's a lot of work. Again this list is not exhaustive, so I do recommend looking at the preface if you want to know more about the changes. The main changes are the incorporation of current test methods and practices in the industry and bringing it up to speed. On to 4200. So Graham mentioned earlier all the work that the ABCB has done on condensation management. The updates to this series is also a reflection of that. There have been quite a large percentage of warranty claims due to poor installation practices and inappropriate product selection. So the aims of this committee were to improve the readability and make sure that the interpretation was more consistent. So there's a few changes there. I'll also note that this standard ties in with the transition period for the energy efficiency provisions. So again look to schedule 4 with that. Also moving on to 4859. Again these are tied into the energy efficiency provisions. The original intent of the original 4859 standard was to provide a consolidated reference for assessing the thermal performance of a number of different products. What this new addition does or these new additions do is separate that out. As a designer previously you had to go through the standard to find the little bits of sections that apply to you. What the committee has done is separate that and try to make it a bit more understandable. So if you're a designer you can actually just refer to part 2 rather than trying to search through the document and see what's applicable. A lot of the revision was to try to assist practitioners in selecting the correct product for the system. So hopefully this standard goes some way to helping practitioners use these products in the industry. So of course I can't cover all the standards. If you do have any questions about particular standards please approach me after the session and I'd be happy to give you more information. But again the comprehensive list of changes, deletions, amendments is available in the seminars section on the ABCB website. But a little bit about standards Australia and what we're doing in the future. We have recognised the need that people no longer want to bring a book or have a PDF with them on a building site. We realise that standards need to be searchable. You want to access it on your phone and not have to figure around, play around with tables to view them all. So we launched the incubator about a year and a half ago and what that is, is we get to experiment and test a bunch of different ideas to do with process. So the development of standards and products. So how people use our content. In terms of processes we've got the usual development of an Australian standard but we're also testing ideas such as crowd sourcing. So one of the projects we're doing is we're crowd sourcing the development of information about building commissioning. So if you're interested please find me in the break or send me an email if you want to participate we'd love to have you. In terms of product development we're looking at visual standards, we're looking at digital standards so the standards that actually do fit to your phone. We're looking at calculators and workflows. We really want to improve the ways that you can access our content and understand our content. We're also working with ABCB on a project to do with standardised terms and definitions. So interestingly enough terms and definitions aren't particularly standard across our standards and this proof of concept exercise has tested that and so if you actually search a term we can see how that term is defined whether it is in the NCC or whether it's in an Australian, a referenced Australian standard or in other sort of documentation and we also want to sort of give an idea about hierarchy. So if you're looking at something like a wet area what actually takes precedence in terms of definitions. This is a great proof of concept it will help us align more as an industry and keep your eye out for further tests in the next months and years as we try and develop solutions to make your life a bit easier. Standards Australia is continually working on making things easier for you to interact with us. So amongst a range of initiatives that we have been doing over the years we've had our technical governance review where we're looking at our systems and processes to try and make things more transparent for the industry and for the community. We've got the connect platform for committee members to contribute with us a lot easier. We have a better public comment platform for any member of the public to comment on drafts released for public consultation and we're also looking at our next-gen program which is encouraging the next generation of contributors to standards. So if you do have any questions about this please feel free to contact me. Now before I move into questions I thought I would deal with the elephant in the room a question that we are asked at pretty much every single seminar and the question is when will standards be free? So with that in mind I thought I'd address it right now with this and the message is to all of you that Standards Australia has won the right to move beyond exclusive distribution arrangements with SAR Global. That is a landmark achievement for our organisation and we're really excited about the future. We had an independent arbitrator assess what market terms do look like in the future and the future is non-exclusive. So over the course of the next year Standards will be working extremely hard, consulting with industry, consulting with the government, consulting on what exactly that future looks like. So there's a lot of things to consider, a lot of different models that we need to understand so please be patient with us as we work over the coming year. If you're interested in talking with us about our distribution models please contact us and I'd be happy to forward you on to our executive so that you can have these discussions. But in terms of the free standards question my answer to you is watch this space. We're really excited about this opportunity but we're working through those models about how we can maintain our relevance for you and be more effective in the way you can access and use content for the future. Moving on to questions. Any questions? No? Thank you very much.


All right, as you can see we're having a little technical difficulties, but I'll We'll work around them. So my name is Christian Hernandez. I'm part of the Red Hat Clap Platforms BU My social handle GitHub Kubernetes Slack is Christian H814. So you can hit me up there In either one of these avenues. I'm usually pretty responsive So today I'm going to be talking about GitOps the holy grail of DevOps. So I'm going to be going first over kind of just defining what DevOps is a little bit just to make sure we're all in the same page And then I'll kind of go over the history of GitOps and how it all fits in. I Also had a demo planned but since I'm not using my laptop I guess we can use that demo time for questions and answers or I couldn't show you on the outside if you like so So first of all, what is DevOps right so What DevOps is Really is like a it's a methodology and it's practices, right? So it's It's not a department, right? So I had a long time ago when We first started doing DevOps and in my previous company there was a guy that would say oh the these two departments will never work together Right, it's not one in that I had to like explain. No, no, it's it's not a department. It's it's a it's a way to work, right? Dev and ops work really closely together, right? Before there was a there was an idea of you know throw it over the fence, right?  So now this is more of a methodology of working together being able to Solve problems and no longer throw throw the throw the code over the fence as it were And it's meant really to shorten the development life cycle, right? So you there was a lot of talks today I just listen to a talk on tecton About CI CD, right development life cycle, you know why that's important for fast delivery and really DevOps is a way to Deliver those things rapidly, right? It's also meant to have a higher quality software, right so when when everyone is working together the the issues that come up can be fixed quicker is what the idea is really and What I like to what what I actually seen out there is that the application stack now is seen as a whole Responsibility right so no longer is like, you know again I do the analogy of throwing the code over the fence is no longer is like, okay You know now it's their problem now It's the the whole stack as a whole is seen as like an atomic unit right from the From the development all the way down to the infrastructure component is all seen as a component so So when I talk about DevOps is I'm kind of using these Methodology you can agree or disagree or whatever, but just in the context of this talk This is how I'm gonna view DevOps And really really how did we get here, right? So there there's there was the buzzword of DevOps has been around for a while but really Really it's really come into fruition in the past. I would say five years or so and And really really how did we get here, right? So I was debating on where where to start this How did we get here, right? I was gonna maybe maybe start of You know In the times where we're rocking rocking servers, but really this is all started where virtualization, right? is really when we started getting into the the idea of a rapid development So with virtualization came with the idea of like snapshots and cloning and With that you'd have really like a template of what What the infrastructure looked like for your application, right? You would you would build a server with all its components and libraries and you would Clone those right like this is my application foo and that's the server for application foo And this is how I'm gonna stamp them out And there was a lot of tools for for this automation, right? Tools like a puppet chef later on ansible. I know I've used chef exclusively in my my former former life and Those tools were were made to automate a lot of those right especially with virtualization and some of those cloud instances right like AWS You can really have this in like this idea of infrastructure as code, right? You can define what your infrastructure looks like programmatically, right? The kind of challenges that I really came up with that Is that you still get the idea of of a one-to-one relationship, right? So you really get the idea of okay. I have I have a server and I'm cloning it now But that whole server is still defined as the application, right as part of the application This service it's it's eventually it still turns into into a pet, right? You have you heard that that phrase pets versus cattle You still have that idea of like this VM is still a pet because it's still specific to the application, right? so all of these tool sets Gave birth to what we call an SRE now so SRE You know before I said that DevOps isn't a A Department if it was the SRE would be they would be part of that department, right? Or they were at least spearhead those that department if it was one But these these are specialized people that know the application so when I said before the application stack as an atomic unit These people know that entire stack, right? So they're really an extension of dev and extension of operations they They really Take care of the application once it's up and running they they submit patches. They they they monitor They do all of those things that need to be done for that application stack. So And that's kind of like the the progression Then after virtualization came this thing called Docker, right? So Big buzz right of Docker before What docker really did is it took the concept of LXC's Linux containers and simplified it, right? They wrote an interface to be able to Like a package and build these containers I remember when I first thought Docker out like many of you I was like blown away. I was like, oh now This this changes the game and actually I think it really did You're able to To build these containers Readily and easily and actually they wrote a really nice workflow for developing Applications and packaging goes up right because they give you an idea of bundling your your application everything, right? All the dependencies everything needed to run the application is built into this this this atomic unit, right? we talked about I talked about atomic unit a little bit before and It's really Containers is really nothing but a It isolates processes right it isolates By processes and namespaces inside the kernel, right? So no longer do you need? The entire operating system in order to run your application You just need the bits that you need to run the application and with the isolation inside Colonel namespaces or in C groups and all the all that nice stuff that you get with Docker You're able to now run you get you actually get multi-tendency now, so you can run multiple Applications without having to worry about oh, yeah, I need this version of the library compiled versus this version And now you're able to run those two different versions right inside side the Inside the operating system, so they're immutable right so which which is really cool because Before with with VMs and puppet and you know ansible you get the problem with drift right so You get the problem with drift until like you run that that sync that makes everything What then the state that you want it right so here with containers they don't really change right you say I want this there since since with tagging you say I want to this version this shot to run That doesn't really change right they did so they're they're They're immutable from that fact the You're able to run it the way you run it runs on your laptop is the way it runs on a server, right? So that's that's I think that's very very powerful, especially with dev devops, especially with that idea of throwing things over the fence Even if you're still doing that right now, you know exactly what you're throwing over the fence It runs the same so you know the only thing really changes is the environment underneath right so So right problem solved right all the problems are solved right so now when you build an application It's easy right docker made a good interface docker build run right my app version one and With the same interface you can run it right docker build docker run easy command line interface And now you can actually see how You can start plugging that in into okay now that I built and I run this container I could run it anywhere physical virtual environment private public cloud all that good stuff And then you can also see how you can plug that in Dressy CI CD pipeline Right, so you have you know developer and then you have a source core repository And then you have some sort of CI CD engine Jenkins or tecton And that builds the container and then you can then deploy that container, so it's starting to come together right so But Application stacks are rarely that simple right so you know even the most simple Application comes at least with the front end back in and a database right maybe have a caching layer So they're more complex than just a few containers right so you usually have a You know usually have a few servers running a few application stacks over a dozen servers, right? So now you think okay cool. I can do okay. I could build the front end back end database cache messaging whatever you need for the application You I built that the same way you can think right and then when you run it then you have to you know kind of think okay well I Run my friend it will not need two front ends right because you know you want your ha so I have two front ends and I to make Sure I link it to the back end well now I have two back ends right because I want that ha so I want to make sure I link that to my database and caching system I want to make sure My caching systems linked to the DB and you just kind of just have to keep all that in mind right so this This is one application stack So now you have that one application stacking you have a way to link it and okay Well then but now when you want to that's fine if you want to deploy it to like you know, maybe five servers, right? Maybe even ten servers But what if you have dozens of applications over across a hundred hundreds of servers? Then then it becomes maybe not that manageable right so as Y'all may have guessed the answer to that question mark right there is Is It's Kubernetes. Sorry these slides were out of order. It's Kubernetes, right? So Kubernetes came in and Really answered the the following the following slide right so You need more than just containers So just containers itself is not solving anything right you need scheduling security Health management persistence, you know all that stuff right so you need more than just Running containers and this is where Kubernetes comes in place right so Kubernetes takes care of all of that for you right so I have a container. I want to Be able to deploy that container the application stack Across you know hundreds of servers and I want to be able to link them all together I want to be able to do health checks. I want to be able to do Rollouts deployments right all that stuff Kubernetes takes care of for you Alright cool now that we have Kubernetes That solved a lot of that that problem itself right so now Kubernetes really Just to from a from a high level Is it really a declarative way to describe your infrastructure or deployment application deployment right so? It's in Yamal and Jason right so really anyone can read it like right even the ops guys can read it It's it's you know you may have hundreds of hundreds of lines of Yamal, but at least you know you can read it whereas You know it before when using tools like puppet and chef and even ansible to an extent You really have to learn the language or learn. It's like a coding scheme more than in It's not as there's a learning curve there right there's still a small learning curve with Yamal and Jason But it's you know you can easily read it Yes Okay, yeah, let me take this off here Is that better Maybe it's this thing is that better? There's a still hello better a little bit. All right, I'll try not to move Yeah, so A Kubernetes really What it really does is monitor state right so you it takes the desired state and the current state and it reconciles it so It'll be things like I want you know three instances of my application running and it sees to it'll spin up another container to meet That right so it's it really has it it has a control loop that basically monitor state your declarative state Versus a running state reconcile high-level Right is that easy? It's not just for containers anymore right so with the With the introduction of CRD CRD's custom resource definitions You can really program anything Into it right so you can if you know a little go we could pretty much program anything into a CRD and and CRD custom resource definition, so it's just real quick from a high-level CRD is a way to program things into Kubernetes without having to write it directly into Into the the tree right so it's it's basically like an extension of Kubernetes right so you can say so like there's things like pod Deployments you can write databases right and whatever databases is is whatever you define it as And you can further get further automation with operators right so this is Just from a high-level operators is writing operational knowledge into your CRD's so if there's a there's a talking operators I'd recommend you guys to go check that out so it's it's really It's really cool technology to be able to automate a lot of this stuff for you so So just my thought Kubernetes high high high level it abstracts the underlying infrastructure So I attended a talk long time ago, so This this will tell you how long ago it was it was a Kelsey high tower, but it was back when he was working at Coro s That's how long the talk ago was And just talking about Kubernetes v1 right so 1.0 He I think he explained it said something very elegant that how would you design a system if I took your SSH keys away, right? So as an admin as an operation as a developer if I took your SSH keys away How would you design a system and really that's what Kubernetes is it abstracts the underlying infrastructure So that way you can interact with the infrastructure and the the the VMs the the instances really just become a method to run containers And there's really no need need for you to SSH in right? That's the idea. So I Think that explains it really well. So if I imagine I took your SSH keys away so Kubernetes is right so How does get ops fit all in all in all this right so now that I went to through the through that whole history and that whole Thing about Kubernetes. What is get ops right so get ops very similar dev ops is a Is a series of methodologies and practices, right? The idea is is that use get as a canonical source of truth For everything in your infrastructure. So with Kubernetes Before you you had like I said before everything's defining YAML and JSON. We'll Just store that YAML and JSON in get the whole thing the idea with get ops is even the the Platform itself all even the Kubernetes itself all that export all that and put it in get and that becomes your canonical source of truth so any changes or Actually, let me backtrack a little bit the entire system described declaratively right so verses so you're talking about a Series of facts versus a series of instructions, right? So that that's it's a small a small Distinction right you're thinking about like ansible puppet Chef those are a set of instructions versus get ops the idea is this is a set of facts, right? So get out get ops Says like this is how the in my infrastructure Looks like everything right so any changes you want whether you're an operations guy developer whatever I Need to do a pull request, right? So I want to change the scale of my application pull request. I want to add another node in the infrastructure That's a pull request. So everything is declared Inside of get so that's that's the idea with get ops, right? Software can be used to reconcile differences, right?  You can use this shell script But there are tools out there With two the biggest one is a flux CD and Argo CD. I'll be talking mostly about Argo CD But you can use software to reconcile those changes and Some of these tools like Argo and and flux which I'll talk about a little bit Uses CRDs, right? So it takes advantage of the control loop that's built inside Kubernetes to be able to reconcile those differences for you, so And I don't know if I mentioned before but changes can be automatically applied, right? So with that with that process, right the automatic changes, right? So some of the the benefits of using get ops is that since you're storing everything and get all of a sudden you get this convenient audit trail Right, you you know exactly what changes were made when and by whom so you get the compliance and stability of Leveraging your your your source control management that you already have in place, right? So you get reliability as well Consistency and standardization right so since you're using get ops You know that this is the the way to do it right in your environment Whether you're in dev staging production, whatever the way to get things through is through through get through pull requests, right?  So generally makes life easier, right? So It's it's as easy as all you need to change is submit that pull request Which makes life easier It speeds up recovery time, right? So I read they read this article about the guys that we works That someone accidentally deleted their infrastructure Like, you know, it sounds weird, but like stuff like that happens. I know I've done blunders in my career as well But someone actually didn't know what they were doing. They actually deleted their the entire infrastructure And they brought it back in 15 minutes Just by applying the get ops practices, right so And get ops really becomes a way to manage your Kubernetes infrastructure, right? Whether you're running Kubernetes or OpenShift it becomes a way To manage that system. It's how do you manage your Kubernetes system? A Lot of people say I just use get ops and that's how I manage my Kubernetes system there So so if I'm storing everything in a repo, right, how's that repo laid out, right? So Some of the things and some of these things I've gotten by attending some talks Mostly by the we've works guys But these are some of the things that pilfered from those talks is that only use one repo, right? So like you'll have a repo called foo. You won't have foo.dash stage as one repo foo.dash prod another repo foo.dash Right dev and another repo you'd have just one repo And you'll use branches, right? So you use a branch To determine what environment you're in or what stage you're in However, you're gonna you're gonna design that system You'll use one branch Use protected branches so protected branches important right in case of accidental change accidental deletion Use code review, you know all those best practices that you should use and get we use and get use it The same and get ops is the same idea, right? Leverage customize right so There's a there's a few ways To do things like overrides, right? So for example if you want to do like a like an a b deployment blue-green employment Or you want to change scale, right? So you have multiple clusters in one cluster you want five instances running and the other one you want I don't know maybe three or four If you're using the same production repo, how do you override that so you do overrides and Think with things by using a customize, right? So you can change things like environment variables Scale different clusters if you're managing multiple clusters with get ops you use customize Question that came up a lot was so what I do with my secrets, right? So in Kubernetes I'm using secrets database connections Things like that right usernames passwords. I don't want to store that and get Bitnami has something called sealed secrets That you can use is basically you're storing you're actually are storing your your secrets in get but they're encrypted and they're decrypted on the platform, right? That there's also other tools that you can use for that there's things like vault right ansible has also a way to store Encrypto secrets, so you just need a management system to Store your secrets, but you yes, the answer the question is yes, you do store your secrets you just need some sort of management system and Encrypting the secrets is probably the best practice. Yes question Yeah, so you can so the idea is to keep track of what's going on in that in that app In that cluster itself or in that deployment itself so you would have one Main repository and different branches will then say I have a branch called foo, and I have sorry I have a Repel call foo and have a branch called prod for example have another branch called dev That's that's the that's the idea behind that you have one deployment would be a deployment of of An app like not the whole application stack it could be it actually depends right it depends how you how you're designing your Your application, but I see it as you'd have foo is one component of One component of you know like microservices right because you want to track those differently. Yes You could use master branch. I don't normally use master branch. I use it. I Normally have branches Depicting on where I am in the in the environment.  That's fine But I usually just branch them out differently So so again like I said before there is there's two I guess before I said you can use any any tool to reconcile those Two of the biggest tool sets is flux CD Flux CD was developed by the guys that we've worked and then they donated it to the CNCF right so it's a CNCF project Argo was actually developed by the guys over to intuit And That's That's really the tool. So red hat has been kind of just observing what's going on in get ops Get ops has actually been around for a while It was really pioneered by the guys over at we've works Right now was kind of monitoring, you know, what's going on how that evolved but eventually red hat is a settle on going to Argo We actually have an operator on Argo. So if you go to operator hub You'll see there's a community version of Argo Up there. I'm not sure are we do you know if we're including Argo in an open shift eventually For So yeah, so what we are We are going to include it in in In open shift eventually I'm not I guess I'm not not 100% sure when but we are Going towards Argo. So As soon as we decided we're going to Argo this thing happened a number 14th We've works and into it join forces And they created something called Argo flux, right is what they called it I guess it's just a codename for now. I would have called it Fargo, but that's just me AWS also did a joint announcement saying that they're getting involved in the project as well So they're building a community around something they call the get ops engine, right? I Intended the first meeting what they really really what get ops engine is is that okay? Well, we have the two different tools that do a lot of the same thing, right? They may they may have different end user experience, but at its core is doing a lot of the same thing So really they wanted to Take any pre-existing functionality. That's the same and just kind of that's not duplicate code It's really what what what their what their idea was It's not intended at least for now to be like a like a framework or anything like that It's it's really what they wanted to do is the wanted to create a library, right? So it's essentially right get ops engine. All right get ops engine. We have Let's not duplicate code. We have all the similar code Let's make one code base and then from that code base then we'll branch off to our respective tools And that's what first step that's what they want to do now The idea eventually is to have some of these one tool to rule them all sort of idea It's still in its infancy so the idea is is It might change so they're still talking about how that's gonna look like how it's you know gonna evolve from there Who knows so things are subject to change but Yeah, this is so new it's still evolving right as I was building this presentation They came out with this, you know after red hat decided. Okay. We're gonna do Argo. No We've worked send into a said we're joining forces. So we're still continuing monitoring that so I Had a demo so I had a demo actually to take up the rest of the time so My laptop isn't working And it's all in my laptop. So Is there any questions Yes Yeah, so the yeah, so the question was is about a get workflow. This is a is a get workflows With the different branches the same right as you would in the development the answer is yes Right, so you would make a change to your dev environment by doing a poor questing your dev And you would have some sort of process To promote that right so you'll have the dev branch then maybe deploy to the dev environment It'll sync that up. You'll see that at works fine. There's some sort of Approval process that goes through that whatever that may be and then that gets merged into let's say staging right and then it'll continue on from That so yes, so you would treat it like you would treat your code. Yes question So he's talking about tests right so if I make a pull request, how do I test the poor request? So ideally you would have a testing environment that you would see those changes so the The Some of the things that you get when you do an application deployment You also get when doing get ops as well, right? So if you for example, you say I want to scale my my infrastructure I want to add another note for example, that would be a pull request That would go into your dev environment and if that goes horribly wrong You can always a revert back because you just use the same the same process and get You leverage get to do you like your rollbacks or or anything like that For your tests your test could be anything really whatever you Put into Jenkins is what you test. It's mostly you're testing the application stack So you would just still test the application stack to see that doll. That's fine But you would do some tests as well for the infrastructure Some of these tools do some testing for you a little bit and We'll do some of the some of the rollbacks. I did have a demo for that, but Technical difficulties, but that answer your question at least a little bit Okay, okay There any other questions Yes Yeah, so the secrets as I yeah, so here you would essentially encrypt them right so you would have Let's say a config map with a username and password. Let's just say for example You would encrypt that with some key that's already stored on the platform and then you would you would store the the garbled up, you know Config map in get so when so when the sync happens when that tool sinks it It'll actually decrypt it and put it on the platform for you. So you would store your secrets Encrypted on on get somewhere that would that would be on the platform So you would it would already be on the platform So yeah, so that you'd have to have some sort of workflow That's why bit Nami a sealed secrets is good. You have to use some some tool that would manage that for you That would make a lot easier Yes question Also, the question was is the seal secrets a CRD of Argo city. No, it's a sealed secrets is its own project By a bit Nami so that would be it would be a CRD in but it's it's not it's not like on Argo or flux There are plugins and for flux for sealed secrets. Just not an Argo cool. Is there any other you have eight minutes left? I can leave that you guys go a little early More questions Okay, all right. Well, thank you very much