Podcasts about Oke

Send us a textAls Bertrand Crasson zijn mening geeft, dan doet hij dat zonder omwegen. Zeker als het over de club van zijn hart RSC Anderlecht gaat. “Iedereen spreekt altijd over het DNA van Anderlecht. Maar niemand in de club die vandaag nog weet dat is,” schiet de voormalige rechtsback van paars-wit met scherp in deze aflevering van Radio Radzinski.Zes titels en een Beker van België, verspreid over twaalf seizoenen. Da's het indrukwekkende palmares van Bertrand Crasson. De voormalige rechtsback van Anderlecht speelt in de jaren 90' en begin 2000 alles op een hoopje met een kern waar supporters van paars-wit vandaag alleen maar van kunnen dromen. “Keshi, Nilis, Degryse, Zetterberg, Musonda en later natuurlijk ook Radzinski. Dat waren allemaal uitzonderlijke spelers. Die vind je niet meer terug in de huidige selectie. Nu staan er met uitzondering van Vertonghen en Hazard geen voetballers meer op het veld die al iets bereikt hebben. Het zijn jonge gasten die na een verloren wedstrijd een foto op Instagram plaatsen, duizend likes krijgen en tevreden zijn, terwijl ze gespeeld hebben als ezels,” is Crasson bikkelhard in deze aflevering van Radio Radzinski. “Niemand binnen de club weet vandaag nog wat het DNA van Anderlecht is. Ik wil niet klinken als een oude zaag die zegt dat vroeger alles beter was, maar op dat gebied is het wel zo. Wie een shirt van Anderlecht draagt, draagt het shirt van de winnaar. Da's het DNA van de club en daarvoor moet je over lijken durven gaan.”De kunst van het verdedigenCrasson spaart niets of niemand in zijn betoog en ziet verschillende problemen die ervoor zorgen dat Anderlecht op dit moment vierkant draait. “Om te beginnen is er één speeldag voor het einde van de reguliere competitie geen typeploeg. Oke, er zijn heel wat blessures, maar je moet toch eens duidelijke keuzes durven maken. Daarnaast ontbreekt het dit middenveld aan voldoende body. Stroeykens gebruikt zijn lichaam beter en beter, maar de rest weegt te licht. Letterlijk en figuurlijk.”Maar waar de ondertussen 53-jarige Brusselaar zich nog het meeste aan stoort, is het gebrek aan een solide defensie. “Neem nu N'Diaye. Da's een mooie voetballer, maar geen verdediger. Goed verdedigen is een kunst waar die gasten geen kaas van hebben gegeten. En met Jan Vertonghen zit de enige speler die wel weet hoe het moet op de bank. Hoelang gaat die joke trouwens nog blijven duren? Zelfs al is hij niet honderd procent fit, dan nog moet je hem opstellen. Want zelfs aan zeventig procent is hij nog altijd beter dan al de rest samen."Het bestuur en de match van de schandeNiet alleen de ploeg en de coach krijgen een veeg uit de pan. Ook het huidige bestuur moet het ontgelden. “Hoe kan er nu stabiliteit zijn als er elk jaar van sportief directeur wordt gewisseld? Al zou het ook goed zijn moesten er wat meer mensen met een echt Anderlecht-profiel mee de koers bepalen. Dat is het geval bij elke Europese topclub.”Eindigen doen we met een korte terugblik op de match van de schande, ofwel een vechtpartij tussen Club Brugge en Anderlecht uit 2002. “Scheidsrechter De Bleeckere had ons toen twee rode kaarten gegeven en ik ging daar helemaal niet mee akkoord. Ik heb er toen alles aan gedaan om zelf rood te krijgen door iedereen die in mijn buurt kwam een paar stampen te geven.""Maar De Bleeckere hield zijn kaarten op zak. Jammer, want het was mijn doel om zelfs met rood op het veld te blijven staan als protest. Op die manier wou ik die match stilleggen (lacht).” Muzikaal wordt deze Radio Radzinski dan weer neergelegd met Stockholmsvy van Hannes en waterbaby.

Oke, je leven is een rommeltje op het moment, maar hoe kom je daar (steeds) in terecht? In deze aflevering staat zelfreflectie centraal. We hebben een ondersteunend document gecreëerd en die kan je hier downloaden: https://www.opeigenkoers.net/product-page/zelfreflectie-guide Succes!

Django, Sam en Ruben geven hun geld in een ramp tempo uit! Maar waaraan eigenlijk? En hoeveel verdien je eigenlijk als 16 jarige? En hoeveel hebben zij en ik eigenlijk op de rekening staan? Wat zou je doen geld zelf houden of liever toch weggeven? Dat en nog veel meer in deze aflevering want we hebben het over DOEKOEEE, SAAAAAF, FLAPPPEN.... Oke ik stop al... Veel luisterplezier! Groetjes van mij en de leerlingen! Insta / TikTok - PauzePraatdePodcast

Ohne Sankt Pauli würde es Viva con Agua nicht geben. Oke Göttlich und Benjamin Adrion lassen mit Micha Fritz die Anfänge von Viva con Agua und der Geburtsstätte St. Pauli Revue passieren. Zwei Öko-Systeme die miteinander verwachsen sind. Eine Partnerschaft die Wurzeln hat. Oke spricht über den St. Pauli, was es beutetet in die Erste Liga aufzusteigen und gleichzeitig hinter den eigenen Werten zu stehen und nicht ansatzweise hinter allem was die Erste Liga vertritt. Sie sind mal wieder Vorreiter und gründen eine soziale Genossenschaft für den Fußballverein. Wie geht man mit Veränderung und Wachstum einer Organisation um? Darf aus einem vermeintlichen Chaos, aus politischen Werten, aus der Kultur des Vereins heraus - darf daraus Erfolg wachsen? Ist das Widersprüchlich oder das was vermeintlich passieren muss um den Zweck des Vereins zu verfolgen?   INFOS Gäste: Öke Göttlich auf Instagram: Instagram (@okegoettlich) Benjamin Adrion auf Instagram: Instagram (@benjamin.adrion) Gemeinsame Projekte von St. Pauli und Viva con Agua: Becherspenden seit 2009 Millerntor Gallery seit 2011 Instagram (@millerntorgallery) SPENDE - Zum Jahresende sorgen wir gemeinsam dafür, dass das Brunnenbohrgerät »John's Rig« auch 2025 nach Wasser bohrt. Spende jetzt für sauberes Trinkwasser in Äthiopien: Keep the water flowing - Viva con Agua   ALLE FÜR WASSER - WASSER FÜR ALLE‌ Produziert von Podstars by OMR.

S4E43 - FWP eersteklas vandaag: op date zijn én een pindanootje tussen je tanden hebben - what to do? Voor zulke problemen neemt Kaj maar al te graag het vliegtuig naar Nederland. Oke, én voor de bizarre London-stories van Mo dan. Bij deze ben je gewaarschuwd, luisteren op eigen risico!

Kencan Dengan Tuhan - Kamis, 7 November 2024 Bacaan: "Kasih dan kesetiaan akan bertemu, keadilan dan damai sejahtera akan bercium-ciuman." (Mazmur 85:11) Renungan: Seorang pria muda suatu kali datang dan memberitahukan niatnya untuk bercerai dari istrinya kepada seorang dokter. Pria itu berkata, "Tidak ada gunanya lagi, Dok. Saya mengasihi istri saya ketika saya menikahinya 2 tahun yang lalu, tetapi sekarang semua kasih itu sudah menguap. Saya hanya tidak ingin hidup dalam kebohongan, jadi saya harus menceraikannya." "Tetapi tidakkah kamu berpikir bahwa kamu berhutang sesuatu kepada istrimu?" tanya sang dokter. "Yah, saya pikir memang begitu. Jadi apa yang bisa saya lakukan mengenai hal ini?", kata pria tersebut. "Mari saya sarankan sesuatu kepadamu. Karena kamu merasa berhutang kepada istrimu, maka pertimbangkanlah niat untuk berceraimu selama 1 bulan. Selama masa-masa tersebut, lakukanlah suatu hal yang baik kepada istrimu setiap hari. Belikan dia buket bunga, sekotak coklat, atau gaun baru. Bawa istrimu ke tempat yang disukainya. Cucilah piring untuk istrimu atau lakukan hal-hal semacam itu." "Tetapi, dok, dia akan berpikir bahwa saya sudah gila," kata pria muda itu. "Mungkin saja, tetapi coba dulu. Oke?", kata sang dokter. Pria itu menjawab, "Baiklah, Dok!" Sebulan kemudian, pria muda itu kembali, dan sambil mengusap kerah bajunya dengan malu-malu, ia memberitahu, "Saya tidak tahu bagaimana harus mengatakannya," kata pemuda tersebut, "tetapi saya telah jatuh cinta kembali kepada istri saya." Bagaimana caranya menghidupkan kembali api cinta dalam pernikahan yang telah pudar? Tidak ada cara lain selain menerapkan kasih Kristus dalam pernikahan tersebut: kasih yang tidak mementingkan diri sendiri, kasih yang melayani, dan kasih yang mau berkorban bagi pasangan. Nilai sebuah pernikahan tidak diukur oleh jam atau harta, tetapi diukur dari banyaknya kasih yang diberikan di sepanjang pernikahan. Tuhan Yesus memberkati. Doa: Tuhan Yesus, tumbuhkanlah kembali cinta yang mula-mula terhadap pasangan hidupku, agar melalui cinta itu aku dapat menghidupkan kembali keharmonisan dalam keluargaku. Amin. (Dod).

Stāsta sociologs, zinātniskā institūta Baltic Studies Centre vadošais pētnieks, LU profesors Tālis Tisenkopfs lasa Adas Tisenkopfas esejas "Biarica" otro daļu "Gabriela Šanele un Igors Stravinskis". Latviski to tulkojusi Jolanta Treile. Gabriela jeb Koko Šanele bija ne tikai slavena modes dizainere, bet arī mecenāte. Šis būs stāsts par kultūras cilvēku saiknēm un draudzību XX gadsimta sākuma Parīzē, Venēcijā, Biaricā un citur. Reiz Parīzē kādās vakariņās 1917. gadā Gabriela Šanele iepazīstas ar Misiju Sertu (Misia Sert) – poļu izcelsmes franču pianisti un literāri muzikāla salona īpašnieci. Misija Serta bija īsta salonu lauviene. Kļuvusi bagāta otrajā laulībā, viņa ļāvās greznībai un visur valdīja. Viņa bija Ogista Renuāra iemīļota modele. Misija bija arī “Krievu baleta” Parīzē impresārija Sergeja Djagiļeva labākā draudzene. Kad Sertu pāris dodas ceļojumā uz Itāliju, Šanele brauc līdzi. Tur, Venēcijā, kādā restorānā Misija iepazīstina Gabrielu ar Djagiļevu. Djagiļeva izskats Šaneli fascinē – gudras, sajūsmas un skumju pilnas acis. Pirms iepazīšanās Gabriela bija redzējusi tikai vienu no slavenā “Krievu baleta” iestudējumiem Parīzē – “Šeherezādi”. Izrāde bija atstājusi satriecošu iespaidu. Šanele atcerējās: “Ar šīm neprātīgi skaistajām Baksta dekorācijām  Parīzē iesākās visaptveroša aizraušanās ar Austrumu stilu”. Djagiļevs prata atklāt ģēnijus. Tieši viņš pasaulei dāvināja Igoru Stravinski. Un arī Gabrielu iepazīstināja ar neparasto komponistu. Tā Šanele kļuva gan par Djagiļeva, gan Stravinska mecenāti. Slepus no Misijas viņa nosūtīja Djagiļevam čeku par 300 tūkstošiem franku Stravinska troksni sacēlušā baleta “Svētpavasaris” atjaunošanai. Stravinskis Parīzē dzīvoja spiedīgos apstākļos un rūpēs par slimo sievu Jekaterinu un četriem bērniem. Gabriela uzaicina Stravinski pārcelties uz viņas villu pie Parīzes. Viņa ir pārliecināta, ka tur – klusumā – komponistam būs labāki apstākļi darbam. Šaneles villā Stravinskis ar ģimeni nodzīvoja divus gadus. Uz Djagiļeva vaicājumu, cik ilgi viņa domā turēt Stravinski savā tuvumā, Šanele atbildēja: “Serž, es nesaprotu jūsu norūpētību. Vai jums vajag, lai Igors atgriežas Ricas viesnīcā un komponē tur? Viņš jau tur nemaz nekomponē, bet klausās troksni aiz durvīm. Lai taču viņš dzīvo manā villā pie visa gatava!” Un vēl piemetināja: “Kad līdzās ir ģeniāls cilvēks, arī man ir vieglāk radīt.” 1921. gadā Stravinskis ar ģimeni pārceļas uz Biaricu, cerot, ka maigais klimats, jūras gaiss un kalnu tuvums uzlabos sievas veselību. Turklāt, Biaricas tuvumā dzīvoja Moriss Ravēls, sens Stravinska paziņa. Bieži te varēja sastapt arī Gabrielu. Stravinskis Biaricā nodzīvoja trīs ražīgus gadus. Te viņš ķērās pie baleta “Kāziņas” instrumentācijas. Šo darbu par krievu zemnieku kāzām komponists bija iecerējis jau sen, taču finanšu trūkuma dēļ Djagiļevs aizvien atlika šī baleta viencēliena pirmizrādi. Tā notika tikai 1923. gadā Parīzē. Djagiļevs bija sajūsmā par “Kāziņu” triumfu. Biaricā Stravinskim patika staigāt pa ielām, laukumā pie rotondas klausīties pūtēju orķestri. Rotonda ir saglabājusies, tāpat kā māja, kurā viņš dzīvoja. Tomēr komponists pameta pilsētu un pārcēlās uz Nicu. Atmiņās viņš raksta: “Mani nervi nevarēja izturēt okeāna vētras, kas īpaši bargi plosās ziemā”. Djagiļevs mirst Venēcijā. Misija Serta un Gabriela Šanele piedalās bērēs. Šanele tās pilnībā apmaksā. Mūsdienās bijušajā Šaneles modes veikalā Biaricā, Klemanso laukumā, tirgo grāmatas. Blakus kasei ir stends ar pastkartēm. Tur var nopirkt Pikaso gleznas reprodukciju, kurā attēlota Biaricas pludmale ar peldētājām uz bākas fona. Biarica turpina savu dzīvi. Atpūtnieki kā ūdens okeānā –  te pieplūst, te atplūst. Vēlu vakarā, kad jau pavisam satumsis, tālu no krasta var samanīt cilvēku siluetus, līdz ceļiem bradājam ūdenī. Okeāns atkāpies.

Hoy 17 de octubre es el Día del Karaoke「カラオケの日 Karaoke no Hi」 Según la Asociación de Operadores de Karaoke de Japón, el karaoke es uno de los mejores inventos creados en Japón para la cultura del entretenimiento. Su significado es KARA「空 カラ vacío」、OKE「オーケストラ ōkesutora, abreviatura japonesa de la palabra inglesa orchestra 」 (Súper Tokio Radio) […] La entrada DÍA DE: 17/OCT – el karaoke se publicó primero en Súper Tokio Radio.

