He is a native of Liverpool, of course, but lives in Paris, has done so for a number of years. He started as a journalist and then contributed articles to some of the main British newspapers. His research really focuses on extremist tendencies in French and North African politics and culture. His latest book is called The French Intifada, and if you haven't read it, I would highly recommend it. He's written for, as I say, many great newspapers. He's lectored throughout the world at this stage, and his books are on the university syllabus throughout the world. In September 2014, he published in French Guy Debord. This was a book originally in English from 2001, The Game of War, The Life and Death of Guy Debord. For those of us who are not familiar with who Guy Debord was, he was one of the leaders of the 1968 troubles, I suppose, of the work in France, and he then went on to be heavily involved with the Red Brigade and the Bader Meinhof. Andrew is extremely well-qualified, and this is a subject which we have been dealing with at the institute in the past, and which I'm afraid we will probably continue to deal with. Of course, so much has changed even, Andrew, I think, as you point out, since you published The French Intifada. There has been the growth of ISIS, the collapse of Syria, and of course the terrible attacks in Nice and Paris. So without further ado, Professor Andrew Huttie. Thank you very much. The Atrocity Exhibition, Tensions and Challenges in Contemporary France. Now before I begin, very quickly, I'm going to say there's a subtitle to this, and the subtitle is this, The Politics of Atmosphere, and that's a phrase which I think is very useful to begin with. It was first used in the 1930s by the novelist Georges Bataille in 1935. He was struggling with his own loss of faith in revolutionary leftist politics, and the rise of Nazism. But what he was really talking about, Bataille, when he talks about the politics of atmosphere, is that there were certain moments in history where emotions, extreme emotions, dominate political discourse rather than logic or reason. And this is where you slide from politics into psychoanalysis. And that's kind of where I'm going to go to today. Now there's another subtitle, and it's this. There's a lot of things happening in France. There's a lot of very complicated things happening in France from the geopolitical influence on the country to the local conditions in the country. But my focus today is on a very old historical French problem, and that is antisemitism. But what I want to look at is, if you like, a 21st century version of antisemitism, which is aligned with radical Islam. And I'm going to try and unpack some of the historical roots which have led to this situation. And without any making any predictions or prophecies, I want to provide a kind of analysis, or at least a diagnosis, it's probably a better word, a diagnosis of the extreme emotions in France now around this very difficult subject. Does that make sense as a way in? OK, good. The atrocity exhibition. It's hard to describe exactly what happens when a whole country goes into shock. But on Monday, the 19th of March 2012, the most visible signs of trauma in Paris were armed soldiers in shopping malls and train stations, bonolets on the metro, and despite the sunny weather, far fewer customers than usual at the Café-Terras. More telling still was the subdued atmosphere everywhere in the city. Certainly by the time of the evening rush hour, there was a distinct sense, and I remember this, because I was in Paris at the time, that everybody wanted to get home to safety and to the evening news on television. The reason for all of this was the news of the murder of a 30-year-old man and three small children at a Jewish school just outside of Toulouse. That morning, as Rabbi Jonathan Sandler was dropping off his two boys, aged five and three, at the Osahatora school at about 8am, all three of them were shot dead by an armed man on a Yamaha T-Max scooter. Other teachers and pupils thought at first that the noise of shots was fireworks. But as they approached, they saw a terrible scene unfold. The gunman had seized on an eight-year-old child, Miriam Monsonego, the eight-year-old daughter of the school's director. She was being pulled back by her hair. The gunman then blasted a bullet through her temple. This scene was captured by security cameras at the school. Low number of people have actually seen this footage. For most of France, for the image, first there were theories about a Rogue soldier or a neo-Nazi psychopath on the loose. These theories gave credence by the fact that the previous week bydd y ffaith yw'r gweithio'r gweithio'r gweithio'r gweithio'r gweithio'r gweithio North African in being killed in the same region near Toulouse, by someone using the same weapon and techniques. But then, if such a thing was possible, given this news, events took another turn for the worst. At 1am on Wednesday 21st of March, an editor at the French news channel France Von Katra, Eber Colondo, was just about to pack up for the night when she received a call from her phone box in Toulouse, from somebody who claimed responsibility for the murders. She heard a young man, apparently in his 20s, very calm, who spoke impeccable French, placing a great weight on his words. This is what she said. Within two hours, the French police had traced the caller, Mohammed Mera, to a flat in a building at 17 Roud de Saint-Jean-Bigny in Côte-Pavie, a suburb 20 minutes in the centre of Toulouse. It turned out that Mera was not only the owner of the Yamaha scooter, but also heavily armed. After an initial attempt to break into the apartment building, special police units settled down into a siege. In the next few hours, Mera claimed to have filmed the killings at the Jewish school and given the tapes to his brothers to distribute on the internet. He said he was going to trigger assaults in Lyon, Marseille and Paris. On Thursday morning, Mera again confronted the police as they made another assault on the building.  It was only then, at that moment, that the full complexity of the story began to take shape. As Le Mold described it, from this point on, the murders were no longer en ffet d'hiver, which is a term that the French used to describe any kind of generic news story, but it became en ffet politique, a political fact, a political story. And this much had actually been anticipated already, I think, by Presidents, the then President Nicolas Soccuzzi, who'd gone straight to Toulouse on Tuesday afternoon in his traditional role of the protector of the French nation. Other politicians, with the notable exception of Marine Le Pen, publicly undertook not to make political capital out of the killings. And the real issue here was a question of denial. It was the immediate reaction of the French government and the media, actually, as the killings were being reported to actively disassociate Meher from anti-sanitism and thus from Islam. The real issues they suggested were immigration, unemployment, psychiatric problems. But for all of this confusion, one fact was clear enough at least for the Jewish population in France. These killings were obviously an anti-Semitic act. Now, this might seem a strangely obvious thing to say, but it's a fact that the question of what is and what isn't an anti-Semitic act in contemporary France has recently been the subject of much debate. That's not to say anti-sanitism doesn't exist, obviously. Obviously it does. It's well documented that anti-Semitism in various forms has been on the rise in France in the past decade. For one thing, more French Jews have been leaving for Israel than ever before as a response to this. So whatever the political and media reluctance to discuss anti-Semitism as a separate category of politically motivated racist activity, it's clear that French Jews themselves know what is happening and understand the potential dangers that lie ahead. So what I want to do today, the overall aim of this talk, really, this lecture, is to describe and define what's happening, to describe and define the various strands of anti-Semitism which are now at work in France and how, first of all, they've been making an impact on Jewish communities, but most importantly, the wider French political landscape. Most crucially, most importantly, what I want to do is also make the case that what's happening in France now is actually a new form of anti-Semitism. And, you know, there are new forms, new varieties of anti-Semitism which seem to be related to each other but actually have the tangled deep roots in the common soil of French history. And more to the point, it's true that since the end of the Second World War, France has largely been in denial about the resurgence of anti-Semitism. And most particularly, there's been an unwillingness to engage with the new and mutated forms that it's taken. But I do think that the political issues here are crucial. And this is partly because, on the left in particular, it's been a long-standing taboo to be seen to be taken the Israeli side in the Israel-Palestine conflict. A much anti-Jewish feeling on the left is confused with anti-Zionism and the desire to be on the side of the former colonised in the post-colonial world. And, you know, there's a book which is called The Llewer of Anti-Semitism, Hatred of Jews in Present Day France by Michel Viocca. And he describes, it's a very good book, he describes contemporary anti-Semitism in France as inextricably linked to colonial history. And in particular the history of the Pinoir, the white settlers who returned to France from North Africa after the French handed independence to Algeria in 1962. And Viocca also links this history to what he calls islamo-progressivism, which is a term used by the philosopher Alan Finklhout and which is linked in contemporary political imagination to the merge of Islamist strains of thought and leftist post-colonial narratives. Well, my feeling is that Viocca is kind of right and that the process he describes has in fact accelerated and taken on a harder form in the past few years. It's also part of my argument, I think, my thinking at least, that as Islamo-progressivism has popularised itself, there's been an emerging anti-Semitic counter-narrative from the right and in particular the Catholic nationalist groups which have rallied round the issue of gay marriage. The academic Pierre Bernbaum has written very powerfully about the convergence of what he describes as convergence of anti-modernism and anti-Semitism. This is in a recent book called C'est un nouveau moment anti-Semite. And he notes that the right, and I saw this actually at Anthe Leed, he notes that at the right-wing demonstrations against gay marriage in 2014, the slogan La France of França was often apparently incomprehensibly accompanied by the cry, cry, Morrojwif, Death to the Jews. So it's trying to understand what brings these apparently very different slogans together. And I think one way of thinking about it is following Bernbaum, is that he sees here a very real alliance between Islamo-progressivism, progressive east, who are open in their contempt for Israel and the coalition of religious groups in and around a right-wing caucus in the Catholic Church. So this debate, I think, is intensified since the killings which took place in January 2015, and then November 2015, which were aimed very precisely at the notion of the Republik Andy Wiesieble, but also as a way of attacking the Republik Andy Wiesieble. You can see, or at least I'm going to try and make the case, that one, as it were, is a particular way of undermining the French Republic is to aim very squarely and precisely at the Jewish population of France. And that's why I talk about a French intifada, or if you like, a new anti-Semitism for a new century. And it brings us quite sharply to the language of radical Islam in France in the 21st century. And going back to the crime, I'm just outlined at the beginning in the mind of the Islamist, in the mind of a killer like Mohammed Merah, it is a double crime, a double crime to be French and a Jew. Now, in some ways, this has a historical origin. And as an origin in colonial Algeria, actually, where Jews apparently enjoyed special favour status under the same French law that apparently excluded Muslims from citizenship. This is the Loire claimer in the 19th century. So historically, for a long time, Algerian Muslims have always thought of Jews as traitors, as traitors who took their own country by stealth in the colonial project. And this belief system, like a lot of belief systems, no matter how much you repress it, keeps coming back. And, well, this was something that I investigated as an academic and a journalist. This was the torture and murder in 2006 of a 23-year-old mobile phone salesman named Ilan Halimi. Halimi was kidnapped in central Paris and it was driven out to the Bannu of Bannu, in Syria. He was Jewish and he'd been invited out for a drink by a young Iranian woman who was called Yalda. He met her while he was selling phones. It turned out her mission, Yalda, was to trap him and to lure him away from safety. Yalda later described in police custody how Ilan had been seized by thugs in Balaclavas in central Paris and bundled into a car. He said he screamed for two minutes with a high-pitched voice like a girl. Three weeks later Ilan Halimi was found naked and tied to a tree near the RER station of San Geneviève de Bois in the Bannu. He died on the way to hospital. His body had been mutilated and burned. Since being kidnapped he'd been imprisoned in a flat in Bannu, starved in torches. This is one of the things that I found really shocking when I went down to Bannu and I interviewed people who'd been in the building at the time. They all knew about it. Residents of the apartment block where he's been imprisoned, they'd heard his screams and the laughter of those torturing him. But they did nothing. They did nothing partly because they were scared of the gang who kidnapped him. This was 15 youths from Bannu who were part of a gang called Libaba, the Barbarians. There were a loose coalition of hard cases, drug dealers and girls who were drawn together with the hatred of what they called rich Jews. The alleged leader of the Barbarians, Yousif Fafana, is now serving a life sentence in Clareville in the east of France. He published videos in which he praised Al Qaeda and from his cell in Clareville he described the capture and torture of Al-Halimi as a symbolic trophy for the Zionists of New York. And during his trial he described how he doused Al-Halimi in petrol, set fire to him with a cigarette lighter and he said that he was proud of what he'd done. Well, again, what is the political, is there a political significance to all of this horrorism? Well, this is what took place in France. There were a lot of theories about the crime but they're pretty confused. Was it a bungled kidnap? Was it a clockwork orange style act of pure sadism? Or was it anti-Semitic? It seems bizarre to even have to ask that question. But the police didn't ask it. The police were in fact very reluctant to link the crime with anti-Semitism.  But while the police and then the government were denying that anything happened, and this is what I discovered when I was, again, out in the bonnier interviewing people, was the murder itself took on a skewed new meaning. The word was that what had begun as a heist and kidnapped to extort a ransom for a rich Jew was actually a form of revenge. Revenge for crimes in Palestine and revenge for crimes in Iraq. And in particular, and this is what these kids acted out with Elan Halimi, the scenes from Abu Ghraib. They re-enacted the stuff that they'd seen in Abu Ghraib on Halimi. They put him in the hood and all this kind of thing. This is where it gets weird and I'm interviewing these kids. This made the Libaba, the torturers, martyrs, soldiers. This is the language that people were using. And there were soldiers in a war and there were soldiers in a war against France and by extension against Europe. And it wasn't me, it was them, these kids who actually used the language of the interfather. And they openly identified with the Palestinians who they saw as prisoners in their own land exactly like themselves that dispossessed of the Prisian Bonnier. Now this sounds very odd and it gets odder still because this was in 2007 and I spent a couple of weeks exploring Bannier walking through the streets chatting to hip hop kids footballers, football fans self-proclaimed caser who were kind of wreckers or rioters. I talked to these people in sports centres shops, bus stops and this is very hard but a lot of it was fun. There was a lot of serious laughter and benign mischief and I enjoyed talking to the kids about football and politics. Bit by bit I kind of started picking up on a secret code in the slang and in the language and the secret code was there were references to synagogues, references to Jews and references to Israelis and they were all kind of refracted through the algo through the slang of the Bonnier and this is where it was interesting, people very casually these expressions sal bif sal id sal fferzio yw pan yw tre now these two final terms yw pan yw tre are particularly poisonous because these were words that were used in 1930s and in 1940s to describe Jews being sent off to the camps. For all this it was very hard to meet anybody who actually met a Jew and we don't need to meet Jews I was told by Gregor Lee a would-be rapper a Muslim from La Chapelle we know what they're like well that's the problem nobody actually did know what they were like it seemed to me that this was a form of youth revolt that was what was happening that hating Jews like supporting Arsenal or listening to a rap band like NTM it just became a defining motif of identity in the Bonnier people started to get angry Jews started to get angry when in the wake of all of this it was then the Shirak Government which dissembled about social problems in the Bonnier and if you like this was a sort of vignette of a wider problem that right up until the end of the first decade of the 21st century everybody knew what was happening in the Bonnier but the media and political elites would not admit what was happening that this is no more than social problems and to his credit I've got to say it was only Nicolas Sarkozy who was then the ambitious Minister of the Interior whose mother was a Sephardic Jew and he was the only one who actually came out and denounced the murder of Ylan Halimi as an anti-Semitic crime but this was interesting because at the moment of Sarkozy's intervention the terms of the debate were suddenly changed and nobody answered this question but they started to ask it was the killing of Ylan an isolated act or was it a political murder in the largest sense and what I mean by a political murder is an act that expressed a collective hatred so did this act belong to individuals or did it belong to the whole community well I can't answer that question but I can start to think about history Hating Jews is one of the oldest motifs one of the most defining motifs in French history and here's part of the theory that informs that there is a theory the hatred of Jews anti-Semitism often emerges in French history when you have a class that feels under threat that feels that its identity is under threat and it's about to be annihilated and one of the classic examples of this is at the end of the 19th century with the Dreyfus Affair and you get an anti-Semite like Louis Ferdin on Selina emerges out of this generation for those who don't know when Selina was the novelist who wrote Wajob Rulani in the 1930s his books, his pamphlets against the Jews are still semi-legal in France and they were so anti-Semitic they actually shocked the Nazis when they came to Paris in the 1940s to my mind Selina is the most brilliant writer in France in the 20th century he's more important to my mind than Proust why? he captures the emotion and the emerges from that generation the pitted bourgeoisie where he feels that this class is losing itself and must express its identity in hatred he was a pessimist he was obsessed by disease and filth and he saw no hope for the poor of the Bonnier in the end Selina blamed nearly everything on the Jews this is a quote actually from one of the semi-legal books war in the name of the bourgeoisie was shitty enough he wrote but now war for the Jews half-negroid, half-asiatic mongrel pastiches of the human race who's only aim is to destroy France well, this is history but it's history which is resurfacing Selina's actually become an inspiration bizarrely enough to a generation of rappers in the Bonnier because of his use of street language because of his stylised slang but there's also something very dangerous there because Selina as the voice of a dying inauthentic working class also expresses antisemitism in the most violent language and it's clear that that has an appeal as well there's actually a track called Selina by the rapper Abdul Malik which is a very good track in which he warns of the dangers of following Selina but I think it's true that you know these extreme emotions are now starting to infect contaminate and actually dominate a whole if you like political discourse in France and that's what's taken us towards this notion of a politics of atmosphere so I don't have any concluding remarks but I will say this and I'm going to return to Pierre Bernbound and Pierre Bernbound in the book I described before he looks back to the 1930s as well and specifically he returns to the Stavisky Riots of 1934 and he sees for those of you who don't know the Stavisky Riots were a series of riots that convulsed Paris in 1934 and it was the alleged crimes of a Jewish financier called Stavisky and left and right were fighting it out in the streets and Bernbound interestingly saw in the violence of 1934 the legacy of Edward Moumont who galvanised the Pianoir in Algeria by promoting the noble races of Arabs and Berbers over what he called the parasitical Jews and Bernbound interestingly sees this at work in the discourse of the National Front the right-wing Catholic groups who opposed gay marriage and one of those dangerous things is the so-called comedian Dieu Donné and what Dieu Donné does he promotes holocaust in Isle effectively and I'm sure that you know that the Rwagu Siw of 1992 is under French law a law which forbids the denial of crimes against humanity and what Dieu Donné brings on to the stage well-known in the Gassian East and the Gatianist holocaust deniers like Robert Fourier-son Now, kids in the Bonnier don't know who Fourier-son is necessarily but what he's transmitting Dieu Donné is this it's one thing to have anti-Semitism as a weird occult conspiracy theory but it's another thing to transmitting out into a wider community and what you get when you do that is that you have this occult conspiracy theory becoming an accepted mass belief now the comparisons with the 1930s are obviously very clear the journalist Michel Dreyfus in Le Monde describes this as the mass so Dieu Donné is doing two things he's attacking the Rwagu Siw he's taking on the French government with the Rwagu Siw and at the same time he's promoting a belief system that everything that's wrong with France everything that's wrong with Europe everything that's wrong with democracy is to do with the Jews and this is I would suggest how the very disparate forms of anti-Semitism in France right now speak to each other because that's what's happening and these elements came together in the January attacks in 2015 with the attack on Charlie Hebdo and the kosher hypermarket then of course the Bataclan which in 2008 have been targeted by radical groups in the Bonneas as an Israeli funded front so if you like due hatred anti-Semitism is a way of attacking French universalism French democracy from this marginalised underclass you see France and this is a quotation as a totalitarian democracy where Jews hold a privileged and controlling position and to my mind it's like the poison of anti-Semitism which dominated French history has never actually gone away and that's why I would finally suggest this is one of the reasons that these are such dangerous days for France and of course this applies to the rest of Europe