Stāsta literatūrzinātniece, filoloģijas doktore, LU Literatūras, folkloras un mākslas institūta vadošā pētniece un Rakstniecības un mūzikas muzeja mākslas eksperte Inguna Daukste-Silasproģe Latviešu kultūrā un arī rakstniecībā nereti vērojams, ka, piemēram, rakstnieks darbojies vairākās nozarēs, visbiežāk gleznojis, tomēr Jaunlaicenes pagastā dzimušais Leonīds Slaucītājs (1899–1971) ir apbrīnojami erudīta un daudzpusīga personībā, sevī apvienojot un sevi atklājot tik dažādās nozarēs. Un arī viņa dzīves ģeogrāfija ir gana iespaidīga, aptverot arī ļoti tālas, un savā ziņā par eksotiskas zemes. Bet par visu pēc kārtas. Leonīds Slaucītājs – zinātnieks, ievērojams polārpētnieks un ģeofiziķis, literāts, sabiedrisks darbinieks, kurš arī komponējis un gleznojis. Lasījis lekcijas daudzās pasaules universitātēs (Latvijā, Vācijā, Austrālijā, bijis viesprofesors Havajas universitātes “graduēto skolā” un ģeofizikas institūtā, lasījis vieslekcijas Stokholmas, Tukumanas, Lapazas, Istambulas un Austrumāfrikas universitātēs, kā arī sniedzis konsultācijas vairākām ASV, Austrālijas un Dienvidamerikas iestādēm, kā Argentīnas, Austrālijas vai ASV delegāts piedalījies starptautiskos ģeodēzijas un ģeofizikas kongresos, vairāku zinātnisku organizāciju kārtējs un goda biedrs, saņēmis atzinības rakstus un Trelevas observatorijas zelta medaļu), publicējis ievērojamu skaitu zinātnisku darbu, lekciju konspektu un grāmatu. Pēc Valkas reālskolas beigšanas viņš mācības turpināja Jūrniecības ministrijas virsnieku skolā un jau krietnu pasaules jūru un zemju iepazīšanā (bijis Klusā okeāna un Ziemeļu Ledus okeāna flotē), viņš 1920. gadā atgriezās Latvijā un divus gadus bija virsnieks Latvijas kara flotē. Pēc tam studēja Latvijas Universitātē Matemātikas un dabaszinātņu fakultātē (1920–1925), vairākkārt papildinājis zināšanas ģeofizikā – Itālijā (1927), Francija (1927) un Karnegī institūtā ASV (1936).  Strādāja par ģeogrāfijas un kosmogrāfijas skolotāju Viļa Olava komercskolā (1923–1927), vēlāk kļuva par mācībspēku Latvijas Universitātē (kopš 1929. gada). Līdzas visam iepriekšminētajam Leonīds Slaucītājs 1933. gadā beidzis Latvijas Konservatorijas profesora Jāzepa Vītola (1863–1948) kompozīcijas klasi ar brīvmākslinieka grādu, kur studējis kopā ar Pēteri Barisonu (1904–1947), Jāni Ķepīti (1908–1989) un Valdemāru Ozoliņu (1896–1973), un Jāzepa Mediņa (1877–1947) diriģentu klasi (1935). Otrā pasaules kara beigās ar ģimeni nonāca Vācijā, kur bija nodarbināts magnētiskajā observatorijā Vingstā, pie Kukshāfenas, vēlāk, nodibinoties Baltijas Universitātei (Hamburgā, Pinebergā), bija profesors šajā augstskolā. 1948. gadā Leonīds Slaucītājs ar ģimeni izceļoja uz Argentīnu, kur divdesmit gadus bija La Platas Universitātes (Universidad Nacional de La Plata) profesors un dekāns, 2 gadus studējis glezniecību – lūk, vēl viena joma, kurā darbojies. Leonīds Slaucītājs ir personība, kura vārdu zināja ne tikai Latvijā un Eiropā, bet arī pasaulē, īpaši zinātnes laukā. Viņš ieguvis trīs doktora grādus – Latvijas Universitātē (1942), Štutgartes augstskolā (1948), Sidnejas Universitātē (1964). 1957. gadā viņš dibinājis Trelevas magnētisko observatoriju Patagonijā. Tagad pāris vārdos par Leonīda Slaucītāja darbību mūzikas jomā: viņš rakstījis arī nelielas apceres par mūzikas koncertiem, plašākā publikācija par komponistu Jāzepu Vītolu. Komponējis klavieru sonātes, variācijas, impresijas un prelūdes, tāpat kora dziesmas, solo dziesmas un īsākus darbus orķestrim; rakstījis baleta mūziku. Rīgā vadījis tolaik jaundibināto Latvijas Universitātes simfonisko orķestri, kā arī Latvijas Republikas Finanšu ministrijas kori. Dzīvojot trimdā Argentīnā, Leonīds Slaucītājs diriģējis Argentīnas latviešu kori, kā viesdiriģents arī Brazīlijas latviešu kori... 1969. gadā ar autora vāka metu un zīmējumiem tekstā iznāca Leonīda Slaucītāja ceļojumu impresijas “Sešos kontinentos” – tā ir saistoša, paša pieredzē un redzētajā, vērotajā balstīta grāmata, kura lieliski sniedz zināšanas ģeogrāfijā un pasaules zemju dažādībā. 1973. gadā izdota grāmata “Kādreiz un tagad” – stāstījumi par redzēto, sastapto, dzirdēto par zemēm pāri septiņām jūrām. Leonīds Slaucītājs trīs reizes nonāca Antarktīdā – 1951., 1955./1956. un 1957. gadā, kad “Argentīna mani aicināja par ekspedīciju ģeomagnētisko grupu vadītāju.” Pētnieciskās gaitas viņu aizveda uz dažādā, zemēm un kontinentiem, viņš pabijis Āfrikā, Ugunszemē, Indonēzijā, Indijā, Papua Gvinejā, Taizemē, Peru, Honkongā, Japānā, Filipīnās Dienvidāfrikas Republikā un daudz kur citur. Tāpēc ar interesi lasāmas viņa grāmatas, kurās atbalsojas paša redzētais. Tādi, lūk, jaunlaicenieša Leonīda Slaucītāja ceļi pasaulē. Un visam tam līdzās – solo dziesmas, kordziesmas, kas izpildītas latviešu dziesmu svētkos trimdā un Austrālijas Latviešu Kultūras dienās. Arī kompozīciju ieraksti, kas glabājas Latvijas Nacionālās bibliotēkā. Un Antarktīdas ainavas, kas iemūžinātas gleznās. Pārsteidzoši daudz viena cilvēka mūžā. Bet noslēgumā – dzejnieka Jāņa Veseļa (1896–1962) veltījuma dzejolis Leonīdam Slaucītājam: Ledainais dienvidu pols, zvaigžņu apmirdzēts, snauž, Gāles — teiksmainas pilis — klintīs šļūdoņus lauž. Vientulis stāvi, pētnieks, rāmo pakalnu dēls: Magneta adata trīc, iznirst pārdabīgs tēls... Vēro, kā Zemes lode, stariem apvīta, trauc. Klusuma klajums runā, drūmi puteņi kauc. Okeāns palsiem viļņiem jūrnieku tālēs nes; Baltijas jūrā. zvaigznēs liekamies — tu un es.  ("Laiks", 1955. gada 25 jūnijs)

Hoi, welkom bij de Bijbellezen met Jan-podcast. Mijn naam is Jan Heijnen. Het is mijn passie om mensen zoals jou te helpen met het lezen, begrijpen en geloven van de Bijbel. Op BijbellezenmetJan.nl kun je boeken, cursussen en Bijbellees-challenges vinden. Oke, laten we met de aflevering beginnen. Je hebt het misschien al gemerkt aan de andere intro, maar we zijn begonnen met seizoen 4 van de Bijbellezen met Jan-podcast. Ik ga het weer iets anders doen dan voor de zomer. Ik wil graag elke week nieuwe afleveringen online zetten, maar ik heb gemerkt dat dit nog best wel een uitdaging is. Het is best bewerkelijk om een aflevering te schrijven, in te spreken, te monteren en dan online te zetten. Bovendien spreek ik al wekelijks diverse overdenkingen in voor mijn cursussen. Daarom dacht ik: wat als ik nu een cursus maak die ik gratis ter beschikking stel aan de luisteraars van mijn podcast? De keuze is gevallen op een serie overdenkingen die het evangelie toegankelijk moeten maken voor een breed publiek. In deze serie staat het goede nieuws centraal. Wat is dat goede nieuws? Hoe vertelt de Bijbel dit goede nieuws? Maar ook: is er dan soms slecht nieuws? Dit zijn allemaal vragen die uitgebreid aan bod komen in deze serie. Iedere maandag komt er een aflevering online. Maar er is nog iets. Ik heb ook gemerkt dat er nog steeds veel vraag is naar de audio-versie van mijn boek ‘De Bijbel in 1 Dag'. Hierin vat ik ieder Bijbelboek samen in ongeveer tien minuten. Als je mijn podcast al langer volgt, dan weet je misschien dat ik mijn podcast eerst ‘De Bijbel in 1 Dag'-podcast heb genoemd. Het eerste seizoen stond dus in het teken van dit boek en nog altijd zijn dit zeer populaire afleveringen. Maar ze zijn misschien wat moeilijker te vinden. Om die reden kies ik ervoor om deze afleveringen te gaan herhalen. Elke donderdag zal ik een aflevering publiceren uit de Bijbel in 1 Dag-serie. Samenvattend: wat kun je de komende tijd verwachten van de podcast? Elke maandag lezen we samen in de Bijbel. Ons thema is ‘Wat is het goede nieuws?' En elke donderdag kun je luisteren naar een samenvatting van een Bijbelboek. Ik hoop dat deze afleveringen je tot zegen mogen zijn. Mocht deze manier van samen Bijbellezen je nu bevallen, dan raad ik je echt aan om één van de challenges te volgen waarbij je bijvoorbeeld een heel Bijbelboek samen met mij leest. Kijk maar eens op bijbellezenmetjan.nl/challenges. Ik garandeer je dat je een hoop nieuwe ontdekkingen doet. Nogmaals: bedankt voor het luisteren van deze podcast. Ik wens je veel zegen!

In cryptids in the news and other oddities, KJ covers some more details of the Michigan Dogman including a review of the infamous Gable Video. Bill covers a great account, although violent from the Mt. Oke area of British Columbia. And some great listener mail from many of you so please join us! Thank you for listening!www.bigfootterrorinthewoods.comProduced by: "Bigfoot Terror in the Woods L.L.C.""

In cryptids in the news and other oddities, KJ covers some more details of the Michigan Dogman including a review of the infamous Gable Video. Bill covers a great account, although violent from the Mt. Oke area of British Columbia. And some great listener mail from many of you so please join us! Thank you for listening! www.bigfootterrorinthewoods.com Produced by: "Bigfoot Terror in the Woods L.L.C."

27. jūlijā Ventspils koncertzāle "Latvija" svinēs piekto gadskārtu ar īpašu svētku koncertu, kura moto ir Rasas Maijas Armales dzejas rindas "Kā mirdzums uz zaļa zāles stiebra" no ­Ērika Ešenvalda kordziesmas "Rasa".  Jubilejas koncertā piedalīsies ērģelniece Iveta Apkalna, Liepājas Simfoniskais orķestris, Latvijas Radio koris, pianists Reinis Zariņš, vijolniece Azade Magsodi, saksofonists Renārs Lācis, solobalss Rūta Pāvulēna, kori "Venda" un "Ventspils", diriģenti Guntis Kuzma un Sigvards Kļava. Par gaidāmo notikumu, kas izskanēs arī Latvijas Radio 3 "Klasika" tiešraidē, izvaicājam koncertzāles "Latvija"māksliniecisko vadītāju Gunti Cimiņu, kurš šajā amatā ir kopš 2023. gada pavasara. Uzzinām par svētku koncerta ideju nākšanu un īstenošanu, Ventspils sajūtu, ostas un tukšas pludmales burvību, producēšanas pieredzi koncertu un festivālu rīkošanā ar veiksmēm un apdedzināšanos šajā jomā, jauno amatu kā ceļa turpinājumu. Izskan arī pārdomas par klausītaju Ventspilī, cerību pēc publikas uzticēšanās un nebaidīšanās piedzīvot ko jaunu, pasaules elpas nepieciešamību, kā arī sadarbību ar Ventpils Mūzikas vidusskolu un kopēja procesa veidošanu ar Ventspils kolektīviem. Guntis Cimiņš: No manas iepriekšējās pieredzes producēšanā jubilejas koncerts bija diezgan netipisks, jo gada garumā vairāk ļāvos dažādām zīmēm, dažādām sarunām, dažādām negaidītām idejām. Tā tas pamazām veidojās. Apbrīnojami, kā tas viss nāca – gan skaņdarbu izvēle, gan mākslinieku iesaiste. Esam iekļāvuši arī dažādus Ventspils rakstnieku tēlojumus par Ventspili, un tas viss izauga lielā apkopojumā par to, ko mums bija svarīgi pateikt šajā laikā. Mums bija svarīgi parādīt mūsu unikālos instrumentus. Ir ērģeles, ir Dāvida Kļaviņa klavieres. Mums ir Ventspils Mūzikas vidusskola, jaunie mūziķi, mums ir ventspilnieks Vilnis Šmīdbergs ar apaļo jubileju. Visu to bija ļoti svarīgi iekļaut. Kā vienojošais no mākslinieciskā, scenāriskā viedokļa ir šie Ventspils dzejnieki, rakstnieki, kur arī ļoti interesantā procesā nonācām līdz pieciem fragmentiem. Palīdzēja viss Ventspils bibliotēku tīkls, jutām milzīgu atbalstu. Tas bija kolosāls process. Kādi dzejnieki ir iesaistīti? Mēs vēlējāmies izcelt, mūsuprāt, nozīmīgākos Ventspils rakstniekus. Būs Mārtiņš Kalndruva, Dagnija Zigmonte, Uldis Krasts, kā arī lielisks atradums programmas veidošanas procesā – Rasa Maija Armale no Liepājas, ar kuras dzeju Ēriks Ešenvalds rakstījis skaņdarbu „Rasa”, kas arī kļuva par vadmotīvu koncertam gan idejiski, gan noskaņas ziņā. Skanēs Rasas Maijas Armales dzeja, kas ļoti labi saplūst kopā ar Radio kora priekšnesumu.  Kā izdevās visus mūziķus sapulcināt vienā datumā? Šķiet, ka tas ir bijis plānots jau ļoti, ļoti laicīgi. Jā. Tas sākās ar vienu no pirmajām ideju apmaiņām ar Ēriku Ešenvaldu. Mēs runājām par pavisam citām lietām un tad kaut kā organiski aizgājām līdz viņa darbam „Okeāna balss”, kas fantastiski skanētu koncertzālē ar ērģelēm un orķestri, ar Ivetu Apkalnu pie ērģelēm. Tas bija pirmais sākumposms. Tad viss sāka veidoties, palēnām un ļoti organiski. Tas bija interesants process. Mūziķi labprāt atsaucās aicinājumam piedalīties? Ko vispār mūziķiem nozīmē Ventspils koncertzāle? Tas bija brīnišķīgi, jo faktiski visi mūziķi, ar kuriem runāju, teica, ka tas ir liels gods un pagodinājums, ka viņi tiek uzrunāti. Tur vispār nebija problēmu. Visi ir ļoti atsaucīgi, un tagad arī sagatavošanās process ir ļoti pretimnākošs – gan viss orķestra menedžments, gan Radio kora direktore, Sigvards, Ēriks. Visu laiku nāk idejas, un es tikai brīnos, kā tas ceļš iet. Gandrīz neko nedaru, idejas vienkārši nāk. Kad runāju ar „Jūras vārtu” dežuranti par Ventspils dzejniekiem, viņa uzreiz piezvanīja Herberta Dorbes memoriālā muzeja vadītājai Inesei Aidei, kura nākamajā dienā atsūtīja savus "slepenos failus" gan no Mārtiņa Kalndruvas, gan no Dagnijas Zigmontes, kas fantastiski iederējās programmā. Es gaidīju zīmes, un tās nenāca. Jau sāku uztraukties, jo bija palikušas divas nedēļas līdz koncertam. Te nu tās zīmes ir. Saruna bija pilnīgi nejauša. Es vienmēr aprunājos ar kolēģiem, man ļoti patīk. Viņi tik labi izjūt Ventspili un to sajūtu, un dod ļoti vērtīgus padomus, kas palīdz nākotnē. Vai Vilnis Šmīdbergs arī būs klāt? Jā, Vilnis būs. Viņš jau bija atbraucis pie mums uz koncertzāli, mēs parunājāmies, es paklausījos viņa stāstus par Ventspili.

Join hosts Lois Houston and Nikita Abraham, along with Hope Fisher, Oracle's Product Manager for Database Technologies, as they break down the basics of databases, explore different database management systems, and delve into database development.   Whether you're a newcomer or just need a refresher, this quick, informative episode is sure to offer you some valuable insights.   Oracle MyLearn: https://mylearn.oracle.com/ou/course/database-essentials/133032/ Oracle University Learning Community: https://education.oracle.com/ou-community LinkedIn: https://www.linkedin.com/showcase/oracle-university/ X: https://twitter.com/Oracle_Edu   Special thanks to Arijit Ghosh, David Wright, Radhika Banka, and the OU Studio Team for helping us create this episode.   --------------------------------------------------------   Episode Transcript:   00:00 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started! 00:26 Nikita: Hello and welcome to the Oracle University Podcast. I'm Nikita Abraham, Principal Technical Editor with Oracle University, and with me is Lois Houston, Director of Innovation Programs. Lois: Hi there! For the last seven weeks, we've been exploring the world of OCI Container Engine for Kubernetes with our senior instructor Mahendra Mehra. We covered key aspects of OKE to help you create, manage, and optimize Kubernetes clusters in Oracle Cloud Infrastructure. So, be sure you check out those episodes if you're interested in Kubernetes. 01:00 Nikita: Today, we're doing something a little different. We've had a lot of episodes on different aspects of Oracle Database, but what if you're just getting started in this world? We wanted you to have something that you could listen to as well. And so we have Hope Fisher with us today. Hope is a Product Manager for Database Technologies at Oracle, and we're going to ask her to take us through the basics of database, the different database management systems, and database development.  Lois: Hi Hope! Thanks for joining us for this episode. Before we dive straight into terminologies and concepts, I want to take a step back and really get down to the basics. We sometimes use the terms data and information interchangeably, but they're not the same, right? 01:43 Hope: Data is raw material or a set of facts and observations. Information is the meaning derived from the facts. The difference between data and information can be explained by using an example, such as test scores. In one class, if every student receives a numbered score and the scores can be calculated to determine a class average, the class average can be calculated to determine the school average. So in this scenario, each student's test score is one piece of data. And information is the class's average score or the school's average score. There is no value in data until you actually do something with it. 02:24 Nikita: Right, so then how do we make all this data useful? Do we create a database system?  Hope: A database system provides a simple function—treat data as a collection of information, organize it, and make the data usable by providing easy access to it and giving you a place where that data can be stored. Every organization needs to collect and maintain data to meet its requirements. Most organizations today use a database to automate their information systems. An information system can be defined as a formal system for storing and processing data. A database is an organized collection of data put together as a unit. The rationale of a database is to collect, store, and retrieve related data for use by database applications. A database application is a software program that interacts with the database to access and manipulate data. A database is usually managed by a Database Administrator, also known as a DBA. 03:25 Nikita: Hope, give us some examples of database systems. Hope: Popular examples of database systems include Oracle Database, MySQL, which is also owned by Oracle, Microsoft SQL server, Postgres, and others. There are relational database management systems. The acronym is DBMS. Some of the strengths of a DBMS include flexibility and scalability. Given the huge amounts of information that modern businesses need to handle, these are important factors to consider when surveying different types of databases. 03:59 Lois: This may seem a little bit silly, but why not just use spreadsheets, Hope? Why use databases? Hope: The easy answer is that spreadsheets are designed for specific problems, relatively small amounts of data and individual users. Databases are designed for lots of data, shared information use, and complex data analysis. Spreadsheets are typically used for specific problems or small amounts of data. Individual users generally use spreadsheets. In a database, cells contain records that come from external tables. Databases are designed for lots of data. They are intended to be shared and used for more complex data analysis. They need to be scalable, secure, and available to many users. This differentiation means that spreadsheets are static documents, while databases can be relational. 04:51 Nikita: Hope, what are some common database applications?  Hope: Database applications are used in far and wide use cases that most commonly can be grouped into three areas. Applications that run companies called enterprise applications. Enterprise applications are designed to integrate computer systems that run all phases of an enterprise's operations to facilitate cooperation and coordination of work across the enterprise. The intent is to integrate core business processes, like sales, accounting, finance, human resources, inventory, and manufacturing. Applications that do something very specific, like healthcare applications-- specialized software is software that's written for a specific task rather than for a broad application area.  And then there are also applications that are used to examine data and turn it into information, like a data warehouse, analytics, and data lake. 05:54 Lois: We've spoken about data lakes before. But since this is an episode about the basics of database, can you briefly tell us what a data lake is? Hope: A data lake is a place to store your structured and unstructured data as well as a method for organizing large volumes of highly diverse data from diverse sources. Data lakes are becoming increasingly important as people, especially in businesses and technology, want to perform broad data exploration and discovery. Bringing data together into a single place or most of it into a single place makes that simpler. 06:29 Nikita: Thanks for that, Hope. So, what kind of organizations use databases? And, who within these organizations uses databases the most? Hope: Almost every enterprise uses databases. Enterprises use databases for a variety of reasons and in a variety of ways. Data and databases are part of almost any process of the enterprise. Data is being collected to help solve business needs and drive value. Many people in an organization work with databases. These include the application developers who create applications that support and drive the business. The database administrator or DBA maintains and updates the database. And the end user uses the data as needed. 07:19 Do you want to stay ahead of the curve in the ever-evolving AI  landscape? Look no further than our brand-new OCI Generative AI Professional course and certification. For a limited time only, we're offering both the course and certification for free. So, don't miss out on this exclusive opportunity to get certified on Generative AI at no cost. Act fast because this offer is valid only until July 31, 2024. Visit https://education.oracle.com/genai to get started. That's https://education.oracle.com/genai. 07:57 Nikita: Welcome back. Now that we've discussed foundational database concepts, I want to move on to database management systems. Take us through what a database management system is, Hope. Hope: A Database Management System, DBMS, has the following elements. The kernel code manages memory and storage for the DBMS. The repository of metadata is called a data dictionary. The query language enables applications to access the data. Oracle database functions include data definitions, storage, structure, and security. Additional functionality also provides for user access control, backup and recovery, integrity, and communications. There are many different database types and management systems. The most common is the relational database management system. 08:51 Nikita: And how do relational databases store data?  Hope: Essentially and very simplistically, there are key elements of the relational database. Database table containing rows and columns; the data in the table, which is stored a row at a time; and the columns which contain attributes or related information. And then the different tables in a database relate to one another and share a column. 09:17 Lois: Customers usually have a mix of applications and data structures, and ideally, they should be able to implement a data management strategy that effectively uses all of their data in applications, right? How does Oracle approach this?  Hope: Oracle's approach to this enterprise data management strategy and architecture is converged database to all different data types and workloads. The converged database is a database that has native support for all modern data types and, of course, traditional relational data.  By providing support for all of these data types, a converged database can run all sorts of workloads, from transaction processing to analytics and machine learning to blockchain to support the applications and systems. Oracle provides a single database engine that supports all data models, process types, and development environments. It also addresses many kinds of workloads against the same data sets. And there's no need to use dozens of specialized databases. Deploying several single-purpose databases would increase costs, complexity, and risk. 10:25 Nikita: In the final part of our conversation today, I want to bring up database development. Hope, how are databases developed?  Hope: Data modeling is the first part of the database development process. Conceptual data modeling is the examination of a business and business data to determine the structure of business information and the rules that govern it. This structure forms the basis for database design. A conceptual model is relatively stable over long periods of time. Physical data modeling, or database building, is concerned with implementation in each technical software and hardware environment. The physical implementation is highly dependent on the current state of technology and is subject to change as available technologies rapidly change. Conceptual model captures the functional and informational needs of a business and is used to identify important entities and their relationships.  A logical model includes the entities and relationships. This is also called an entity relationship model and provides the details of the relationships.  11:34 Lois: I think that's a good place to wrap up our episode. To know more about the Oracle Database architecture, offerings, and so on, visit mylearn.oracle.com. Thanks for joining us today, Hope.  Nikita: Join us next week for another episode of the Oracle University Podcast. Until then, this is Nikita Abraham… Lois: And Lois Houston, signing off! 11:55 That's all for this episode of the Oracle University Podcast. If you enjoyed listening, please click Subscribe to get all the latest episodes. We'd also love it if you would take a moment to rate and review us on your podcast app. See you again on the next episode of the Oracle University Podcast.

Wantimpres Jadi DPA: Pembagian "Kue" Jabatan Oleh. Miladiah al-Qibthiyah(Tim Redaksi NarasiPost.Com) Voice over talent: Yeni M NarasiPost.Com-Hai, Ganks. Kalau bicara soal politik rasanya bukan ranah remaja, ya. Remaja biasanya hanya membahas yang mudah-mudah atau ringan-ringan saja. Apalagi kalo sudah bahas dunia politik dalam negeri, pasti bikin bosan. Menonton beritanya saja sudah malas duluan, apalagi membaca beritanya. Akan tetapi, Ganks, mengetahui seputar politik dalam negeri sebenarnya ada manfaatnya juga. Kita bisa tahu bagaimana negara dalam mengurus urusan masyarakatnya, berpartisipasi dalam mengoreksi kebijakan yang sekiranya tidak sesuai dengan apa yang dibutuhkan masyarakat. Jangan pernah antipolitik, ya, Ganks, karena ini berkaitan dengan kemaslahatan masyarakat. Seperti berita tentang Wantimpres katanya bakal kembali menjadi DPA jelang pelantikan Prabowo. Mungkin kamu bertanya Wantimpres dan DPA itu apa sih? Oke deh, aku spill dulu tentang wantimpres dan DPA, ya, serta urgensinya dalam pemerintahan negara Indonesia. Naskah selengkapnya: ⁠https://narasipost.com/pilihan/07/2024/wantimpres-jadi-dpa-pembagian-kue-jabatan/ Terimakasih buat kalian yang sudah mendengarkan podcast ini, Follow us on: instagram: http://instagram.com/narasipost Facebook: https://www.facebook.com/narasi.post.9 Fanpage: Https://www.facebook.com/pg/narasipostmedia/posts/ Twitter: Http://twitter.com/narasipost

// GUEST // Website: https://okefarm.com/Instagram: https://www.instagram.com/thefarmatokefenokee/// SPONSORS // In Wolf's Clothing: https://wolfnyc.com/ The Farm at Okefenokee: https://okefarm.com/ Heart and Soil Supplements (use discount code BREEDLOVE): https://heartandsoil.co/Swan Bitcoin: https://www.swanbitcoin.com/breedlove22/// EVENTS I WILL BE ATTENDING // Bitcoin 2024: the World's Largest Bitcoin Conference (use discount code BREEDLOVE): https://b.tc/conferencePacific Bitcoin 2024 (use discount code BREEDLOVE): https://www.pacificbitcoin.com/// PRODUCTS I ENDORSE // Protect your mobile phone from SIM swap attacks: https://www.efani.com/breedlove Noble Protein (discount code BREEDLOVE for 15% off): https://nobleorigins.com/ The Bitcoin Advisor: https://content.thebitcoinadviser.com/breedlove Lineage Provisions (use discount code BREEDLOVE): https://lineageprovisions.com/?ref=breedlove_22  // SUBSCRIBE TO THE CLIPS CHANNEL // https://www.youtube.com/@robertbreedloveclips2996/videos // OUTLINE // 0:00 - WiM Intro 2:18 - Helping Lightning Startups with In Wolf's Clothing 3:10 - Introducing the Farm at Oke 13:28 - What is the Farm at Oke? 15:34 - Living Quarters 21:18 - Regenerative Agriculture 31:38 - The Farm at Okefenokee 33:04 - Heart and Soil Supplements 34:05 - Hunting on the Farm 46:14 - Activities on the Farm 51:38 - The Healthiest Community on Earth 01:08:22 - Commercial Kitchen and Event Space 01:10:43 - Swan Bitcoin: Set up Instant and Recurring Bitcoin Buys 01:11:40 - Bitcoin 2024: The Largest Bitcoin and Fintech Conference in the World 01:12:46 - What Comes With Being A Farm Owner? 01:16:42 - Detoxing From Modern Society 01:25:47 - Upcoming Retreat at the Farm 01:32:06 - Who Are Buying Cabins on the Farm? 01:35:12 - Becoming a Member at the Farm and Cabin Options 01:38:48 - Recent Changes at the Farm// PODCAST // Podcast Website: https://whatismoneypodcast.com/Apple Podcast: https://podcasts.apple.com/us/podcast/the-what-is-money-show/id1541404400Spotify: https://open.spotify.com/show/25LPvm8EewBGyfQQ1abIsE?RSS Feed: https://feeds.simplecast.com/MLdpYXYI// SUPPORT THIS CHANNEL // Bitcoin: 3D1gfxKZKMtfWaD1bkwiR6JsDzu6e9bZQ7 Sats via Strike: https://strike.me/breedlove22 Sats via Tippin.me: https://tippin.me/@Breedlove22Dollars via Paypal: https://www.paypal.com/paypalme/RBreedloveDollars via Venmo: https://account.venmo.com/u/Robert-Breedlove-2The "What is Money?" Show Patreon Page: https://www.patreon.com/user?u=32843101// WRITTEN WORK // Medium: https://breedlove22.medium.com/Substack: https://breedlove22.substack.com/ // SOCIAL // Breedlove Twitter: https://twitter.com/Breedlove22WiM? Twitter: https://twitter.com/WhatisMoneyShowLinkedin: https://www.linkedin.com/in/breedlove22/Instagram: https://www.instagram.com/breedlove_22/TikTok: https://www.tiktok.com/@breedlove22All My Current Work: https://linktr.ee/robertbreedlove

Par piemiņu no ceļojuma mājās pārvests gliemežvāks, skaists savvaļas zieds vai koraļļu kaklarota lai nepadara jūs par noziedznieku. Raidījumā Kā labāk dzīvot skaidrojam, kā nekļūt par kontrabandistu. Ko labāk neizvēlēties kā suvenīru tālā zemē, atgādina rāpuļu eksperts Andris Čeirāns, Rīgas Nacionālā Zooloģiskā dārza pārstāvis Māris Lielkalns un Valsts ieņēmumu dienesta Muitas pārvaldes Lidostas muitas kontroles punkta muitas virsuzraudze Linna Mukāne. Lai ierobežotu cilvēku vēlmi pārvest mājās kādus eksotiskus dzīvniekus vai augus, izveidota Vašingtonas konvencijas jeb  CITES, kas pieņemta jau 1975. gadā. Latvija tai ir pievienojusies 1997. gadā. "Kad aizbrauciet uz ārzemēm, ieejot vietējā tirdziņā vai vienalga kur, skatoties uz dažādiem interesantiem objektiem, kas varētu būt nākuši no dabas, vislabākais būtu turēt rokas kabatās un galvu vēsumā. Tāpēc ka CITES sarakstos ir iekļautas ap 35000 augu un dzīvnieku sugu. Ja kāds no šiem dzīvniekiem vai augiem atrodas šajos sarakstos, tā jau ir cita līmeņa aizsardzības pakāpe. Lai nevestu pāri robežām un netirgotu šos priekšmetus, ir ierobežojumi," norāda Māris Lielkalns. Jābūt uzmanīgam, vēloties iegādāties krokodilādas, čūskādas somiņas, dažādas rotaslietas, kas ir no bruņurupuču bruņām taisītas, dažādas kažokādas. Arī korāļi, kas salasīti jūras krastā, arī dažādi gliemeži, kas arī guļ jūras krastā, dažādas spalvas, pulverīši. Pat krēmos var būt iekļautas vielas, ko nedrīkst pārvadāt. Kāpēc cilvēki izvēlas šādus eksotiskus suvenīrus – daudzos gadījumos tās ir mirkļa emocijas – ļoti gribas, foršs, jauks un vēl lēti. Arī Latvijas un Eiropas dzīvnieki ir iekļauti CITES sarakstos. Rīgas Zoodārzā ir ap 125 sugu, kas iekļautas CITES sarakstos. Arī šos dzīvniekus transportējot ir vajadzīgas ievešanas un izvešanas atļaujas. "Būtu ļoti skaisti, ka pasažieri nāktu pie mums un stāstītu, ka ir iegādājušies čūsku pudelē vai čūskas ādas jostu, bet parasti tā nenotiek, un mums ir jāveic kontroles pasākumi," norāda Linna Mukāne. "Protams, vienmēr aicinām pasažierus, ja viņiem ir neskaidrības un jautājumi, vai tomēr viņš drīkst vai nedrīkst šādu preci ievest, doties pa sarkano koridoru lidostā, meklēt muitnieki un teikt, ka ir šāda prece, ko vēlas atmuitot. Tā ir ideālā pasaule, uz ko mēs tiektos un par ko mēs ļoti priecātos. Diemžēl tā nenotiek, lielākoties pasažieri dodas uz zaļo koridoru, kas nozīmē, ka viņam nav nekas deklarējams." Visbiežāk lietas, kas iekļautas CITES sarakstos, tiek ievestas no Āzijas valstīm, Okeānijas, tāpat bieži tas ir neapzināti, ka cilvēks, pastaigājoties okeāna krastā, pacēlis kādu gliemežvāku vai koralli, vai nopircis tirdziņā kādu suvenīru, nedomājot, ka tam nepieciešama īpaša atļauja, lai to pārvadātu. Šogad vēl nav bijis neviens gadījums, kad kaut kas no CITES sarakstā iekļautā būtu konstatēts lidostā. Linna Mukāne ir gandarīta, ka cilvēki kļūst arvien apzinīgāki. Viens no lidostas muitas darbinieku pieredzē neparastākiem priekšmetiem, ko cilvēks mēģinājis ievest, ir lāčāda ar visu lāča galvu. "Ir bijis, kad persona kā tādu mazo mīļdzīvnieku uz rokas nes izbāztu mazo krokodillīti, aligatoriņu. Tādi ir tie spilgtākie, kas mums paliek atmiņā. Un tādi koraļļi jau kā ikdiena," bilst Linna Mukāne.      