So, so in the morning, were you up when she left? Oh yeah. I said goodbye. She went out the door and I was watching the news and I saw the accident on the news. I said, God, that car looks familiar, but I didn't know it was her. And then when I got the phone call, I realized what was going on. What did they tell you? That your wife is here. She's been in an accident. She's stable, but she's been in an accident. She's in the ER. So I went down and the doctor told me she's got a lot of problems. There's a lot of internal injuries because of the way she hit. I think we were going to be okay. They did surgery on her. Where was she at, John? Down at Bayfront. They did surgery on her, told her, told me that she was going to be all right the next evening, actually the next morning. They had to take her back into surgery because she was becoming really ill. Took her back in. He did surgery on her again. He met me coming out of the operating room as she was going back into the ICU and said she's not going to make it All of her intestines and her organs and all that stuff had something to do with the accident had stopped any of those organs from getting blood. So she basically became septic and all of her insides died basically.


We'll get started. This is a seamless multi-cloud Kubernetes, a practical guide. I am Justin Sanabarbara. I've been a contributor to Kubernetes basically since the start, and I work at Google. Hi, everyone. My name is Ciprian. I'm a software engineer at Microsoft. I'm a contributor for Kubernetes and various project link to it since a long time ago also. We're happy to have you here. Awesome. So one of the things that we're celebrating this year at KubeCon and the various KubeCons is 10 years of Kubernetes. And from the very start, Kubernetes set out to give application portability. And that means you should be able to take a working application that works on a Kubernetes cluster in Cloud A, and you should be able to take that same YAML basically and move it over and run it on Cloud B. And 10 years in, we've basically achieved that. So of course, we're still aiming to expand the set of applications that do work well in Kubernetes at all. And there are still some rough edges, but broadly it works. But there's an important detail in that. Like, what we're talking about is one application running on one cluster, and so one Cloud and one region. It was not really part of the original mandate of Kubernetes to run one application on multiple clusters or on multiple clouds. But what we are going to talk about today is how to effectively climb that pyramid of complexity so that you can get to real multi-cloud. We'll talk about why you might want to, and just as importantly, why you might not want to do this. I also have a confession. I, at least, I don't know how you feel, thought it was going to be easier to climb this mountain. I think we all in the Kubernetes project thought it would be easier. The idea was we'd start with one cluster, and we would get to multi-cluster, and everything would be joy and happiness and simplicity, and it's proven tougher. So we have recorded a few videos today to get through all this faster, but it's all live. If we have more time, we're in questions afterwards. We can sort of show you some more stuff. But as we go through this, I think bearing in mind the complexity, think about where that complexity line is for you. Like, at what point do you pull the ejection handle and say, you know what, this is just too complicated and I want to stop. For me, there's an obvious sweet spot where I think it makes a lot of sense, but everyone will have their own requirements and their own place to draw that line. Okay. Okay, so let's start at the beginning. Why would we even want to step outside of the happy place, a single cluster, that we've all spent 10 years optimizing? Well, the biggest restriction in Kubernetes is that it's really designed to run in a single region. In the early days, we were going to have just run in one zone, but if we're going the path of multi-region, we may have, well, tried to solve multi-cluster. But today, one cluster runs in one zone, one region. Many businesses need to run in multiple regions, maybe for compliance issues or because you want to tolerate regional outages or because your customers are spread around the world and latency sensitive. Another big reason is that you probably shouldn't be adding nodes indefinitely into a single cluster. The sweet spot depends on your workload, but there is a point where you're hitting problems simply because of your scale.  And along the way, you may solve some compliance issue or some DR issues. You may have to do this for one reason, but still get the wins for all the other reasons. Subtle reason that we'll keep touching on is having two cluster means you can avoid a lot of shared fate.  So yeah, I guess, okay. If you change one cluster at a time, even if it breaks, you don't have all your pods in one cluster. So ideally it would survive. Of course, it's not all easy. Most of the tooling is based around the idea of clusters. In SIG multi-cluster, we are trying to address this to be more user-centric or application-centric, but you may need updated tooling that understand the idea of aggregating multiple cube API servers. For application developers, depending on how you structure it, the traffic is now going to cross clusters. And some apps will start misbehaving if that also translates to more latency or a higher error rate. Some of the convenience when running with in a single cluster like service account identity also start breaking down. And if you start running clusters across regions or even across zones, you'll also start to see higher traffic costs, quite a lot I would say. I would say looking at this list, these problems are not the bad, but if you really need multi-region, you have to pay for the multi-region traffic. But we'll show a pattern to minimize the inter-region traffic. Traffic slowdowns and errors can happen even in a single cluster. So it's not a bad thing to find these problems. And as a community, we're building that multi-cluster where tooling like cluster inventory in SIG multi-cluster. But that was multi-cluster. Let's quickly cover off why you may want to go to multi-cloud. Often it's accidental. You combine two companies or two teams and now you have two clouds. You may say no problem, we'll just pick one cloud but sometimes you just can't consolidate because of something keeping you in one cloud whether that's hardware or software or you may want to reduce cost both today and in the future when you negotiate your contracts. And finally, the clouds are not evenly distributed. For example, availability in regions like China, I don't know, India, but multi-cloud is not free. And these problems are even harder to solve. Take all the problems of multi-cluster and add some extra just for you. In terms of network traffic, multi-cloud looks a lot like multi-region even if the two clouds are in the same region. So you lose a lot of the fast paths, you definitely lose the cheap path and you should not assume that the network is secure anymore. You should assume that failures happen a lot more often and if you're using some of the convenient features like automatic authentication to cloud services, that is likely broken also.  The big problem is that you're off the beaten path. There's not as many tools to help you with. There's not as many docs to help you and there's not one vendor that understands everything you're doing. But it's not all bad news. We can architect to minimize this. So let's start digging into how to make sense of all this. So there are a lot of challenges, but if there is an attractive payoff, if we can minimize those problems. So let's look at where we are. So as we started, we pointed out that together we have built a Kubernetes that works well for application consistency. But we've also, along the way, been building tools for consistent management of clusters. In fact, we've built lots of it. We've built Kops along with others. Cluster API, CubeSpray, there are some commercial services. So this is the first step, the tooling that understands the idea that you want to manage a cluster, that you want to manage multiple clusters, and that those multiple clusters might be in multiple regions or multiple clouds. So let's start with the cluster API. Like most of the tooling, like this tooling has sort of all followed the same pattern. There's a model. Cluster API uses CRDs. Everyone else is sort of converging on CRDs, including Kops. And that model describes both Kubernetes, sort of the common functionality across clouds, and a model that describes the infrastructure specifics. So those vary across clouds. But generally, there's a tool, in this case, Cluster CTL, that helps generate that model, like largely independent of the clouds. And so what you can see is, whether you type cluster, CTL generate cluster, infrastructure AWS or Azure, behind the scenes, there's a lot of details, but when you're working on, when you're working at the CLI level, the interface you get is consistent. And a lot of those details are abstracted away from you. They're not hidden, they're still there if and when you need them, and you probably will need them, but you don't have to sort of know everything about AWS or Azure or GCP right off the bat. And similarly, Kops is another OSS tool that Cyprian and I are two of the maintainers of. Again, look, it's very similar. There's a declarative model for infrastructure and for the Kubernetes installation. And again, you create clusters very simply using a CLI tool with very similar commands across the clouds. And sort of the details of the load balancer or whatever it is, is largely abstracted away from you. So if Kubernetes is solving for applications and application portability, and we've also started working on creating multiple clusters, what is the story for those application developers that want to deploy those applications to multiple clusters? In other words, are we done? And we are by no means done. The original effort here was the Kube Federation project or KubeFed. I think what KubeFed did really right was optimizing for that application developer experience. The idea was essentially from the application developer's perspective that multiple clusters would look and feel like one massive Kubernetes cluster that was sort of magically auto-scaling in all the regions. It was a very ambitious goal. And I think 10 years in, I don't think we're not all using KubeFed today. It has been slow going and it has had a few reboots. And in my opinion, that's because of two problems. The first is that architecturally, it's difficult to avoid introducing a new single point of failure. So KubeFed has sort of a, that control plane is now a potentially single point of failure. And that's something we'll deal with again and again. And the second is that KubeFed was very early. It was building a lot of this before CRDs existed, the core Kubernetes APIs. I'm not even sure deployment existed when KubeFed started. Those core APIs were still evolving. So that made everything harder. The efforts are still continuing here, but it certainly isn't ubiquitous. And I don't think we've reached a conclusion as a community that is necessarily the right and the perfect model. One of the things that has come along though, over the past few years, is a different approach, which is the idea of using GitOps to deploy applications. And so what we're really saying is that the new interface, GitOps is that new interface that replaces KubeCuttleApply. So you probably today already are using GitOps. We could do the show of hands. Who is using GitOps? There we go. Excellent, ubiquitous. So you probably have a GitOps deployment mechanism so that when developers push to Git, that deployment mechanism, whatever it might be, rolls it out to at least the development cluster automatically. And so the argument here is that extending that deployment tooling so that it can cover deployment to multiple clusters is both natural and will be mostly invisible to developers. So it fits the way developers are already working with the system. So it's a very natural point to introduce multi-cluster. It doesn't solve all the problems. It doesn't solve the observability problem. It doesn't solve some of the plumbing problems that we're gonna tackle next. But in many cases, if you aren't giving your application developers KubeCuttle access to prod, which you probably aren't, it's a great solution that fits with what you're doing today. Already changed? I'm unchanged. Okay, so if you have your application deployed to multiple clusters, let's talk how the application actually runs and talk to each other. The first step is to get traffic into the cluster. So when user visit the www.example.com, we want the traffic to go to one cluster. Ideally, we want an even distribution or geo-aware distribution. Okay, so we have three approaches. We have IP level. So anycast, DNS, and external load balancer CDNs like Cloudflare. Each one has its own complexities. I guess the most common ones are DNS and external load balancers. We were preparing a demo, but the video is not ready. So this is a very simple way of getting traffic into multiple clusters easily. You could use external DNS. Basically, you're declaring the same DNS name for each of the services in, for the same service in separate clusters. And you have to set a different identifier and everything is taken care of by external DNS. You get to have various ways of splitting traffic like weighted, latency-based, failover, geolocation-based. So it's pretty flexible if for almost any usual workload. That's not stateless. In this simple case, I chose weighted. You can see that when you're doing DNS lookups, you're getting IPs from both clusters. And well, one important aspect here is the TTL. Considering that you have multiple clusters, in case of one goes down, you would like your application to request very often to be able to switch to one that works. So I think this is a wonderful sweet spot. I was talking about where my personal line might be. I think you can probably guess. But in this, what we've got here is create multiple clusters. Every cluster runs all of your applications. You use DNS to ingress the traffic and basically spray it across multiple clusters. You get up to do the deployment. Apps only talk to apps within the cluster.  And so for me, this is a great place and perhaps a very natural place to either stop or start depending on how you want to think about it. But there are times or reasons when you can't stop here. So the most obvious one, which I'm sure you're all thinking about is when you have a database somewhere. You can't not trivially put a database into all your clusters and expect your East customers to just have a completely different world from your West customers. You have some singleton or stateful service and you want all your clusters to have the same view of that service. And so the cheat mode here is just not to put these into the cluster. These are going to be hard services to run in any case. And when you're talking about multi-cluster or multi-region or multi-cloud, they become very hard services to run. So this is something where it's certainly worth thinking about whether you should consume this as a service, whether that is from your cloud or another vendor. But keeping it out of the cluster often works out better from a TCO perspective. I think we see this even with a single cluster where a lot of people don't run their SQL database in their cluster. They find it easier to get it from their cloud vendor or service. There are shortcomings with that. You do have to be aware of latency. You probably have to deal with authentication in a way that was more complicated than if it was running in the cluster. You might have to distribute cloud credentials. If you can use OIDC, that's better. You may have noticed we're sort of pushing back or thinking about cheat modes here. And it's because we're trying to avoid this east-west traffic. It's a big can of worms where pods talk to pods in other clusters. If we can avoid that, it's worth considering. So stand up those parallel universes, parallel services, all the clusters are homogenous and they don't talk to each other. They're isolated. If we can consume services from outside the cluster, it helps us keep us in that happy case. And one of the cheat modes, I guess, if you feel like you still can't do that, is we can publish internal services using the DNS that Cyprian just showed for our own internal consumption, which sort of transforms internal services and what might be east-west traffic into north-south traffic, which we know how to deal with. But in general, when we're dealing with east-west, it's gonna be really easy to accidentally get a single point of failure. It's easy to mess up on security and it's gonna get that cross-cluster traffic is gonna get much more expensive. But sometimes we have to do hard things. There are plenty of use cases. I think I've given you enough caveats, so let's move on and look how it can be done. Let's have some fun, maybe a demo. One more slide before the demo. So there are three problems we have to overcome for east-west traffic, in my opinion. They are discovery, connectivity, and security. Service meshes like Istio tackle all three and give you, they solve all three at the same time. I think one of the reasons that they have this reputation of being complicated is because they are doing that. They are solving all three problems together and it's not really the Unix philosophy of composable tooling anymore. Another problem is that they're replacing all of Kubernetes networking, but the good news is that they do solve all three. They do work once you get them going. There are other efforts. Multi-cluster services in SIG Multi-cluster is tackling the discovery problem. IPv6 support basically works in most clouds today and can solve the connectivity problem and SPIFI continues to tackle the identity and the security problem. Each of those solves only one piece of the puzzle, but I think what's interesting is that together they solve exactly the three problems that we're trying to solve. So as we continue to develop these three pieces, east-west will hopefully get easier and those same solutions will also apply to single cluster, so we won't have this big disconnect when you suddenly wanna go multi-cluster where now I need a service mesh. You'll just be using them all the time. The video didn't show on my screen, that was terrifying. Okay, so here's the video. I will try to find where it is. There it is, I will get there. So, okay, we have two small clusters. The first is in US East and the second is in US West. I cutely named them East and West for East-West traffic. They are independent clusters broadly and the problem is how do we get that traffic going between East and West? So we have the Kubernetes guestbook example and you will notice that we're only running the Redis leader pod. Just pause here for a second, I think. We're running the Redis leader pod in West and so the problem is how do we get the East pods able to talk to the Redis leader when they want to? They have replicas, they both have the replica pod so for reading they will hopefully go to the replicas but they want to go to the leader for writing and that requires essentially track crossing the continent from East to West. In the West cluster where we are running the leader we do have a normal Kubernetes service and what we would like is we want that same service in the East cluster also so that we don't have to change our application so that guestbook will still talk to the, oh, sorry, guestbook will still talk to the service named Redis leader and so you can see this one, the top one is West and has Redis leader and we do also have a cluster service in East called Redis leader as well, it has the same name so it will still resolve the same and we don't have to change guestbook. What's fun is we actually have the same endpoints in them so let's look at the endpoints. For those who don't know the endpoints are the pod IPs that sit behind the services so when we look at the endpoints in West you can see them, they're IPv6 so I apologize, I will pause to give you a chance to read and I will call attention to the important thing. So if you look at guestbook for example there are three pods, those IPs are all different, they better be but if you look at the replicas there are two pods so they each have two IPs and they're different, if you look at the Redis leader there is only one pod, it is only across both clusters, it's only in West so the IP address of it is that first one, the one that ends in B4 C4 and if you look at East it has the exact same IP address so we have used Kubernetes services to solve the discovery problem, we are using IPv6 to solve the connectivity problem, one of the nice things about IPv6, if you were running in IPv4 these would have virtual IP address, they would likely have virtual IP addresses that weren't valid outside the cluster, some sort of overlay, because they're IPv6 we can give them real routable IP addresses, security comes in, don't worry but that solves the discovery and the connectivity problems and the way this is working is using the service import from SIG multi-cluster, so you can see there's a service import in that East cluster, the service import export API is only an implementation and implementations are pluggable so what we're actually doing here is we are syncing basically IP addresses or sets of IP addresses across the clusters, oh that is unfortunate, this is really gonna test my ability, let's see if we can do this, I can't remember what we said here. And so the other thing we're also doing at the same time is we have basic firewalling being driven by syncing IP addresses of the nodes so that's how we get some of the security, it's not enough but it tackles some of the problems like denial of service type attacks, how do I advance, okay, I think, and so that is East-West, if I'm the cursor, I think. Okay, over to you, you want to close this out? Okay, I'll do this, okay. So that's a pretty rapid run through but we have shown how you can run multiple clusters across multiple clouds fairly easily, now for me the natural stopping point came before we came to East-West traffic where it got a lot harder where there was a lot more sort of implementation work that had to be done but we've shown how to make East-West or one way to make East-West work, you can also use service mesh but we've shown a couple of strategies also to avoid even needing the East-West traffic and why you might want to. I think it's also just as important to think about what are the implications of this, where are we, what does that mean, how should we think about clusters? For me the big change is about thinking about clusters as commodities, clusters as cattle sometimes, so rather than updating clusters in place, let's think about a world where we are able to bring up a new cluster with that new configuration, we add it to the pool, we remove the oldest clusters when the new clusters are basically happily serving traffic. If you're on the cloud, you might as well use that supply elasticity but there are I think a ton of benefits even if you're on-prem and have to sort of really think carefully about capacity. We avoid a ton of risk and a ton of complexity, that is really the goal, that for me is why East-West is crossing that line but that's what we're trying to do. The big change I think, the other big change for me is thinking about what is a cluster, like once pods in one cluster start talking to pods in another cluster, a cluster isn't really a set of pods anymore. For me it's about thinking about a cluster as a particular version of the Kubernetes control plane, the cluster software, the location, you bring up resources, clusters where you want them and you update the versions of software in a managed and safe way using blue-green strategies. Okay, so let's summarize what we've learned. There's a great sweet spot for multi-cluster, every cluster runs everything, GitOps deploys everything, avoid East-West traffic, use ingress to bring traffic into multiple clusters and DNS is good enough. If you need to do East-West or stateful, it's possible. Service mesh is the most complete option today but it has a reputation for complexity. That's something that you cannot avoid in this space. In the Kubernetes project we're somewhat accidentally working on breaking up service mesh into more modular components. That will also apply to single clusters but those are not what we would consider seamless today. If you have to do it, please be mindful of the fact that it isn't seamless and come join the efforts to make sure that at least your use case is heard and taken into discussion. And finally, the next time you're thinking about upgrades of clusters or software on those clusters, think about whether you can mitigate a lot of the pain by embracing the seamless version of multi-cluster GitOps homogeneous clusters with ingress as the only shared point. Thank you. I think we've saved a couple of minutes for questions but I acknowledge that lunch is also now so I don't think anyone will be offended if you try to satisfy that hunger first but if you are hungry for answers, please either put your hand up and we can do a public question or we face government find us afterwards.