In the season's final episode, hosts Lois Houston and Nikita Abraham interview senior OCI instructor Mahendra Mehra about the security practices that are vital for OKE clusters on OCI.   Mahendra shares his expert insights on the importance of Kubernetes security, especially in today's digital landscape where the integrity of data and applications is paramount.   OCI Container Engine for Kubernetes Specialist: https://mylearn.oracle.com/ou/course/oci-container-engine-for-kubernetes-specialist/134971/210836   Oracle University Learning Community: https://education.oracle.com/ou-community   LinkedIn: https://www.linkedin.com/showcase/oracle-university/   X (formerly Twitter): https://twitter.com/Oracle_Edu   Special thanks to Arijit Ghosh, David Wright, Radhika Banka, and the OU Studio Team for helping us create this episode.   ---------------------------------------------------------   Episode Transcript:   00:00 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started! 00:26 Nikita: Welcome to the Oracle University Podcast! I'm Nikita Abraham, Principal Technical Editor with Oracle University, and with me is Lois Houston, Director of Innovation Programs. Lois: Hi there! In our last episode, we spoke about self-managed nodes and how you can manage Kubernetes deployments. Nikita: Today is the final episode of this series on OCI Container Engine for Kubernetes. We're going to look at the security side of things and discuss how you can implement vital security practices for your OKE clusters on OCI, and safeguard your infrastructure and data.  00:59 Lois: That's right, Niki! We can't overstate the importance of Kubernetes security, especially in today's digital landscape, where the integrity of your data and applications is paramount. With us today is senior OCI instructor, Mahendra Mehra, who will take us through Kubernetes security and compliance practices. Hi Mahendra! It's great to have you here. I want to jump right in and ask you, how can users add a service account authentication token to a kubeconfig file? Mahendra: When you set up the kubeconfig file for a cluster, by default, it contains an Oracle Cloud Infrastructure CLI command to generate a short-lived, cluster-scoped, user-specific authentication token. The authentication token generated by the CLI command is appropriate to authenticate individual users accessing the cluster using kubectl and the Kubernetes Dashboard. However, the generated authentication token is not appropriate to authenticate processes and tools accessing the cluster, such as continuous integration and continuous delivery tools. To ensure access to the cluster, such tools require long-lived non-user-specific authentication tokens. One solution is to use a Kubernetes service account. Having created a service account, you bind it to a cluster role binding that has cluster administration permissions. You can create an authentication token for this service account, which is stored as a Kubernetes secret. You can then add the service account as a user definition in the kubeconfig file itself. Other tools can then use this service account authentication token when accessing the cluster. 02:47 Nikita: So, as I understand it, adding a service account authentication token to a kubeconfig file enhances security and enables automated tools to interact seamlessly with your Kubernetes cluster. So, let's talk about the permissions users need to access clusters they have created using Container Engine for Kubernetes. Mahendra: For most operations on Container Engine for Kubernetes clusters, IAM leverages the concept of groups. A user's permissions are determined by the IAM groups they belong to, including dynamic groups. The access rights for these groups are defined by policies. IAM provides granular control over various cluster operations, such as the ability to create or delete clusters, add, remove, or modify node pool, and dictate the Kubernetes object create, delete, view operations a user can perform. All these controls are specified at the group and policy levels. In addition to IAM, the Kubernetes role-based access control authorizer can enforce additional fine-grained access control for users on specific clusters via Kubernetes RBAC roles and ClusterRoles.  04:03 Nikita: What are Kubernetes RBAC roles and ClusterRoles, Mahendra? Mahendra: Roles here defines permissions for resources within a specific namespace and ClusterRole is a global object that will provide access to global objects as well as non-resource URLs, such as API version and health endpoints on the API server. Kubernetes RBAC also includes RoleBindings and ClusterRoleBindings. RoleBinding grants permission to subjects, which can be a user, service, or group interacting with the Kubernetes API. It specified an allowed operation for a given subject in the cluster. RoleBinding is always created in a specific namespace. When associated with a role, it provides users permission specified within that role related to the objects within that namespace. When associated with a ClusterRole, it provides access to namespaced objects only defined within that cluster rule and related to the roles namespace. ClusterRoleBinding, on the other hand, is a global object. It associates cluster roles with users, groups, and service accounts. But it cannot be associated with a namespaced role. ClusterRoleBinding is used to provide access to global objects, non-namespaced objects, or to namespaced objects in all namespaces. 05:36 Lois: Mahendra, what's IAM's role in this? How do IAM and Kubernetes RBAC work together? Mahendra: IAM provides broader permissions, while Kubernetes RBAC offers fine-grained control. Users authorized either by IAM or Kubernetes RBAC can perform Kubernetes operations. When a user attempts to perform any operation on a cluster, except for create role and create cluster role operations, IAM first determines whether a group or dynamic group to which the user belongs has the appropriate and sufficient permissions. If so, the operation succeeds. If the attempted operation also requires additional permissions granted via a Kubernetes RBAC role or cluster role, the Kubernetes RBAC authorizer then determines whether the user or group has been granted the appropriate Kubernetes role or Kubernetes ClusterRoles. 06:41 Lois: OK. What kind of permissions do users need to define custom Kubernetes RBAC rules and ClusterRoles?  Mahendra: It's common to define custom Kubernetes RBAC rules and ClusterRoles for precise control. To create these, a user must have existing roles or ClusterRoles with equal or higher privileges. By default, users don't have any RBAC roles assigned. But there are default roles like cluster admin or super user privileges. 07:12 Nikita: I want to ask you about securing and handling sensitive information within Kubernetes clusters, and ensuring a robust security posture. What can you tell us about this? Mahendra: When creating Kubernetes clusters using OCI Container Engine for Kubernetes, there are two fundamental approaches to store application secrets. We can opt for storing and managing secrets in an external secrets store accessed seamlessly through the Kubernetes Secrets Store CSI driver. Alternatively, we have the option of storing Kubernetes secret objects directly in etcd.  07:53 Lois: OK, let's tackle them one by one. What can you tell us about the first method, storing secrets in an external secret store? Mahendra: This integration allows Kubernetes clusters to mount multiple secrets, keys, and certificates into pods as volumes. The Kubernetes Secrets Store CSI driver facilitates seamless integration between our Kubernetes clusters and external secret stores. With the Secrets Store CSI driver, our Kubernetes clusters can mount and manage multiple secrets, keys, and certificates from external sources. These are accessible as volumes, making it easy to incorporate them into our application containers. OCI Vault is a notable external secrets store. And Oracle provides the Oracle Secrets Store CSI driver provider to enable Kubernetes clusters to seamlessly access secrets stored in Vault. 08:54 Nikita: And what about the second method? How can we store secrets as Kubernetes secret objects in etcd? Mahendra: In this approach, we store and manage our application secrets using Kubernetes secret objects. These objects are directly managed within etcd, the distributed key value store used for Kubernetes cluster coordination and state management. In OKE, etcd reads and writes data to and from block storage volumes in OCI block volume service. By default, OCI ensures security of our secrets and etcd data by encrypting it at rest. Oracle handles this encryption automatically, providing a secure environment for our secrets. Oracle takes responsibility for managing the master encryption key for data at rest, including etcd and Kubernetes secrets. This ensures the integrity and security of our stored secrets. If needed, there are options for users to manage the master encryption key themselves. 10:06 Lois: OK. We understand that managing secrets is a critical aspect of maintaining a secure Kubernetes environment, and one that users should not take lightly. Can we talk about OKE Container Image Security? What essential characteristics should container images possess to fortify the security posture of a user's applications? Mahendra: In the dynamic landscape of containerized applications, ensuring the security of containerized images is paramount.  It is not uncommon for the operating system packages included in images to have vulnerabilities. Managing these vulnerabilities enables you to strengthen the security posture of your system and respond quickly when new vulnerabilities are discovered. You can set up Oracle Cloud Infrastructure Registry, also known as Container Registry, to scan images in a repository for security vulnerabilities published in the publicly available Common Vulnerabilities and Exposures Database. 11:10 Lois: And how is this done? Is it automatic? Mahendra: To perform image scanning, Container Registry makes use of the Oracle Cloud Infrastructure Vulnerability Scanning Service and Vulnerability Scanning REST API. When new vulnerabilities are added to the CVE database, the container registry initiates automatic rescanning of images in repositories that have scanning enabled. 11:41 Do you want to stay ahead of the curve in the ever-evolving AI landscape? Look no further than our brand-new OCI Generative AI Professional course and certification. For a limited time only, we're offering both the course and certification for free! So, don't miss out on this exclusive opportunity to get certified on Generative AI at no cost. Act fast because this offer is valid only until July 31, 2024. Visit https://education.oracle.com/genai to get started. That's https://education.oracle.com/genai. 12:20 Nikita: Welcome back! Mahendra, what are the benefits of image scanning? Mahendra: You can gain valuable insights into each image scan conducted over the past 13 months. This includes an overview of the number of vulnerabilities detected and an overall risk assessment for each scan. Additionally, you can delve into comprehensive details of each scan featuring descriptions of individual vulnerabilities, their associated risk levels, and direct links to the CVE database for more comprehensive information. This historical and detailed data empowers you to monitor, compare, and enhance image security over time. You can also disable image scanning on a particular repository by removing the image scanner.  13:11 Nikita: Another characteristic that container images should have is unaltered integrity, right?  Mahendra: For compliance and security reasons, system administrators often want to deploy software into a production system. Only when they are satisfied that the software has not been modified since it was published compromising its integrity. Ensuring the unaltered integrity of software is paramount for compliance and security in production environment. 13:41 Lois: Mahendra, what are the mechanisms that guarantee this integrity within the context of Oracle Cloud Infrastructure? Mahendra: Image signatures play a pivotal role in not only verifying the source of an image but also ensuring its integrity. Oracle's Container Registry facilitates this process by allowing users or systems to push images and sign them using a master encryption key sourced from the OCI Vault.  It's worth noting that an image can have multiple signatures, each associated with a distinct master encryption key. These signatures are uniquely tied to an image OCID, providing granularity to the verification process. Furthermore, the process of image signing mandates the use of an RSA asymmetric key from the OCI Vault, ensuring a robust and secure validation of the image's unaltered integrity. 14:45 Nikita: In the context of container images, how can users ensure the use of trusted sources within OCI? Mahendra: System administrators need the assurance that the software being deployed in a production system originates from a source they trust. Signed images play a pivotal role, providing a means to verify both the source and the integrity of the image. To further strengthen this, administrators can create image verification policies for clusters, specifying which master encryption keys must have been used to sign images. This enhances security by configuring container engine for Kubernetes clusters to allow the deployment of images signed with specific encryption keys from Oracle Cloud Infrastructure Registry. Users or systems retrieving signed images from OCIR can trust the source and be confident in the image's integrity. 15:46 Lois: Why is it imperative for users to use signed images from Oracle Cloud Infrastructure Registry when deploying applications to a Container Engine for Kubernetes cluster?  Mahendra: This practice is crucial for ensuring the integrity and authenticity of the deployed images.  To achieve this enforcement. It's important to note that an image in OCIR can have multiple signatures, each linked to a different master encryption key. This multikey association adds layers of security to the verification process. A cluster's image verification policy comes into play, allowing administrators to specify up to five master encryption keys. This policy serves as a guideline for the cluster, dictating which keys are deemed valid for image signatures.  If a cluster's image verification policy doesn't explicitly specify encryption keys, any signed image can be pulled regardless of the key used. Any unsigned image can also be pulled potentially compromising the security measures. 16:56 Lois: Mahendra, can you break down the essential permissions required to bolster security measures within a user's OKE clusters? Mahendra: To enable clusters to include master encryption key in image verification policies, you must give clusters permission to use keys from OCI Vault. For example, to grant this permission to a particular cluster in the tenancy, we must use the policy—allow any user to use keys in tenancy where request.user.id is set to the cluster's OCID. Additionally, for clusters to seamlessly pull signed images from Oracle Cloud Infrastructure Registry, it's vital to provide permissions for accessing repositories in OCIR. 17:43 Lois: I know this may sound like a lot, but OKE container image security is vital for safeguarding your containerized applications. Thank you so much, Mahendra, for being with us through the season and taking us through all of these important concepts. Nikita: To learn more about the topics covered today, visit mylearn.oracle.com and search for the OCI Container Engine for Kubernetes Specialist course. Join us next week for another episode of the Oracle University Podcast. Until then, this is Nikita Abraham… Lois Houston: And Lois Houston, signing off! 18:16 That's all for this episode of the Oracle University Podcast. If you enjoyed listening, please click Subscribe to get all the latest episodes. We'd also love it if you would take a moment to rate and review us on your podcast app. See you again on the next episode of the Oracle University Podcast.

In this episode, hosts Lois Houston and Nikita Abraham speak with senior OCI instructor Mahendra Mehra about the capabilities of self-managed nodes in Kubernetes, including how they offer complete control over worker nodes in your OCI Container Engine for Kubernetes environment.   They also explore the various options that are available to effectively manage your Kubernetes deployments.   OCI Container Engine for Kubernetes Specialist: https://mylearn.oracle.com/ou/course/oci-container-engine-for-kubernetes-specialist/134971/210836   Oracle University Learning Community: https://education.oracle.com/ou-community   LinkedIn: https://www.linkedin.com/showcase/oracle-university/   X (formerly Twitter): https://twitter.com/Oracle_Edu   Special thanks to Arijit Ghosh, David Wright, Radhika Banka, and the OU Studio Team for helping us create this episode.   --------------------------------------------------------   Episode Transcript:   00:00 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started! 00:26 Nikita: Hello and welcome to the Oracle University Podcast! I'm Nikita Abraham, Principal Technical Editor with Oracle University, and with me is Lois Houston, Director of Innovation Programs. Lois: Hi everyone! Last week, we discussed how OKE virtual nodes can offer you a complete serverless Kubernetes experience. Nikita: Yeah, and in today's episode, we'll focus on self-managed nodes, where you get complete control over the worker nodes within your OKE environment. We'll also talk about how you can manage your Kubernetes deployments. 00:57 Lois: To tell us more about this, we have Mahendra Mehra, a senior OCI instructor with Oracle University. Hi Mahendra! Welcome back! Let's get started with self-managed nodes. Can you tell us what they are? Mahendra: In Container Engine for Kubernetes, a self-managed node is essentially a worker node that you personally create and host on a compute instance or instance pool within the compute service. Unlike managed nodes or virtual nodes, self-managed nodes are not grouped into node pools by default. They are often referred to as Bring Your Own Nodes, also abbreviated as BYON. If you wish to streamline administration and manage multiple self-managed nodes collectively, you can utilize the compute service to create a compute instance pool for hosting these nodes. This allows for greater flexibility and customization in your Kubernetes environment. 01:58 Nikita: Mahendra, what are some practical usage scenarios for OKE self-managed nodes? Mahendra: These nodes offer a range of advantages for specific use cases. Firstly, for specialized workloads, leveraging the compute service allows you to configure compute instances with shapes and image combination that may not be available for managed nodes or virtual nodes. This includes options like GPU shapes for hardware accelerated workloads or high frequency processor cores for demanding high-performance computing tasks. Secondly, if you require complete control over your compute instance configuration, self-managed nodes are the ideal choice. This gives you the flexibility to tailor each node to your specific requirements. Additionally, self-managed nodes are particularly well suited for Oracle Cloud Infrastructure cluster networks. These nodes provide high bandwidth, low latency RDMA connectivity, making them a preferred option for certain networking setups. Lastly, the use of compute instance pools with self-managed nodes enables the creation of infrastructure for handling complex distributed computing tasks. This can greatly enhance the efficiency of your Kubernetes environment. Consider these points carefully to determine the optimal use of OKE self-managed nodes in your deployments. 03:30 Lois: What do we need to consider before creating a self-managed node and integrating it into a cluster? Mahendra: There are two crucial aspects to address. Firstly, you need to confirm that the cluster to which you plan to add a self-managed node is configured appropriately.  Secondly, it's essential to choose the right image for the compute instance hosting the self-managed node.  03:53 Nikita: Can you dive a little deeper into these prerequisites? Mahendra: To successfully integrate a self-managed node into your cluster, you must ensure that the cluster is an enhanced cluster. This is a crucial prerequisite for the addition of self-managed nodes. The flannel CNI plugin for pod networking should be utilized, not the VCN-native pod networking CNI plugin. This ensures optimal pod networking for your self-managed nodes. The control plane nodes of the cluster must be running Kubernetes version 1.25 or later. This is essential for compatibility and optimal performance. Lastly, maintain compatibility between the Kubernetes version on control plane nodes and worker nodes with a maximum allowable difference of two minor versions. This ensures a smooth and stable operation of your Kubernetes environment. Keep these cluster requirements in mind as you prepare to add self-managed nodes to your OKE cluster. 04:55 Lois: What about the image requirements when creating self-managed nodes? Mahendra: Choose either Oracle Linux 7 or Oracle Linux 8 image, for your self-managed nodes. Ensure that the selected image has a release date of March 28, 2023 or later. Obtain the image OCID, also known as Oracle Cloud Identifier, from the respective sources. When specifying an image, be mindful of the Kubernetes version it contains. It's your responsibility to select an image with a Kubernetes version that aligns with the Kubernetes version skew support policy. Keep in mind that the Container Engine for Kubernetes does not automatically check the compatibility. So it's up to you to ensure harmony between the Kubernetes version on the self-managed node and the cluster's control plane nodes. These considerations will help you make informed choices when configuring images for your self-managed nodes. 05:57 Nikita: I really like the flexibility and customization OKE self-managed nodes offer. Now I want to switch gears a little and ask you about OCI Service Operator for Kubernetes. Can you tell us a bit about it? Mahendra: OCI Service Operator for Kubernetes is an open-source Kubernetes add-on that transforms the way we manage and connect OCI resources within our Kubernetes clusters. This powerful operator enables you to effortlessly create, configure, and interact with OCI resources directly from your Kubernetes environment, eliminating the need for constant navigation between the Oracle Cloud Infrastructure Console, CLI, or other tools. With the OCI Service Operator, you can seamlessly leverage kubectl to call the operator framework APIs, providing a streamlined and efficient workflow. 06:53 Lois: On what framework is the OCI Service Operator built? Mahendra: OCI Service Operator for Kubernetes is built using the open-source Operator Framework toolkit. The Operator Framework manages Kubernetes-native applications called operators in an effective, automated, and scalable way. The Operator Framework comprises essential components like Operator SDK. This leverages the Kubernetes controller-runtime library, providing high-level APIs and abstractions for writing operational logic. Additionally, it offers tools for scaffolding and code generation. 07:35 Do you want to stay ahead of the curve in the ever-evolving AI landscape? Look no further than our brand-new OCI Generative AI Professional course and certification. For a limited time only, we're offering both the course and certification for free! So, don't miss out on this exclusive opportunity to get certified on Generative AI at no cost. Act fast because this offer is valid only until July 31, 2024. Visit https://education.oracle.com/genai to get started. That's https://education.oracle.com/genai. 08:14 Nikita: Welcome back! Mahendra, are there any other components within OCI Service Operator to manage Kubernetes deployments? Mahendra: The other essential component is Operator Lifecycle Manager, also abbreviated as OLM. OLM extends Kubernetes by introducing a declarative approach to install, manage, and upgrade operators within a cluster. The OCI Service Operator for Kubernetes is intelligently packaged as an Operator Lifecycle Manager bundle, simplifying the installation process on Kubernetes clusters. This comprehensive bundle encapsulates all necessary objects and definitions, including CRDs, RBACs, ConfigMaps, and deployments, making it effortlessly deployable on a cluster. 09:02 Lois: So much that users can take advantage of! What about OCI Service Operator's integration with other OCI services?  Mahendra: One of its standout features is its seamless integration with a range of OCI services. The first one is Autonomous Database, specifically tailored for transaction processing, mixed workloads, analytics, and data warehousing. Enjoy automated patching, upgrades, and tuning, allowing routine maintenance tasks to be performed without human intervention. The next on the list is MySQL HeatWave, a fully-managed Database Service designed for developing and deploying secure cloud-native applications using widely adopted MySQL open-source database. Third on the list is OCI Streaming service. Experience a fully managed, scalable, and durable solution for ingesting and consuming high-volume data streams in real time. Next is Service Mesh. This service offers a set of capabilities to facilitate communication among microservices within a cloud-native application. The communication is centrally managed and secured, ensuring a smooth and secure interaction. The OCI Service Operator for Kubernetes serves as a versatile bridge, seamlessly connecting your Kubernetes clusters with these powerful Oracle Cloud Infrastructure services. 10:31 Nikita: That's awesome! I've also heard about Ingress Controllers. Can you tell us what they are? Mahendra: A Kubernetes Ingress Controller serves as the enforcer of rules defined in a Kubernetes Ingress. Its primary role is to manage, load balance, and route incoming traffic to specific service pods residing on worker nodes within the cluster. At the heart of this process is the Kubernetes Ingress Resource. Think of it as a blueprint, a rich configuration holding routing rules and options, specifically crafted for handling HTTP and HTTPS traffic. It serves as a powerful orchestrator for managing external communication with services inside the cluster. 11:15 Lois: Mahendra, how do Ingress Controllers bring about efficiency? Mahendra: Efficiency comes with consolidation. With a single ingress resource, you can neatly gather routing rules for multiple services. This eliminates the need to create a Kubernetes service of type LoadBalancer for each service seeking external or private network traffic. The OCI native ingress controller is a powerhouse. It crafts an OCI Flexible Load Balancer, your gateway to efficient request handling. The OCI native ingress controller seamlessly adapts to changes in routing rules with real-time updates. 11:53 Nikita: And what about integration with an OKE cluster? Mahendra: Absolutely. It harmonizes with the cluster for streamlined traffic management. Operating as a single pod on a randomly selected worker node, it ensures a balanced workload distribution. 12:08 Lois: Moving on, let's talk about running applications on ARM-based nodes and GPU nodes. We'll start with ARM-based nodes.  Mahendra: Typically, developers use ARM-based worker nodes in Kubernetes cluster to develop and test applications. Selecting the right infrastructure is crucial for optimal performance.  12:28 Nikita: What kind of options do developers have when running applications on ARM-based nodes? Mahendra: When it comes to running applications on ARM-based nodes, you have a range of options at your fingertips. First up, consider the choice between ARM-based bare metal shapes and flexible VM shapes. Each comes with its own unique advantages. Now, let's talk about the heart of it all, the Ampere A1 Compute instances. These instances are driven by the cutting edge Ampere Altra processor, ensuring high performance and efficiency for your workloads. You must specify the ARM-based node pool shapes during cluster or node pool creation, whether you choose to navigate through the user-friendly console, leverage the flexibility of the API, or command with precision through the CLI, the process remains seamless. 13:23 Lois: Can you define pods to run exclusively on ARM-based nodes within a heterogeneous cluster setup? Mahendra: In scenarios where a cluster comprises node pools with ARM-based shapes alongside other shapes, such as AMD64, you can employ a powerful tool called node selector in the pod specification. This allows you to precisely dictate that an application should exclusively run on ARM-based worker nodes, ensuring your workloads aligns with the desired architecture. 13:55 Nikita: And before we end this episode, can you explain why developers must run applications on GPU nodes? Mahendra: Originally designed for graphics manipulations, GPUs prove highly efficient in parallel data processing. This makes them a top choice for deploying data-intensive applications. Our GPU nodes utilize cutting edge NVIDIA graphics cards ensuring efficient and powerful data processing. Seamless access to this computing prowess is made possible through CUDA libraries. To ensure smooth integration, be sure to select a GPU shape and opt for an Oracle Linux GPU image preloaded with the essential CUDA libraries. CUDA here is Compute Unified Device Architecture, which is a parallel computing platform and application-programming interface model created by NVIDIA. It allows developers to use NVIDIA graphics-processing units for general-purpose processing, rather than just rendering graphics. 14:57 Nikita: Thank you, Mahendra, for another insightful session. We appreciate you joining us today. Lois: For more information on everything we discussed, go to mylearn.oracle.com and search for the OCI Container Engine for Kubernetes Specialist course. You'll find plenty of demos and skill checks to supplement your learning. Join us next week when we'll discuss vital security practices for your OKE clusters on OCI. Until next time, this is Lois Houston… Nikita: And Nikita Abraham, signing off! 15:28 That's all for this episode of the Oracle University Podcast. If you enjoyed listening, please click Subscribe to get all the latest episodes. We'd also love it if you would take a moment to rate and review us on your podcast app. See you again on the next episode of the Oracle University Podcast.

Oke jadi one of us at least finished the whole series and trying to convince the other to continue watching. HAHAHAHAAHAHAHAHAHAHAHAH SEMUA ORANG LAGI SUKA BANGET BYEON WOO SEOK dan sekarang keyword Byeon Woo Seok juga lagi naik banget di mana-mana. Episode ini isinya spoiler semua ya!!!!! --- Podcast ngedrakor! dipersembahkan Dalam Ruang Produksi Studios, diproduseri bersama oleh Ron & Mal. Episode baru tayang mingguan! Baca berita drama Korea favoritmu di ⁠⁠⁠detikpop.com⁠⁠⁠ Follow Instagram kami di⁠⁠⁠ ⁠⁠@podcastngedrakor⁠⁠⁠⁠⁠ #PodcastNgedrakor #ngedrakordidetikcom #ngedrakordispotify --- Send in a voice message: https://podcasters.spotify.com/pod/show/ngedrakor/message

Want to gain insights into how virtual nodes provide a serverless Kubernetes experience?   Join hosts Lois Houston and Nikita Abraham, along with senior OCI instructor Mahendra Mehra, as they compare managed nodes and virtual nodes. Continuing from the previous episode, they explore how virtual nodes enhance Kubernetes deployments in Oracle Cloud Infrastructure.   OCI Container Engine for Kubernetes Specialist: https://mylearn.oracle.com/ou/course/oci-container-engine-for-kubernetes-specialist/134971/210836   Oracle University Learning Community: https://education.oracle.com/ou-community   LinkedIn: https://www.linkedin.com/showcase/oracle-university/   X (formerly Twitter): https://twitter.com/Oracle_Edu   Special thanks to Arijit Ghosh, David Wright, Radhika Banka, and the OU Studio Team for helping us create this episode.   --------------------------------------------------------   Episode Transcript: 00:00 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started! 00:25 Lois: Welcome to the Oracle University Podcast! I'm Lois Houston, Director of Innovation Programs with Oracle University, and with me is Nikita Abraham, Principal Technical Editor. Nikita: Hey everyone! In our last episode, we examined OCI Container Engine for Kubernetes, including its key features and benefits. Lois: Yeah, that was an interesting one. Today, we're going to discuss virtual nodes and their role in enhancing Kubernetes deployments in Oracle Cloud Infrastructure. Nikita: We're going to compare virtual nodes and managed nodes, and look at their differences and advantages. To take us through all this, we have Mahendra Mehra with us. Mahendra is a senior OCI instructor with Oracle University.  01:09 Lois: Hi Mahendra! From our discussion last week, we know that when creating a node pool with Container Engine for Kubernetes, we have the option of specifying the type of Oracle nodes as either managed nodes or virtual nodes. But I'm sure there are some key differences in the features supported by each type, right?  Mahendra: The primary point of differentiation between virtual nodes and managed nodes is in their management approach. When it comes to managed nodes, users are responsible for managing the nodes. They have the flexibility to configure them to meet the specific requirements. Users are also responsible for upgrading Kubernetes on managed nodes and for managing cluster capacity. You can create managed nodes and node pools in both basic clusters and enhanced clusters, whereas in virtual nodes, virtual nodes provide a serverless Kubernetes, experience, enabling users to run containerized applications at scale. The Kubernetes software is upgraded and security patches are applied while respecting application's availability requirements.  You can only create virtual nodes and virtual node pools in enhanced clusters. 02:17 Nikita: What about differences in terms of resource allocation? Are there any differences we should be aware of? Mahendra: When it comes to managed nodes, the resource allocation is at the node pool level and the users specify CPU and memory resource requirements for a given node pool. In the virtual nodes, the resource allocation is done at the pod level, where you can specify the CPU and memory resource requirements, but this time, as requests and limits in the pod specification.  02:45 Lois: What about differences in the approach to load balancing? Mahendra: When it comes to managed nodes, load balancing is between the worker nodes, whereas in virtual nodes, load balancing is between pods.  Also, load balancer security list management is never enabled, and you always must manually configure security rules. When using virtual nodes, load balances distribute traffic among pods' IP addresses and then assign node port.  03:12 Lois: And when it comes to pod networking? Mahendra: Under managed nodes, both the VCN-Native Pod Networking CNI plugin and the flannel CNI plugin are supported. When it comes to virtual nodes, only VCN-Native Pod Networking is supported. Also, only one VNIC is attached to each virtual node. Remember, IP addresses are not pre-allocated before pods are created. And the VCN-Native Pod Networking CNI plugin is not shown as running in the kube-system namespace. Pod subnet route tables must have route rules defined for a NAT gateway and a service gateway. 03:48 Nikita: OK… I have a question, Mahendra. When it comes to scaling Kubernetes clusters and node pools, can users adjust the cluster capacity in response to their changing requirements? Mahendra: When it comes to managed nodes, customers can scale the cluster and node pool up and down by changing the number of managed node pools and nodes respectively. They also have an option to enable autoscaling to automatically scale managed node pools and pods. When it comes to virtual nodes, operational overhead of cluster capacity management is handled for you by OCI. A virtual node pool scales automatically and can support up to 1000 pods per virtual node. Users also have an option to increase the number of virtual node pools or virtual nodes to scale up the cluster or node pool respectively. 04:37 Lois: And what about the pricing for each? Mahendra: Under managed nodes, you pay for the compute instances that execute applications, whereas under virtual nodes, you pay for the exact compute resources consumed by each Kubernetes pod. 04:55 Do you want to stay ahead of the curve in the ever-evolving AI landscape? Look no further than our brand-new OCI Generative AI Professional course and certification. For a limited time only, we're offering both the course and certification for free! So, don't miss out on this exclusive opportunity to get certified on Generative AI at no cost. Act fast because this offer is valid only until July 31, 2024. Visit https://education.oracle.com/genai to get started. That's https://education.oracle.com/genai. 05:34 Nikita: Welcome back! We were just discussing how when you have to choose between virtual nodes and managed nodes for your Kubernetes cluster, you need to consider several key points of differentiation, like the management approach, resource allocation, load balancing, pod networking, scaling, and pricing.  Lois: Yeah, it's important to understand the benefits and drawbacks of each approach to make informed decisions. Mahendra, now let's talk about the prerequisites to configure clusters with virtual nodes and the IAM policies that are required to use virtual nodes. Mahendra: Before you can use virtual nodes, you always have to set up at least one IAM policy, which is required in all circumstances by both tenancy administrators and non-administrator users. This basically means, to create and use clusters with virtual nodes and virtual node pools, you must endorse Container Engine for Kubernetes service to allow virtual nodes to create container instances in the Container Engine for Kubernetes service tenancy with a VNIC connected to a subnet of a VCN in your tenancy. All you need to do is create a policy in the root compartment with policy statements from the official documentation page. You will find them under the Working with Virtual Nodes section within the Container Engine topic.  06:55 Lois: Mahendra, how do you create and configure virtual nodes and virtual node pools? Mahendra: Creating virtual nodes is a pivotal step and it involves setting up a virtual node pool in a new cluster. This is exclusively applicable to enhanced clusters. You can initiate this process using the console, the CLI, or the API. Configuring your virtual node pools involves defining critical parameters. Firstly, we have the node count. This represents the number of virtual nodes you wish to create within your virtual node pool. These nodes will be strategically placed in the availability domains that you specify. Now, it's important to carefully consider the placement of these nodes. You can distribute them across different availability domains, ensuring high availability for your applications. Additionally, you have the option to place these nodes in a regional subnet, which is the recommended approach for optimal performance. 07:53 Nikita: Isn't the pod shape another important parameter? Can you tell us a bit about it? Mahendra: Pod shape refers to the type of shape you want for pods running on your virtual nodes within the virtual node pool. The pod shape is crucial as it determines the processor type on which you want your pods to run. It is important to note that only shapes available in your tenancy and supported by Container Engine for Kubernetes will be shown. So choose a shape that aligns with the requirements of your applications and services. A noteworthy point is that you explicitly specify the CPU and memory resource requirements for virtual nodes in the pod specification file. This ensures that your virtual nodes have the necessary resources to handle the workloads of your applications. Precision in specifying these requirements is key to achieving optimal performance. 08:49 Lois: What is the network setup for virtual nodes?  Mahendra: The pod running on virtual nodes utilize VCN-native pod networking, and it's crucial to specify how these pods in the node pool communicate with each other. This involves setting up a pod subnet, which is a regional subnet configured specially to host pods. The pod subnet you specify for virtual nodes must be private. Oracle recommends that the pod subnet and the virtual node subnets are the same. In addition to subnet configurations, you have the option to use security rules in network security group to control access to the pod subnet. This involves defining security rules within one or more NSGs that you specify with a maximum limit of five network security groups. Also, it is worth noting that using network security group is recommended over using security list. Now, let's shift our focus to virtual node communication. For this, you will configure a virtual node subnet. This subnet can be either a regional subnet, which is recommended, or an availability domain-specific subnet. And it's designed to host your virtual nodes. 10:02 Nikita: What are some key considerations for virtual node subnets? Mahendra: If you've specified load balancer subnets, ensure that the virtual node subnets are different. As with pod communication, Oracle recommends that the pod subnet and the virtual node subnet are the same, with the added condition that the virtual node subnet must be private. 10:23 Lois: Mahendra, can you take us through the fundamental tasks involved in managing virtual nodes and virtual node pools? Mahendra: Whether you're creating a new enhanced cluster using the Console, or looking to scale up an existing one, the creation process is versatile.  Creating virtual nodes involves establishing a virtual node pool. Virtual nodes can only be created within enhanced clusters. Listing virtual nodes task offers visibility into virtual nodes within a virtual node pool. Whether you prefer Console, CLI, or the API, you have the flexibility to choose the method that suits your workflow best. For a comprehensive understanding of your virtual node pools, navigate to the Cluster List page, and click on the name of the cluster. This will unveil the specifics of the virtual node pool you are interested in. Now let's talk about updating virtual node pools. Whether your initiating a new enhanced cluster, or expanding an existing one, the update process ensures your cluster aligns with your evolving requirements. You can easily update the virtual node pool's name for clarity. You can also dynamically change the number of virtual nodes to meet the workload demands, and you can fine tune the Node Placement using options like Availability Domain and Fault Domain settings. Moving on to an essential aspect of node pool management, that is deletion. It's crucial to understand that deleting a node pool is a permanent action. Once deleted, the node pool cannot be recovered.  12:04 Lois: Before we wrap up, Mahendra, can you talk about the critical factors when allocating CPU, memory, and storage resources to pods provisioned by virtual nodes within your OKE cluster? Mahendra: To ensure optimal performance, OKE calculates CPU and memory allocations at the pod level, a distinctive feature when using virtual nodes. This approach stands in contrast to the traditional worker node-level allocation. The allocation process takes into account several factors. First one is the CPU and memory requests and limits. These are specified for each container in the pod spec file, if present. Secondly, number of containers in the pod. The total number of containers impacts the overall resource requirements. And kube-proxy and container runtime requirements. A small but essential consideration taking up 0.25 GB of memory and negligible CPU. Pod CPU and memory requests must meet a minimum of 0.125 OCPUs and 0.5 GB of memory. 13:12 Nikita: Thank you, Mahendra, for this really insightful session. If you're interested in learning more about the topics we discussed today, head over to mylearn.oracle.com and search for the OCI Container Engine for Kubernetes Specialist course.  Lois: You'll find demos that you watch as well as skill checks that you can attempt to better your understanding. In our next episode, we'll journey into the world of self-managed nodes and discuss how to manage Kubernetes deployments. Until then, this is Lois Houston…  Nikita: And Nikita Abraham, signing off! 13:45 That's all for this episode of the Oracle University Podcast. If you enjoyed listening, please click Subscribe to get all the latest episodes. We'd also love it if you would take a moment to rate and review us on your podcast app. See you again on the next episode of the Oracle University Podcast.