Hello, this is Bethany O'Rear, Regional Agent for Alabama Extension. Thank you for joining me today to learn more about planting the spring garden, a part of our series for home vegetable gardeners called Grow More, Give More. At the end of this talk, you'll see a list of several publications you might find useful at our website, aces.edu. Spring is the season most gardeners start planting in earnest. For that reason, it's important to have a plan because whatever you see, plant or fail to remove from the garden now will affect your success for the whole year. You can use a paper and pencil to plan out your garden, but I highly recommend so, a free app found at aces.edu. Whatever method you choose, think ahead for this year and keep records to grow even more successfully next year. Preparing the garden soil is critical to success. Different vegetables have different nutritional needs. The best way to know the nutrient content of your soil is to conduct a soil test. No matter what garden type you choose, container, raised bed, or in-ground plot, be sure you get enough sunlight. Most vegetables need at least six hours but prefer more. Reliable moisture is key. Plant where you know you can easily supply additional water, but be sure that the soil doesn't stay too wet. That may mean choosing the right container or improving your soil. It's best to give it a little thought now rather than watch your plants wilt. Spring vegetables like a pH of 6 to 7. Not sure what your soil pH is? The soil test that I just mentioned will give you this information and more. Spring vegetables mature before the last spring frost, at least for our eating purposes. Cool temperatures keep broccoli florets tight and cabbage heads firm, but when temperatures start rising, the plants want to flower or bolt. Spring plants need to be planted with more space than you might think. Rows should be two feet apart. In a row, no matter how small your broccoli or cabbage transplants look at planting, give them two feet because you'll be pleasantly surprised at how big they get. Plants like carrots, radishes, and turnips need three inches separation in a row. That gives them at least an inch from the other plant at maturity. Leafy greens also take up more real estate than you might think, so give them one to two feet in a row. When it comes to fertility, a general recommendation is to apply a balanced fertilizer like 131330. And then compensate for any extra needs specific to the crop or soil with side dressing four to six weeks after planting. Spacing is often the key to a spring garden success. Seeds should generally be planted as deeply as two to three times their diameter. Check the sew up for more specifics. Transplants want to be planted even with a soil line, and when you're working in the garden, be mindful of the roots right under the surface they don't like to be trampled on. One of the great things about gardening in the south is that we have so many vegetable varieties to choose from. I love to grow old fashioned heirloom types, but I also choose modern varieties as well because they're bred for disease resistance. The seed packet or the plant label will give you this information. When you plant and what you plant can vary over four months, just for what we call spring planting in Alabama. The Alabama vegetable gardener is a great resource. You can find it and many others at our website asus.edu. Have gardening questions? We have answers. Call the Master Gardener Helpline at<PHONE_NUMBER>. Thanks for watching and until next time, happy gardening.