Curious about how OCI Container Engine for Kubernetes (OKE) can transform the way your development team builds, deploys, and manages cloud-native applications? Listen to hosts Lois Houston and Nikita Abraham explore OKE's key features and benefits with senior OCI instructor Mahendra Mehra.   Mahendra breaks down complex concepts into digestible bits, making it easy for you to understand the magic behind OKE.   OCI Container Engine for Kubernetes Specialist: https://mylearn.oracle.com/ou/course/oci-container-engine-for-kubernetes-specialist/134971/210836   Oracle University Learning Community: https://education.oracle.com/ou-community   LinkedIn: https://www.linkedin.com/showcase/oracle-university/   X (formerly Twitter): https://twitter.com/Oracle_Edu   Special thanks to Arijit Ghosh, David Wright, Radhika Banka, and the OU Studio Team for helping us create this episode.   --------------------------------------------------------   Episode Transcript:   00:00 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started! 00:25 Nikita: Hello and welcome to the Oracle University Podcast. I'm Nikita Abraham, Principal Technical Editor with Oracle University, and with me is Lois Houston, Director of Innovation Programs. Lois: Hi there! If you've been listening to us these last few weeks, you'll know we've been discussing containerization, the Oracle Cloud Infrastructure Registry, and the basics of Kubernetes. Today, we'll dive into the world of OCI Container Engine for Kubernetes, also referred to as OKE.  Nikita: We're joined by Mahendra Mehra, a senior OCI instructor with Oracle University, who will take us through the key features and benefits of OKE and also talk about working with managed nodes. Hi Mahendra! Thanks for joining us today. 01:09 Lois: So, Mahendra, what is OKE exactly? Mahendra: Oracle Cloud Infrastructure Container Engine for Kubernetes is a fully managed, scalable, and highly available service that empowers you to effortlessly deploy your containerized applications to the cloud. But that's just the beginning. OKE can transform the way you and your development team build, deploy, and manage cloud native applications. 01:36 Nikita: What would you say are some of its most defining features?    Mahendra: One of the defining features of OKE is the flexibility it offers. You can specify whether you want to run your applications on virtual nodes or opt for managed nodes. Regardless of your choice, Container Engine for Kubernetes will efficiently provision them within your existing OCI tenancy on Oracle Cloud Infrastructure. Creating OKE cluster is a breeze, and you have a couple of fantastic tools at your disposal-- the console and the rest API. These make it super easy to get started. OKE relies on Kubernetes, which is an open-source system that simplifies the deployment, scaling, and management of containerized applications across clusters of hosts. Kubernetes is an incredible system that groups containers into logical units known as pods. And these pods make managing and discovering your applications very simple. Not to mention, Container Engine for Kubernetes uses Kubernetes versions that are certified as conformant by the Cloud Native Computing Foundation, also abbreviated as CNCF. And here's the icing on the cake. Container Engine for Kubernetes is ISO-compliant. The other two ISO-IEC standards—27001, 27017, and 27018. That's your guarantee of a secure and reliable platform.   03:08 Lois: That's great. But how do you access all this power? Mahendra: You can define and create your Kubernetes cluster using the intuitive console and the robust rest API. Once your clusters are up and running, you can manage them using the Kubernetes command line, also known as kubectl, the user-friendly Kubernetes dashboard, and the powerful Kubernetes API. 03:32 Nikita: I love the idea of an intuitive console and being able to manage everything from a centralized place. Lois: Yeah, that's fantastic! Mahendra, can you talk us through the magic that happens behind the scenes? What's Oracle's role in all this? Mahendra: All the master nodes or control plane nodes are managed by Oracle. This includes components like etcd, the API server, and the controller manager among others. To ensure reliability, we make sure multiple copies of these master components are distributed across different availability domains. And we don't stop there. We also manage the Kubernetes dashboard and even handle the self-healing mechanism of both the cluster and the worker nodes. All of these are meticulously created and managed within your Oracle tenancy. 04:19 Lois: And what happens at the user's end? What is their responsibility? Mahendra: At your end, you have the power to manage your worker nodes. Using different compute shapes, you can create and control them in your own user tenancy. So, as you can see, it's a perfect blend of Oracle's expertise and your control. 04:38 Nikita: So, in your opinion, why should users consider OKE their go-to solution for all things Kubernetes? Mahendra: Imagine a world where building and maintaining Kubernetes environments, be it master nodes or worker nodes, is no longer complex, costly, or even time-consuming. OKE is here to make your life easier by seamlessly integrating Kubernetes with various container life cycle management products, which includes container registries, CI/CD frameworks, networking solutions, storage options, and top-notch security features. And speaking of security, OKE gives you the tools you need to manage and control team access to production clusters, ensuring granular access to Kubernetes cluster in a straightforward process. It empowers developers to deploy containers quickly, provides devops teams with visibility and control for seamless Kubernetes management, and brings together Kubernetes container orchestration with Oracle's advanced cloud infrastructure. This results in robust control, top tier security, IAM, and consistent performance. 05:50 Nikita: OK…a lot of benefits! Mahendra, I know there have been ongoing enhancements to the OKE service. So, when creating a new cluster with Container Engine for Kubernetes, what is the cluster type we should specify?  Mahendra: The first type is the basic clusters. Basic clusters support all the core functionality provided by Kubernetes and Container Engine for Kubernetes. Basic clusters come with a service-level objective, but not a financially backed service level agreement. This means that Oracle guarantees a certain level of availability for the basic cluster, but there is no monetary compensation if that level is not met. On the other hand, we have the enhanced clusters. Enhanced clusters support all available features, including features not supported by basic clusters.  06:38 Lois: OK. So, can you tell us more about the features supported by enhanced clusters? Mahendra: As we move towards a more digitized world, the demand for infrastructure continues to rise. However, with virtual nodes, managing the infrastructure of your cluster becomes much simpler. The burden of manually scaling, upgrading, or troubleshooting worker nodes is removed, giving you more time to focus on your applications rather than the underlying infrastructure. Virtual nodes provide a great solution for managing large clusters with a high number of nodes that require frequent updates or scaling. With this feature, you can easily simplify the management of your cluster and focus on what really matters, that is your applications. Managing cluster add-ons can be a daunting task. But with enhanced clusters, you can now deploy and configure them in a more granular way. This means that you can manage both essential add-ons like CoreDNS and kube-proxy as well as a growing portfolio of optional add-ons like the Kubernetes Dashboard.  With enhanced clusters, you have complete control over the add-ons you install or disable, the ability to select specific add-on versions, and the option to opt-in or opt-out of automatic updates by Oracle. You can also manage add-on specific customizations to tailor your cluster to meet the needs of your application. 08:05 Lois: Do users need to worry about deploying add-ons themselves? Mahendra: Oracle manages the lifecycle of add-ons so that you don't have to worry about deploying them yourself. This level of control over add-ons gives you the flexibility to customize your cluster to meet the unique needs of your applications, making managing your cluster a breeze. 08:25 Lois: What about scaling? Mahendra: Scaling your clusters to meet the demands of your workload can be a challenging task. However, with enhanced clusters, you can now provision more worker nodes in a single cluster, allowing you to deploy larger workloads on the same cluster which can lead to better resource utilization and lower operational overhead. Having fewer larger environments to secure, monitor, upgrade, and manage is generally more efficient and can help you save on cost. Remember, there are limits to the number of worker nodes supported on an enhanced cluster, so you should review the Container Engine for Kubernetes limits documentation and consider the additional considerations when defining enhanced clusters with large number of managed nodes.  09:09  Nikita: Ensuring the security of my cluster would be of utmost importance to me, right? How would I do that with enhanced clusters? Mahendra: With enhanced clusters, you can now strengthen cluster security through the use of workload identity. Workload identity enables you to define OCI IAM policies that authorize specific pods to make OCI API calls and access OCI resources. By scoping the policies to Kubernetes service account associated with application pods, you can now allow the applications running inside those pods to directly access the API based on the permissions provided by the policies. 09:48 Nikita: Mahendra, what type of uptime and server availability benefits do enhanced clusters provide? Mahendra: You can now rely on a financially backed service level agreement tied to Kubernetes API server uptime and availability. This means that you can expect a certain level of uptime and availability for your Kubernetes API server, and if it degrades below the stated SLA, you'll receive compensation. This provides an extra level of assurance and helps ensure that your cluster is highly available and performant. 10:20 Lois: Mahendra, do you have any tips for us to remember when creating basic and enhanced clusters? Mahendra: When using the console to create a cluster, a new cluster is created as an enhanced cluster by default unless you explicitly choose to create a basic cluster. If you don't select any enhanced features during cluster creation, you have the option to create the new cluster as a basic cluster. When using CLI or API to create a cluster, you can specify whether to create a basic cluster or an enhanced cluster. If you don't explicitly specify the type of cluster to create, a new cluster is created as a basic cluster by default. Creating a new cluster as an enhanced cluster enables you to easily add enhanced features later even if you didn't select any enhanced features initially. If you do choose to create a new cluster as a basic cluster, you can still choose to upgrade the basic cluster to an enhanced cluster later on. However, you cannot downgrade an enhanced cluster to a basic cluster. These points are really important while you consider selection of a basic cluster or an enhanced cluster for your usage. 11:34 Do you want to stay ahead of the curve in the ever-evolving AI landscape? Look no further than our brand-new OCI Generative AI Professional course and certification. For a limited time only, we're offering both the course and certification for free! So, don't miss out on this exclusive opportunity to get certified on Generative AI at no cost. Act fast because this offer is valid only until July 31, 2024. Visit https://education.oracle.com/genai to get started. That's https://education.oracle.com/genai. 12:13 Nikita: Welcome back! I want to move on to serverless Kubernetes with virtual nodes. But I think before we do that, we first need to have a basic understanding of what managed nodes are.   Mahendra: Managed nodes run on compute instances within your tenancy, and are at least partly managed by you. In the context of Kubernetes, a node is a compute host that can be either a virtual machine or a bare metal host. As you are responsible for managing managed nodes, you have the flexibility to configure them to meet your specific requirements. You are responsible for upgrading Kubernetes on managed nodes and for managing cluster capacity. Nodes are responsible for running a collection of pods or containers, and they are comprised of two system components: the kubelet, which is the host brain, and the container runtime such as CRI-O, or containerd.  13:07 Nikita: Ok… so what are virtual nodes, then? Mahendra: Virtual nodes are fully managed and highly available nodes that look and act like real nodes to Kubernetes. They are built using the open source CNCF Virtual Kubelet Project, which provides the translation layer between OCI and Kubernetes. 13:25 Lois: So, what makes Oracle's managed virtual Kubernetes product different? Mahendra: OCI is the first major cloud provider to offer a fully managed virtual Kubelet product that provides a serverless Kubernetes experience through virtual nodes. Virtual nodes are configured by customers and are located within a single availability and fault domain within OCI. Virtual nodes have two main components: port management and container instance management. Virtual nodes delegates all the responsibility of managing the lifecycle of pods to virtual Kubernetes while on a managed node, the kubelet is responsible for managing all the lifecycle state. The key distinction of virtual nodes is that they support up to a 1,000 pods per virtual node with the expectation of supporting more in the future. 14:15 Nikita: What are the other benefits of virtual nodes? Mahendra: Virtual nodes offer a fully managed experience where customers don't have to worry about managing the underlying infrastructure of their containerized applications. Virtual nodes simplifies scaling patterns for customers. Customers can scale their containerized application up or down quickly without worrying about the underlying infrastructure, and they can focus solely on their applications. With virtual nodes, customers only pay for the resources that their containerized application use. This allows customers to optimize their costs and ensures that they are not paying for any unused resources. Virtual nodes can support over 10 times the number of pods that a normal node can. This means that customer can run more containerized applications on virtual nodes, which reduces operational burden and makes it easier to scale applications. Customers can leverage container instances in serverless offering from OCI to take advantage of many OCI functionalities natively. These functionalities include strong isolation and ultimate elasticity with respect to compute capacity. 15:26 Lois: When creating a cluster using Container Engine for Kubernetes, we have the flexibility to customize the worker nodes within the cluster, right? Could you tell us more about this customization? Mahendra: This customization includes specifying two key elements. Firstly, you can select the operating system image to be used for worker nodes. This image serves as a template for the worker node's virtual hard drive, and determines the operating system and other software installed. Secondly, you can choose the shape for your worker nodes. The shape defines the number of CPUs and the amount of memory allocated to each instance, ensuring it meets your specific requirements. This customization empowers you to tailor your OKE cluster to your exact needs. It is important to note that you can define and create OKE clusters using both the console and the REST API. This level of control is specially valuable for your development team when building, deploying, and managing cloud native applications.  You have the option to specify whether applications should run on virtual nodes or managed nodes. And Container Engine for Kubernetes efficiently provisions them on Oracle Cloud Infrastructure within your existing OCI tenancy. This flexibility ensures that you can adapt your OKE cluster to suit the specific requirements of your projects and workloads. 16:56 Lois: Thank you so much, Mahendra, for giving us your time today. For more on the topics we discussed, visit mylearn.oracle.com and look for the OCI Container Engine for Kubernetes Specialist course. Join us next week as we dive deeper into working with OKE virtual nodes. Until then, this is Lois Houston… Nikita: And Nikita Abraham, signing off! 17:18 That's all for this episode of the Oracle University Podcast. If you enjoyed listening, please click Subscribe to get all the latest episodes. We'd also love it if you would take a moment to rate and review us on your podcast app. See you again on the next episode of the Oracle University Podcast.

Welcome to a new season of the Oracle University Podcast, where we delve deep into the world of OCI Container Engine for Kubernetes. Join hosts Lois Houston and Nikita Abraham as they ask senior OCI instructor Mahendra Mehra about the transformative power of containers in application deployment and why they're so crucial in today's software ecosystem.   Uncover key differences between virtualization and containerization, and gain insights into Docker components and commands.   Getting Started with Oracle Cloud Infrastructure: https://oracleuniversitypodcast.libsyn.com/getting-started-with-oracle-cloud-infrastructure-1   Networking in OCI: https://oracleuniversitypodcast.libsyn.com/networking-in-oci   OCI Identity and Access Management: https://oracleuniversitypodcast.libsyn.com/oci-identity-and-access-management   OCI Container Engine for Kubernetes Specialist: https://mylearn.oracle.com/ou/course/oci-container-engine-for-kubernetes-specialist/134971/210836   Oracle University Learning Community: https://education.oracle.com/ou-community   LinkedIn: https://www.linkedin.com/showcase/oracle-university/   X (formerly Twitter): https://twitter.com/Oracle_Edu   Special thanks to Arijit Ghosh, David Wright, Radhika Banka, and the OU Studio Team for helping us create this episode.   ---------------------------------------------------------   Episode Transcript:   00:00 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started! 00:26 Lois: Hello and welcome to the Oracle University Podcast! I'm Lois Houston, Director of Innovation Programs with Oracle University, and with me is Nikita Abraham, Principal Technical Editor.  Nikita: Hi everyone! Welcome to a new season of the Oracle University Podcast. This time around, we're going to delve into the world of OCI Container Engine for Kubernetes, or OKE. For the next couple of weeks, we'll cover key aspects of OKE to help you create, manage, and optimize Kubernetes clusters in Oracle Cloud Infrastructure. 00:58 Lois: So, whether you're a cloud native developer, Kubernetes administrator and developer, a DevOps engineer, or site reliability engineer who wants to enhance your expertise in leveraging the OCI OKE service for cloud native application solutions, you'll want to tune in to these episodes for sure. And if that doesn't sound like you, I'll bet you will find the season interesting even if you're just looking for a deep dive into this service. Nikita: That's right, Lois. In today's episode, we'll focus on concepts of containerization, laying the foundation for your journey into the world of containers. And taking us through all this is Mahendra Mehra, a senior OCI instructor with Oracle University. 01:38 Lois: Hi Mahendra! We're so glad to start our look at containerization with you today. Could you give us an overview? Why is it important in today's software world? Mahendra: Containerization is a form of virtualization, operates by running applications in isolated user spaces known as containers.  All these containers share the same underlying operating system. The container engine, pivotal in containerization technologies and container orchestration platforms, serves as the container runtime environment. It effectively manages the creation, deployment, and execution of containers. 02:18 Lois: Can you simplify this for a novice like me, maybe by giving us an analogy?  Mahendra: Imagine a container as a fully packaged and portable computing environment. It's like a digital suitcase that holds everything an application needs to run—binaries, libraries, configuration files, dependencies, you name it. And the best part, it's all encapsulated and isolated within container. 02:46 Nikita: Mahendra, how is containerization making our lives easier today?  Mahendra: In olden days, running an application meant matching it with your machine's operating system. For example, Windows software required a Windows machine. However, containerization has rewritten this narrative. Now, it's ancient history. With containerization, you create a single software package, a container that gracefully runs on any device or operating systems. What's fascinating is that these containers seamlessly run while sharing the host operating system. The container engine is like a shadow abstracted from the host operating system with limited access to underlying resources. Think of it as a super lightweight virtual machine. The beauty of this, the containerized application becomes a globetrotter, seamlessly running on bare metal within VMs or on the cloud platforms without needing tweaks for each environment. 03:52 Nikita: How is containerization different from traditional virtualization? Mahendra: On one side, we have traditional virtualization. It's like having multiple houses on a single piece of land, and each house or virtual machine has its complete setup—wall, roofs, and utilities. This setup, while providing isolation, can be resource-intensive with each virtual machine carrying its entire operating system. Now, let's shift gears to containerization, the modern day superhero. Imagine a high-rise building where each floor represents a container. These containers share the same building or host operating system, but have their private space or isolated user space. Here's the magic. They are super lightweight, don't carry extra baggage of a full operating system and can swiftly move between different floors. 04:50 Lois: Ok, gotcha. That sounds pretty efficient! So, what are the direct benefits of containerization?  Mahendra: With containerization technology, there's less overhead during startup and no need to set up a separate guest OS for each application since they all share the same OS kernel. Because of this high efficiency, containerization is commonly used for packing up the many individual microservices that make up modern applications. Containerization unfolds a spectrum of benefits, delivering unparalleled portability as containers run uniformly across diverse platforms. This agility, fostered by open source container engines, empowers developers with cross-platform flexibility. The speed of containerized applications known for their lightweight nature reduces cost, boosts efficiency, and accelerates start times. Fault isolation ensures robustness, allowing independent operations without affecting others. Efficiency thrives as containers share the OS kernel and reusable layers, optimizing server utilization. The ease of management is achieved through orchestration platforms like Kubernetes automating essential tasks. Security remains paramount as container isolation and defined permissions fortify the infrastructure against malicious threats. Containerization emerges not just as a technology but as a transformative force, redefining how we build, deploy, and manage applications in the digital landscape. 06:37 Lois: It sure makes deployment efficient, scalability, and seamless! Mahendra, various components of Docker architecture work together to achieve containerization goals, right? Can you walk us through them? Mahendra: A developer or a DevOps professional communicates with Docker engine through the Docker client, which may be run on the same computer as Docker engine in case of development environments or through a remote shell. So whenever a developer fires a Docker command, the client sends them to the Docker Daemon which carries them out. The communication between the Docker client and the Docker host is usually taken place through REST APIs. The Docker clients can communicate with more than one Daemon at a time.  Docker Daemon is a persistent background process that manages Docker images, containers, networks, and storage volumes. The Docker Daemon constantly listens to the Docker API request from the Docker clients and processes them. Docker registries are services that provide locations from where you can store and download Docker images. In other words, a Docker registry contains repositories that host one or more Docker images. Public registries include Docker Hub and Docker Cloud and private registries can also be used. Oracle Cloud Infrastructure offers you services like OCIR, which is also called a container registry, where you can host your own private or public registry. 08:02 Do you want to stay ahead of the curve in the ever-evolving AI landscape? Look no further than our brand-new OCI Generative AI Professional course and certification. For a limited time only, we're offering both the course and certification for free. So, don't miss out on this exclusive opportunity to get certified on Generative AI at no cost. Act fast because this offer is valid only until July 31, 2024. Visit https://education.oracle.com/genai to get started. That's https://education.oracle.com/genai. 08:39 Nikita: Welcome back! Mahendra, I'm wondering how virtual machines are different from containers. How do virtual machines work? Mahendra: A hypervisor or a virtual machine monitor is a software, firmware, or hardware that creates and runs virtual machines. It is placed between the hardware and the virtual machines, and is necessary to virtualize the server. Within each virtual machine runs a unique guest operating system. VMs with different operating systems can run on the same physical server. A Linux VM can sit alongside a Windows VM and so on. Each VM has its own binaries, libraries, and application that it services. And the VM may be many gigabytes in size. 09:22 Lois: What kind of benefits do we see from virtual machines? Mahendra: This technique provides a variety of benefits like the ability to consolidate applications into a single system, cost savings through reduced footprints, and faster server provisioning. But this approach has its own drawbacks. Each VM includes a separate operating system image, which adds overhead in memory and storage footprint. As it turns out, this issue adds complexity to all the stages of software development lifecycle, from development and test to production and disaster recovery as well. It also severely limits the portability of applications between different cloud providers and traditional data centers. And this is where containers come to the rescue.  10:05 Lois: OK…how do containers help in this situation? Mahendra: Containers sit on top of a physical server and its host operating system—typically, Linux or Windows. Each container shares the host OS kernel and usually the binaries and libraries as well. But the shared components are read only. Sharing OS resources such as libraries significantly reduces the need to reproduce the operating system code. A server can run multiple workloads with a single operating system installation. Containers are thus exceptionally lightweight. They are only megabytes in size and take just seconds to start. What this means in practice is you can put two or three times as many applications on a single server with containers than you can put on a virtual machine. Compared to containers, virtual machines take minutes to run and are order of magnitude larger than an equivalent container measured in gigabytes versus megabytes. 11:01 Nikita: So then, is there ever a time you should use a virtual machine? Mahendra: You should use a virtual machine when you want to run applications that specifically require a new OS, also when isolation and security are your priority over everything else. In most scenarios, a container will provide a lighter, faster, and more cost-effective solution than the virtual machines. 11:22 Lois: Now that we've discussed containerization and the different Docker components, can you tell us more about working with Docker images? We first need to know what a Dockerfile is, right?  Mahendra: A Dockerfile is a text file that defines a Docker image. You'll use a Dockerfile to create your own custom Docker image. In other words, you use it to define your custom environment to be used in a Docker container. You'll want to create your own Dockerfile when existing images won't meet your project needs to different runtime requirements, which means that learning about Docker files is an essential part of working with Docker. Dockerfile is a step-by-step definition of building up a Docker image. It provides a set of standard instructions to be used in Dockerfile that Docker will execute when you issue a Docker build command. 12:09 Nikita: Before we wrap up, can you walk us through some Docker commands? Mahendra: Every Dockerfile must start with a FROM instruction. The idea behind this is that you need a starting point to build your image. It can be from scratch or from an existing image available in the Docker registry.  The RUN command is used to execute a command and will wait till the command finishes its execution. Since most of the images are Linux-based, a good practice is to set up a directory you will work in. That's the purpose of work directory line. It defines a directory and moves you in. The COPY instruction helps you to copy your source code into the image. ENV provides default values for variables that can be accessed within the containers. If your app needs to be reached from outside the container, you must open its listening port using the EXPOSE command. Once your application is ready to run, the last thing to do is to specify how to execute it. You must add the CMD line with the same command with all the arguments you used locally to launch your application. This command can also be used to execute commands at runtime for the containers, but we can be more flexible using the ENTRYPOINT command. Labels are used in Dockerfile to help organize your Docker images.   13:20 Lois: Thank you, Mahendra, for joining us today. I learned a lot! And if you want to learn more about working with Docker images, go to mylearn.oracle.com and search for the OCI Container Engine for Kubernetes Specialist course. The course is free so you can get started right away. Nikita: Yeah, a fundamental understanding of core OCI services, like Identity and Access Management, networking, compute, storage, and security, is a prerequisite to the course and will certainly serve you well when leveraging the OCI OKE service. And the quickest way to gain this knowledge is by completing the OCI Foundations Associate learning path on MyLearn and getting certified. You can also listen to episodes from our first season, called OCI Made Easy, where we discussed these topics. We'll put a few links in the show notes so you can easily find them.  Lois: We're looking forward to having Mahendra join us again next week when we'll talk about container registries. Until next time, this is Lois Houston… Nikita: And Nikita Abraham signing off! 14:24 That's all for this episode of the Oracle University Podcast. If you enjoyed listening, please click Subscribe to get all the latest episodes. We'd also love it if you would take a moment to rate and review us on your podcast app. See you again on the next episode of the Oracle University Podcast.

Raidījumā Diplomātiskās pusdienas šoreiz stāsts par Okeānijas valsti Tuvalu. Šo valsti kāds varētu zināt pēc agrākā nosaukuma – Elisa salas. Šis nosaukums bija līdz 1978. gadam, kad Tuvalu ieguva neatkarību. Tuvalu uzskata par vienu no visattālākajām pasaules valstīm, jo atrodas Klusā okeāna vidū ar relatīvi maz piekļuves iespējām, kuras ne tikai apdzīvo, bet arī apmeklē ļoti mazs skaits cilvēku. Tuvalu tiek uzskatīta par otru pasaulē vismazāko valsti pēc Vatikāna iedzīvotāju skaita ziņā. Tuvalu var sacensties tikai ar netālu esošo Nauru par to, kura ir otra mazākā valsts. Sacensība, kuras rezultātu bieži nosaka viens cilvēks. Jaunākie dati liecina, ka Tuvalu apdzīvo 11733 cilvēku. No tiem septiņi tūkstoši dzīvo galvaspilsētā Funafuti. Un absolūtais vairākums dzīvo tikai uz vienas no daudzajām salām – Fongafale, kura ir garena sala, vietām tikai 20 metrus plata. Tuvalu atrodas uz arhipelāga, kuru veido seši atoli un trīs uz rifiem izvietotas salas. Kā jau bieži esam runājuši, salu valstis ļoti apdraud klimata pārmaiņas. Tuvalu sauszeme vidēji virs jūras līmeņa atrodas vien divu metru augstumā. Tas ir izraisījis to, ka vairākus gadu desmitus ir nopietni apspriesta iespēja visu valsti pārcelt uz Jaunzēlandi vai Fidži, kad situācija kļūs nepanesama. Distance līdz Tuvalu un sarežģītā piekļuve ir izraisījusi to, ka valsti katru gadu apmeklē vien apmēram 2000 cilvēku. Lielākoties no blakus esošajām Fidži, Austrālijas un Jaunzēlandes. Tā rezultātā valstī nav tūristiem domātas infrastruktūras, ieskaitot informācijas biroju vai suvenīru veikalu. Tuvalu praktiski nav noziedzības, nav malārijas, nav indīgo čūsku un trakumsērgas. Odi un mušas gan esot, bet tie nav bīstami. Pamatiedzīvotāji Tuvalu ieradās apmēram pirms 1000 gadiem. Ticamākais, ka no blakus esošajām Samoa vai Tongas. Vienlaicīgi Tuvalu arī kļuva par tālākas pārceļošanas vietu daudziem polinēziešu izcelsmes cilvēkiem, kas apmetās Melanēzijā un Mikronēzijā. Spāņu ceļotājs Alvaro Mendana de Neira bija pirmais eiropietis, kurš ieradās Tuvalu 1558. un arī 1595. gadā. Un tad līdz pat 1781. gadam, kad salās ieradās britu kapteinis Tomass Gilberts. Tuvalu vēlākajos gadsimtos bieži apciemoja britu, amerikāņu, nīderlandiešu, kanādiešu, peru un pat krievu kuģi. 1819. gadā kanādieši salām iedeva Elisa salu nosaukumu, bet kristieši misionāri vietējos pievērsa kristietībai apmēram četrdesmit gadus vēlāk. Rezultātā 93 procenti no Tuvalu iedzīvotājiem ir protestanti. 1892. gadā Elisa salas kopā ar Gilberta salām kļuva par britu protektorātu un Pirmā pasaules kara vidū par koloniju. Tuvalu iedzīvotāji – polinēzieši – nodalījās no Gilberta salu iedzīvotājiem mikronēziešiem referenduma ceļā 1974. gadā. Četrus gadus vēlāk ieguva pilnīgu neatkarību, lai arī ASV savas pretenzijas oficiāli izbeidza tikai 1979. gadā. Gilberta salas mūsdienās pazīstam kā valsti ar nosaukumu Kiribati. Tuvalu salās Otrā pasaules kara laikā atradās sabiedroto militārā bāze, kas arī skaidro daudzu valstu interesi par salām. To agrākās stratēģiskās nozīmes dēļ. Mūsdienās Tuvalu ir viena no valstīm, kurām nav pastāvīgas armijas. Un arī valsts galva ir britu karalis Čārlzs Trešais. Vienlaicīgi valsts ir relatīvi aktīva starptautisko organizāciju dalībniece. Par ANO 189. dalībvalsti Tuvalu kļuva 2000. gada septembrī, bet tā ir arī Klusā okeāna savienības sekretariāta un Klusā okeāna salu foruma dalībvalsts, kā arī Mazo valstu alianses dalībvalsts. Par Tuvalu centieniem izmantot savu dalību starptautiskajās organizācijās un digitālās iespējas valsts ienākumu vairošanai stāsta Māris Cepurītis, Austrumeiropas politikas pētījumu centra direktors un Rīgas Stradiņa universitātes lektors.

"Die Nummer eins, die Nummer eins, die Nummer eins der Stadt sind wir", intonierte Oke später beim ausgelassenen Feiern auf dem Rasen des Millerntor (Feierbiest scheint das neue Wort der Saison zu sein ;). Vorher jedoch war Singen, noch ein wenig bangen und Osnabrücker Konter überstehen angesagt. Für uns POPcaster als Erinnerung haben wir diesen Bonus aufgenommen ... Hört live und unzensiert, welchen Quatsch wir uns auf der Tribüne erzählen, wenn auch ein historisches Spiel mal seine Längen hat ;) Ach, und wenn euch unsere Aufstiegssaison-Schnackerei gefallen hat, dann supportet uns via Steady: https://steadyhq.com/de/stpauli/about

"Die Nummer eins, die Nummer eins, die Nummer eins der Stadt sind wir", intonierte Oke später beim ausgelassenen Feiern auf dem Rasen des Millerntor (Feierbiest scheint das neue Wort der Saison zu sein ;). Vorher jedoch war Singen, noch ein wenig bangen und Osnabrücker Konter überstehen angesagt. Für uns POPcaster als Erinnerung haben wir diesen Bonus aufgenommen ... Hört live und unzensiert, welchen Quatsch wir uns auf der Tribüne erzählen, wenn auch ein historisches Spiel mal seine Längen hat ;) Ach, und wenn euch unsere Aufstiegssaison-Schnackerei gefallen hat, dann supportet uns via Steady: https://steadyhq.com/de/stpauli/about Du möchtest deinen Podcast auch kostenlos hosten und damit Geld verdienen? Dann schaue auf www.kostenlos-hosten.de und informiere dich. Dort erhältst du alle Informationen zu unseren kostenlosen Podcast-Hosting-Angeboten. kostenlos-hosten.de ist ein Produkt der Podcastbude.Gern unterstützen wir dich bei deiner Podcast-Produktion.

"Die Nummer eins, die Nummer eins, die Nummer eins der Stadt sind wir", intonierte Oke später beim ausgelassenen Feiern auf dem Rasen des Millerntor (Feierbiest scheint das neue Wort der Saison zu sein ;). Vorher jedoch war Singen, noch ein wenig bangen und Osnabrücker Konter überstehen angesagt. Für uns POPcaster als Erinnerung haben wir diesen Bonus aufgenommen ... Hört live und unzensiert, welchen Quatsch wir uns auf der Tribüne erzählen, wenn auch ein historisches Spiel mal seine Längen hat ;) Ach, und wenn euch unsere Aufstiegssaison-Schnackerei gefallen hat, dann supportet uns via Steady: https://steadyhq.com/de/stpauli/about Du möchtest deinen Podcast auch kostenlos hosten und damit Geld verdienen? Dann schaue auf www.kostenlos-hosten.de und informiere dich. Dort erhältst du alle Informationen zu unseren kostenlosen Podcast-Hosting-Angeboten. kostenlos-hosten.de ist ein Produkt der Podcastbude.Gern unterstützen wir dich bei deiner Podcast-Produktion.

In der Aprilausgabe von Drama! sprechen wir für ein Mal nicht über Theater, sondern über Musik. Oke, natürlich über die Musik im Theater. Also über Theatermusik. Im Studio zu Besuch war für dieses Gespräch die Komponistin und Klangkünstlerin Aleksandra Sucur. In dieser Drama! Ausgabe gibt es deshalb nicht nur ein sehr spannendes und feinfühliges Gespräch zu hören, sondern auch vier Musikstücke- natürlich von Aleksandra Sucur komponiert (und gesungen!)- zu hören. Und zwar folgende Stücke: - seCure Opener - Cloud - Abstieg - Barely Alive Mehr Infos zu Aleksandra Sucur und ihren Projekten findet ihr hier: https://www.aleksandrasucur.ch/

Raidījumā Diplomātiskās pusdienas stāsts par Palau Republiku. Tā atrodama Okeānijā, konkrēti Mikronēzijā. Šī Klusajā okeānā atrodamā valsts sastāv no apmēram 340 salām un saliņām. Un Palau šobrīd dzīvo nepilni 22 tūkstoši cilvēku. Respektīvi tikpat daudz cilvēku, cik Zolitūdē. Vienā pašā Purvciemā ir trīs reizes vairāk iedzīvotāju nekā visā Palau valstī. Un vienlaicīgi Palau nav mazākā valsts pasaulē. Tā pat nav mazāko valstu desmitniekā. Toties tās galvaspilsēta Ngerulmude gan ir rekordiste ar to, ka ir vismazāk apdzīvotā galvaspilsēta pasaulē. Tajā pat netiek uzskaitīti cilvēki, jo pirms dažiem gadiem, kad to izdarīja, sanāca apaļa nulle iedzīvotāju. Interesanti, ka tulkojumā no palau valodas Ngerulmude nozīmē “vieta, kur dzīvo fermentētas enģeļzivis”. Palau, starp citu, uzstāda vēl vienu politisko rekordu. Tā skaitās pasaulē visvairāk pārvaldītā vieta. Proti, valsts atrodas uz neliela arhipelāga, bet tā ir iedalīta sešpadsmit administratīvajos reģionos un katrai no šīm pašvaldībām ir savs parlaments un arī cilšu vecāko padomes. Ja pieskaita valsts līmeņa institūcijas tad skaitlis ar valsts amatpersonām krasi pieaug uz kopējo iedzīvotāju skaitu. Palau parlaments – Nacionālais Kongress sastāv no divām palātām, kurā ir pārstāvēti bezpartejiski deputāti. Senātā ir 13 cilvēki un Delegātu palātā ir 16. Bet Palau galvaspilsētas vidū ir atrodams cietums. Ne tikai tas ir vienīgais cietums valstī. Tas pats par sevi ir tūristu apskates objekts. Koror cietuma ieslodzītie cietuma veikaliņā tirgo pašu darinātus koka suvenīrus. Pirms dažiem gadiem cietumā par dažādiem noziegumiem sēdējā 79 cilvēki, no kuriem trīs bija sievietes. Tropiskajā Palau pamatiedzīvotāji ienāca vairāk nekā pirms divarpus tūkstošiem gadu no relatīvi netālu esošās Indonēzijas. Pirmatnējie Palau iedzīvotāji esot izveidojuši visnotaļ sarežģītas pārvaldības sistēmas, kā arī attīstījuši zvejniecības un lauksaimniecības prasmes. Pirmais eiropietis, kurš nonāca Palau, bija angļu kapteinis Henrijs Vilsons, kura kuģis cieta katastrofu 1783. gadā un viņš tika izmests uz salas vētras laikā. 19. gadsimta beigās salas kolonizēja spāņi, kuri pēc tam tās pārdeva vāciešiem. Palau kļuva par daļu no Vācijas Jaunās Gvinejas un vācieši aktīvi ekspluatēja vietējos iedzīvotājus un resursus gan fosfātu ieguvei, gan kokosriekstu plantācijās. Sākoties Pirmajam pasaules karam, salas vāciešiem atņēma japāņi, kas tās paturēja līdz pat 1944. gadam, kad tās atkaroja amerikāņi. Amerikāņi bieži sev arī pārmet, ka Palau salās mira disproporcionāli daudz karavīru, ja rēķina uz to, cik Palau ir relatīvi stratēģiski nenozīmīgas. No 1947. gada Palau ar ANO mandātu pārvaldīja ASV. Valsts ieguva neatkarību no Amerikas Savienotajām Valstīm tikai 1994. gadā, kad parakstīja vienošanos ar Vašingtonu par finansiālās un tehniskās palīdzības saņemšanu apmaiņā pret ASV militāro bāzu atrašanos Palau teritorijā. Tajā pašā gadā Palau arī tika uzņemta ANO. Palau ir viena no tām nedaudzajām pasaules valstīm, kurai nav pašai savas armijas. Toties 2022. gadā tā piekrita izvietot savā teritorijā papildus vēl 100 miljonus eiro vērtu, modernu gaisa aizsardzības radaru sistēmu, kas spēj redzēt tālāk par horizontu. Pašai Palau ir tikai apmēram 30 cilvēku neliels krasta apsardzības dienests. Atgriežoties atpakaļ pie pirmatnējiem cilvēkiem, kuri dzīvoja Palau, ir vērts pieminēt, ka sarežģītās pārvaldības sistēmas centrā bija sievietes. Proti, Palau faktiski pastāvēja matriarhāts. Vēl mūsdienās Palau sabiedrības un politiskās dzīves centrā ir matrilineāra sistēma. Sievietes ir lēmumu pieņēmējas sabiedrībā un mātes līnija prevalē mantojuma, laulību, bēru un citās civiltiesiskajās attiecībās. Talibanam Afganistānā Palau noteikti šķiet kā elle zemes virs;u. Turklāt lielākā daļa Palau iedzīvotāju ir kristieši. Vietējās izcelsmes Modek-n-gei reliģijai pieder vien pieci procenti iedzīvotāju. Palau klasificējās kā valsts ar augstu ienākumu līmeni un tā skaitās augsti attīstīta valsts. Neskatoties uz to, ka Latvijas IKP uz vienu iedzīvotāju pēc pirktspējas paritātes ir apmēram 2,5 reizes lielāks nekā Palau. Cilvēku procentuālais skaits, kuri dzīvo zem nabadzības sliekšņa līmeņa, abās valstīs ir ļoti līdzīgs – apmēram ceturtā daļa cilvēku. Šo sociālekonomisko rādītāju esam bieži pieminējuši raidījumos, bet, veidojot stāstu par Palau, sapratām, ka nekad neesam šo detalizētāk izskaidrojuši. Tāpēc palūdzām to skaidrot Vitautam Kuokštim, Viļņas Universitātes asociētajam profesoram.

Oke, kami punya teori gelap soal drama Korea ini. NGGAK BISA BIASA AJA KARENA BANYAK YANG SUS!!!!!!! Akan ada beberapa episode Podcast ngedrakor! yang bahas Queen of Tears dan we thought it's gonna be fun to start everything with some DAAARRRRRKKK THEORIES. Queen of Tears diperankan oleh Kim Ji Won dan Kim Soo Hyun. Ini adalah proyek pertama mereka disatukan sebagai pasangan suami-istri. Dalam drama Korea Queen of Tears, Kim Ji Won memerankan karakter bernama Hong Hae In. Dia adalah pewaris kekayaan dari seorang konglomerat yang dilabeli sebagai ratu di Queens Group, sebuah pusat perbelanjaan. Sementara itu Kim Soo Hyun akan memerankan karakter bernama Baek Hyun Woo, anak kepala desa Yongduri yang punya label 'pangeran supermarket'. Hong Hae In dideskripsikan sebagai karakter anak orang kaya yang tidak pernah mau tunduk atau memberi hormat kepada siapapun. Pertemuannya dengan sosok Baek Hyun Woo yang amat sederhana menjadi tantangan tersendiri buatnya. Baek Hyun Woo di sisi lain tak hanya sederhana tapi juga bersahaja. Lulus dari sekolah hukum ternama dan dikaruniai wajah tampan, dia pun mencapai sukses dalam karier dan percintaan ketika menikahi Hong Hae In. Tiga tahun berjalan, pernikahan itu menghadapi sebuah krisis. Tapi pelan-pelan mereka bisa menghidupkan cinta mereka lagi. --- Podcast ngedrakor! dipersembahkan Dalam Ruang Produksi Studios, diproduseri bersama oleh Ron & Mal. Episode baru tayang Rabu setiap minggunya. Baca berita drama Korea favoritmu di ⁠⁠⁠detikpop.com⁠⁠⁠Follow Instagram kami di⁠⁠⁠ ⁠⁠@podcastngedrakor⁠⁠⁠⁠⁠ #PodcastNgedrakor #ngedrakordidetikcom #ngedrakordispotify --- Send in a voice message: https://podcasters.spotify.com/pod/show/ngedrakor/message

We get deep this week with friends of the show, Chewy and Oke. Both of these incredible men share their health struggles over the last few years and how it's changed their perspectives and approaches to life. Cuff Daddy also gets his own Bat Signal and American Pharaoh embarrasses himself over pager noises...who says we can't be serious and have fun?!?

The second part of our Cinemalaya 2023 episode is here! This time we're putting the focus on the other five films that we and our colleagues from the Society of Filipino Film Reviewers have reviewed! Babala: ang views and opinions ng bawat isa sa episode na ito ay STRICTLY their own. Hindi po ito nagrerepresenta kung anuman ang Third World Cinema Club. Oke? The five films tackled here are: Rookie Tether As If It's True Huling Palabas Bulawan Nga Usa (Golden Deer) You can also watch the live version of this through our Facebook page here: https://fb.watch/mKxHaMHBb3/ We'd like to thank our colleagues from the SFFR for joining us in this episode: Ronald Cruz, Nico Quejano, Jun Mendoza, ang suki ng TWCC na si Manuel Pangaruy, Jay-r Trinidad, at ang founder ng SFFR/Pinoy Rebyu na si Skilty Labastilla. Listen to this episode now and let us know what your thoughts are by tagging us on IG, Twitter, Tiktok, FB and many more! (Wala pa po kaming threads sorry). Magkikita kita ulit kami soon and magrerecord ng live! Dahil Third World kami, nagtitipid pa ng pang meet-up. We thank you for your utmost support.

The second part of our Cinemalaya 2023 episode is here! This time we're putting the focus on the other five films that we and our colleagues from the Society of Filipino Film Reviewers have reviewed! Babala: ang views and opinions ng bawat isa sa episode na ito ay STRICTLY their own. Hindi po ito nagrerepresenta kung anuman ang Third World Cinema Club. Oke? The five films tackled here are: Rookie Tether As If It's True Huling Palabas Bulawan Nga Usa (Golden Deer) You can also watch the live version of this through our Facebook page here: https://fb.watch/mKxHaMHBb3/ We'd like to thank our colleagues from the SFFR for joining us in this episode: Ronald Cruz, Nico Quejano, Jun Mendoza, ang suki ng TWCC na si Manuel Pangaruy, Jay-r Trinidad, at ang founder ng SFFR/Pinoy Rebyu na si Skilty Labastilla. Listen to this episode now and let us know what your thoughts are by tagging us on IG, Twitter, Tiktok, FB and many more! (Wala pa po kaming threads sorry). Magkikita kita ulit kami soon and magrerecord ng live! Dahil Third World kami, nagtitipid pa ng pang meet-up. We thank you for your utmost support.

Berikut adalah deskripsi asal sebagai bentuk alat uji untuk mengukur seberapa berpengaruh deskripsi episode podcast dengan jumlah engagement di social media. Mari kita coba. Oke, kita coba buka dengan resep dasar untuk membuat kue bolu warna-warni: Bahan-bahan: 250 gram tepung terigu 200 gram gula pasir 150 gram mentega atau margarin, lelehkan 4 butir telur 1 sendok teh baking powder 1 sendok teh vanili Sejumput garam Pewarna makanan (beberapa warna sesuai selera) 100 ml susu cair Langkah-langkah: Siapkan loyang bolu yang telah diolesi dengan margarin dan ditaburi sedikit tepung, atau Anda juga bisa menggunakan kertas roti di bagian dasar loyang untuk mencegah bolu lengket. Panaskan oven pada suhu 180 derajat Celsius. Ayak tepung terigu, baking powder, dan garam ke dalam sebuah wadah. Aduk rata dan sisihkan. Kocok telur dan gula pasir menggunakan mixer dengan kecepatan tinggi hingga mengembang dan berwarna putih pucat. Setelah itu, tambahkan lelehan mentega dan vanili ke dalam adonan telur, kocok kembali hingga rata. Turunkan kecepatan mixer, masukkan susu cair secara bertahap sambil terus dikocok hingga rata. Masukkan tepung terigu, baking powder, dan garam yang telah diayak ke dalam adonan. Aduk perlahan hingga semua bahan tercampur rata, tapi jangan terlalu lama mengaduknya. Bagi adonan menjadi beberapa bagian sesuai dengan jumlah warna yang ingin Anda gunakan. Tambahkan pewarna makanan ke masing-masing bagian adonan dan aduk hingga warna merata. Tuang adonan bergantian ke dalam loyang bolu yang telah disiapkan, buatlah motif atau pola sesuai dengan kreativitas Anda. Panggang kue bolu dalam oven yang sudah dipanaskan sebelumnya selama sekitar 25-30 menit atau hingga bagian atasnya kecokelatan dan ketika tusuk gigi dimasukkan ke tengah-tengah bolu, keluar bersih. Setelah matang, keluarkan kue bolu dari oven dan biarkan sedikit dingin di dalam loyang sebelum dikeluarkan. Kue bolu warna-warni siap disajikan! Anda bisa tambahkan hiasan atau saus sesuai selera. Selamat mencoba, semoga berhasil! #PodcastBercanda

In this episode, Tega 'The Gem King' Oke shares his experience and perspective on the cost of living crisis. The UK has been in a cost of living crisis for a few months now and our community has been concerned about how students and recent graduates are faring in our community and beyond. The Marketing communication strategist, Tega, uses humour, passion and practicality to share how we can all manage the current economic situation. From how he had to switch transportation modes for a more affordable one, to how he manages housing cost, bills and entertainment and what he can't give up even in the worst cost of living crisis. The point is, there's a lot to learn and apply. We hope you love this, and ask that you share with your friends too. Do send us messages as we would really love to hear your thoughts, ideas or questions because we do this for you and want you to be a part of the creation! If you haven't already, please sign up to join the Outliers Circle on https://ibukunogundipe.com/theoutlierscircle/ Follow us on: Instagram - @theoutlierscircle Twitter - @theoutlierscircle LinkedIn - @The Outliers Circle

Last week the Midstream Energy Infrastructure Conference (MEIC) held its annual event in Palm Beach, FL. SL Advisors partner Henry Hoffman was there and today's blog post recounts highlights reported by Henry.   Oneok's (OKE) proposed acquisition of Magellan Midstream (MMP) was a common topic, especially the unwelcome recapture of deferred taxes facing MMP. When a […]

An unintended side-effect of Oneok's (OKE) proposed acquisition of Magellan Midstream (MMP) has been to give a bid to smaller MLPs. This has come about because of the shrinking pool of names available to populate the Alerian MLP Infrastructure Index (AMZIX) and the Alerian MLP ETF (AMLP) which tracks it. AMZIX recently increased its maximum […]

Wall Street analysts are predisposed to be supportive of management's M&A activities.  The sycophantic posturing that precedes an earnings call question with, “Nice quarter, guys” lives in the hope of investment banking business. Hence the response of sell-side analysts to Oneok's (OKE) proposed acquisition of Magellan Midstream (MMP) is one of mild surprise at this […]

In this video, we'll perform an OKE stock analysis and figure out what the company looks like based on the numbers. We'll also try to figure out what a reasonable fair value is for ONEOK. And answer is OKE one of the best dividend stocks to buy at the current price? Find out in the video above! Global Value's ONEOK, Inc. stock analysis. Check out Seeking Alpha Premium and score an annual plan for just $119 - that's 50% off! Plus all funds from affiliate referrals go directly towards supporting the channel! Affiliate link - https://www.sahg6dtr.com/H4BHRJ/R74QP/ If you'd like to try Sharesight, please use my referral link to support the channel! https://www.sharesight.com/globalvalue (remember you get 4 months free if you sign up for an annual subscription!) ONEOK, Inc. ($OKE) | ONEOK, Inc. Stock Value Analysis | ONEOK, Inc. Stock Dividend Analysis | OKE Dividend Analysis | $OKE Dividend Analysis | ONEOK, Inc. Intrinsic Value | OKE Intrinsic Value | $OKE Intrinsic Value | ONEO Intrinsic Value (Recorded October 17, 2022) ❖ MUSIC ❖ ♪ "Lift" Artist: Andy Hu License: Creative Commons Attribution 3.0. ➢ http://creativecommons.org/licenses/b... ➢ https://www.youtube.com/watch?v=sQCuf...

On this episode of The Cloud Pod, the team discusses the new Amazon Linux 2023, Google Bard,  new features of Google Chronicle Security Operations, GPT-4 from Azure Open AI, and Oracle's Kubernetes platform comparison. They also talk about cloud-native architecture as a way to adapt applications for a pivot to the cloud. A big thanks to this week's sponsor, Foghorn Consulting, which provides full-stack cloud solutions with a focus on strategy, planning and execution for enterprises seeking to take advantage of the transformative capabilities of AWS, Google Cloud and Azure. This week's highlights

Ihr Bruder Oke ist ein echt blöder Hund, findet Tonka. Täglich fällt ihm etwas Neues ein, wie er sie ärgern kann. Nun verreisen ihre Eltern, die sonst den größten Unfug verhindern. Oke läuft zu Höchstform auf, er mischt Tonka giftgrüne Farbe ins Shampoo. Als sie einer Fee begegnet, verwandelt sich Oke in einen Dackel. Geplant war das nicht. Und nun? Alle 7 Folgen der OHRENBÄR-Hörgeschichte: Einmal Dackel und zurück von Janine Lüttmann. Es liest: Sandra Schwittau.

OKe guys, this episode is about inner conflict and how it actually torture us in our whole way of recovery and even before we start choosing recovery. In this episode, I will describe the process of how inner conflict exists in a person with a eating disorder, and what you can do about it. Follow @iamstuffed.nl

Wealth building isn't just about financial prosperity, but also about personal growth and making a difference in the world. Our guest today, Paul Dickson, is a prime example of someone who is living for something bigger. Paul is a father and the head of a charity called OKE, which provides Kiwi kids with the opportunity to learn life and social skills through productive gardens in schools. Read more here.To learn more or to volunteer time or money on a working bee, check out: https://oke.org.nz/working-bees/Hey! Can we have a little chat?If you're picking up what I'm putting down, help me build the Everyday Investor community!Spread the word: Write a review anywhere you can, share posts on social media, vote for Pedro! Follow me on YouTube, and if you can, subscribe on Spotify also. Use the following referral/affiliate links. In some cases with these codes, I may receive a financial benefit - in other cases I've waived any benefit so you can get a better deal.Hatch: $10 for you, and $10 for me, if you sign up and deposit $100NZD.Sharesies: $10 for you, and $10 for me, if you sign up for the first time.Easy Crypto: One of NZ's most trusted places to buy/sell your digital assets. Sharesight: Get 5 months free when you sign up to an annual (paid) subscription. CMC Markets: You and I both get $150 if you sign up using this link. *Note CFD's are incredibly high risk investment options(read more here)When you're reviewing your insurance plan or KiwiSaver, obtaining a mortgage or in need of financial advice, use Ungaro & Co Financial Services, the main partner of this podcast. Want to learn more about working with Darcy Ungaro, book in a free 15-min phone call - click on this link.Enough of the sales pitch, what else?1 - You're my inspiration! Most topics are inspired by YOUR questions or suggestions. So, what do want to hear? Ask me anything, suggest a topic!2 - Subscribe to YouTube to get earlier access, participate in live-recordings, and gain additional perspectives from Darcy Ungaro.3 - Sign up to the NZ Everyday Investor Newsletter! It's a newsletter, not a sales pitch: Sign up to our newsletter hereDisclaimer: Please act independent from any content...

Meredith Oke of the Quantum Biology Collective joined Sarah and Russ for a new year kick-off. Sarah and Meredith dive deep into the power of light. They talk food, treating depression with sunlight, barefoot walks outside boosting the immune system. Meredith also shares the power of the Quantum Biology Collective, pioneering health professionals who study, apply and explain the emerging field of quantum biology: a new paradigm of understanding how human health REALLY works that is light years beyond the current established medical model. Happy New Year with a happy new view about longevity and light health!DISCLAIMER: This podcast is for educational and informational purposes only and is solely intended as a self-help tool for your own use.

*Dialogue transcript* Hoa and Nhân are on the phone, and Nhan asks Hoa to go watch movie Nhân: Alo, Hoa à? Hoa: Alo, ai đấy? Nhân: Mình đây, mình là Nhân đây. Hoa: À, Nhân à, có việc gì thế? Nhân: Thứ bảy tuần này, cậu có bận không? Hoa: Có, mình bận rồi. Thứ bảy tuần này là sinh nhật chị gái mình. Nhân: Còn chủ nhật thì sao, cậu có rảnh không? Hoa: Chủ nhật mình chưa có kế hoạch, sao thế? Nhân: Chúng mình đi xem phim đi. Hoa: Có phim gì mới à? Nhân: Ừ, có phim mới hay lắm! Hoa: Thế thì, chủ nhật mình đi nhé. Nhân: Chúng ta đến quán cà phê, sau đó đi xem phim được không? Hoa: Được, mấy giờ thế? Nhân: Khoảng 2 giờ chiều nha. Hoa: Cậu đến nhà đón tớ nhé. Nhân: Oke, hẹn gặp cậu vào chủ nhật. Hoa: Nhất trí, bye nhé. Nhân: Ừ, bai bai. __________________________________ *New vocabulary* 1. Alo: hello (used when picking up phone) 2. thứ bảy: saturday 3. tuần này: this week 4. bận: to be busy 5. sinh nhật: birthday 6. chủ nhật: sunday 7. rảnh: to be available, to be free 8. kế hoạch: plan 9. sao thế?: what's going on?/ what's the matter 10. xem phim: to watch movies 11. phim mới: new movie 12. hay: good, interesting, great 13. chúng ta: we 14. quán cà phê: coffee shop 15. sau đó: then 16. được: to agree 17. đón: to pick up 18. nhất trí: agree __________________________________ Levion - Learn Vietnamese Online Email: xinchao@levion.vn Website: www.levion.vn (coming soon) IG: @levion.vietnamese FB: Levion - Learn Vietnamese Online

*This episode is part of a series highlighting stories in Albemarle, NC*Shawn Oke is a third generation firefighter who began his fire service career at the age of fourteen as a junior firefighter in Union County, NC and in 2019 he retired from the City of Albemarle as Fire Chief. In April 2000, Shawn purchased the Albemarle Sweet Shop, a scratch bakery located in Albemarle, North Carolina.  The Albemarle Sweet Shop has been located in downtown Albemarle since 1922.  Since retiring from the fire service in June 2019 and focusing on the operations of the bakery the business has seen double digit growth each year outside of the pandemic year.  In October 2022, Oke and his family broke ground on a $2 million dollar building to relocate the Albemarle Sweet Shop. https://www.albemarlesweetshop.com/https://www.instagram.com/albemarlesweetshop/https://www.facebook.com/albemarlesweetshophttps://twitter.com/albeSweetShop

"The stock market outlook appears to be short covering. The stock market is headed for a recession if the Fed keeps tightening and inflation remains elevated. Investors will continue to see big risks until the Federal Reserve says risks have lessened. Berkshire Hathaway added $44B net in public equity this year," says James Locke. Locke provides his stock picks: CSCO, GSK, OKE, and OMC.

It's the show's 2 year anniversary! This episode brings Reggie, Jason, and Oke all together to answer listener questions and run wildly off topic about things like cereal and what flavor of pie is best while... Grab hold of that shower head and hang on for another year of normalizing kinks and fetishes!

D.L. interviews Daniel Silliman about the Christian romance novel that started it all—Love Comes Softly.  We talk about Oke's Canadian background and how that plays into her writing, as well as the impact her books have had on Christian women and the Christian romance genre as a whole. Daniel is a news editor for Christianity Today and author of Reading Evangelicals. You can follow him on Twitter @danielsilliman Here is an interview with Janette Oke This article on Active History explores how Janette Oke romanticizes the Mounties You can check out this detailed report from the Royal Canadian Mounted Police on their role in the Indian residential school system “I was born on the Canadian prairie. I was actually born at home. This sounds really like old, old west. I was born in a little log house. The doctor came out to our place to deliver me. So it sounds really, really old fashioned. I went to a one room country school. So a lot of what I write, it's very much a part of my background–as a teenager, and even younger than that, I was very into the west and the pioneer days. So I read everything I could find on the pioneers. I felt they were a very hearty group of people with a lot of bravery to come out and start making a life on a new frontier. Our Canadian west opened up quite a bit different than the stories that I was reading, which were basically westerns from the U.S. side of the border, in that we had the Northwest Mounted Police—they were at that time—and basically precede the settlers.” “We never had the cowboy and Indian skirmishes and the unsettled west for them to come in. We never had sheriffs in Canada. We have had what is now the RCMP, the Royal Canadian Mounted Police and so our pioneers came out to a rather settled area as far as the laws were concerned and oftentimes there were groups of people that sort of came together from a united background, and if you look at our small town around our area and find the oldest church you can pretty well say, ‘Well, that group of settlers came from Germany', ‘That group of settlers came from Sweden', you know. By the oldest church there you can pretty well identify it, so these people came west with deep, personal faith. That changed the whole color of how our west was settled.” We have a website—check it out for more information. You can also find us on Twitter and Instagram. To support our show (we can't do this without you!), join us on Patreon! You'll get access to our monthly patron-only episodes (including the entire backlog), as well as occasional zoom hangouts. You can join this community for as little as $1.50 a month! Cover art by Zech Bard.