Umapped

umapped

In 2020, I authored an article on LinkedIn titled "Welcome to Edge Territory." (Welcome to Edge Territory – the Hidden Space Between Networks | LinkedIn) The blog was intended to start a series exploring the complexities of edge computing. The idea still intrigues me, and I am considering revisiting it—perhaps as a podcast series. One of the more startling insights from that blog was the projected $10 trillion in damages by 2025, a figure we are now on track to exceed by the end of 2024. Despite $300 billion being spent a year on prevention, this exponential growth in damage continues to outpace our efforts. I defined "edge territory" as "the unmapped space beyond the network edge between environments, where secured and unsecured networks and devices collide." I still find that definition fitting, though I would add that we continually discover new edges beyond what was previously understood. These evolving threats extend beyond manageable devices to unmanaged IoT and edge scenarios in cloud and data center deployments. So, the critical question becomes: Where can I find the edge? The edge is everywhere, constantly shifting based on how we use new computing concepts and remain productive in our daily lives, individually and organizationally. This dynamic presents a challenge that I highlighted in that earlier blog. The seen and unseen spaces at the edge invite us to cooperate more closely as a community and marketplace. I am thrilled to collaborate with other leaders working tirelessly to provide solutions for visibility and response in edge scenarios. Both attackers and defenders are keenly aware of how vulnerable we are. Since 2020, the number of known exploits has grown exponentially. The challenge posed by bounties and threat hunting has been met with increasingly sophisticated tools, making discovery more effective for attackers and cybersecurity teams. One article noted that quarterly disclosed additions to the Common Vulnerabilities and Exposures (CVE) database surged from 8,051 in 2021 to 26,447 in 2022—a staggering 320% year-over-year increase. By January 2024, the CVE database had reached 176,000 entries; as I write this, the number surpassed 240,000. What stands out about the edge is how exponential growth is clear across the board: in losses, spending, and the number of identified vulnerabilities. Addressing cybersecurity at the edge requires finding the necessary solutions for visibility and response. I want to take a moment to acknowledge and express gratitude to the many vendors, service providers, and companies on the front lines of what can only be described as a war zone in edge territory. A comprehensive approach to edge security might involve intrusion detection systems, Security Operations Centers (SOCs), firewalls, security system management, endpoint management solutions, log management solutions, event management solutions, and strategies for decreasing time for responding to an event that is detected by a tool or professional. I also want to highlight the incredible leaders and solutions in the Extended Detection and Response (XDR) space. They focus on device vulnerabilities and work diligently to reduce the meantime to detect and contain threats, using AI and other advanced technologies. For those on the front lines, I hope to bring more awareness to the sheer volume of activity and effort needed to stay ahead of the identified exploits that threaten organizations and individuals. Malicious actors' use of AI or Machine Learning Models (MLLs) is a growing concern, underscoring that edge territory is constantly evolving. A comprehensive approach to edge cybersecurity should begin with network awareness and extend to every connected device. This is a daunting challenge, as most organizations struggle to gather the necessary tools and ability to optimize awareness and response. Recent reports, such as one from Google’s Mandiant, show that the average dwell time—the time it takes to detect a cyber intrusion—has dropped to a record low of 2.24 months. As we continue to navigate edge territory, we, as a community, are working together more effectively to observe, identify, protect, and respond. This collective effort can potentially reduce the exponential growth of damage and chart a different course for the future. Recent reports, like Sophos' 2024 State of Ransomware in Healthcare, highlight the rapid increase in attacks on healthcare organizations, with incidents rising from 34% in 2021 to 67% in 2024. These statistics serve as a stark reminder that edge territory is expanding and becoming increasingly dangerous. Combined attack vectors or surface information offers a holistic view of edge territory. At the network level, monitoring vulnerabilities and traffic allows for responses. At the device level, observability from the network through the application and data layers covers every aspect of edge territory. One reason the Edge continues to evolve, and grow is the expansion of connected services and digital assets. As one analyst from Silicon Angle recently noted, "The edge is now space." I am excited to join my team in applying AI more holistically across edge-to-edge scenarios, offering greater visibility and empowering organizations to respond faster than ever with more connected analytics. With our DCX Offering, we have extended our awareness edge-to-edge and now provide automated detection and containment through isolation. This adds value to any existing solution, creating unprecedented metrics for success, with over 240,000 incidents detected and contained last year alone. We are proud to collaborate with writers and industry experts to provide our partners, vendors, and industry leaders with improved awareness of edge territory making the undefinable visible and approachable for any organization.                                                                   Follow Our Blog & News https://guarddog.ai/news/ In 2020, I authored an article on LinkedIn titled "Welcome to Edge Territory." ( Welcome to Edge Territory – the Hidden Space Between Networks | LinkedIn ) The blog was intended to start a series exploring the complexities of edge computing. The idea still intrigues me, and I am considering revisiting it—perhaps as a podcast series. Welcome to Edge Territory – the Hidden Space Between Networks | LinkedIn One of the more startling insights from that blog was the projected $10 trillion in damages by 2025, a figure we are now on track to exceed by the end of 2024. Despite $300 billion being spent a year on prevention, this exponential growth in damage continues to outpace our efforts. I defined "edge territory" as "the unmapped space beyond the network edge between environments, where secured and unsecured networks and devices collide." I still find that definition fitting, though I would add that we continually discover new edges beyond what was previously understood. These evolving threats extend beyond manageable devices to unmanaged IoT and edge scenarios in cloud and data center deployments. So, the critical question becomes: Where can I find the edge? The edge is everywhere, constantly shifting based on how we use new computing concepts and remain productive in our daily lives, individually and organizationally. This dynamic presents a challenge that I highlighted in that earlier blog. The seen and unseen spaces at the edge invite us to cooperate more closely as a community and marketplace. I am thrilled to collaborate with other leaders working tirelessly to provide solutions for visibility and response in edge scenarios. Both attackers and defenders are keenly aware of how vulnerable we are. Since 2020, the number of known exploits has grown exponentially. The challenge posed by bounties and threat hunting has been met with increasingly sophisticated tools, making discovery more effective for attackers and cybersecurity teams. One article noted that quarterly disclosed additions to the Common Vulnerabilities and Exposures (CVE) database surged from 8,051 in 2021 to 26,447 in 2022—a staggering 320% year-over-year increase. By January 2024, the CVE database had reached 176,000 entries; as I write this, the number surpassed 240,000. What stands out about the edge is how exponential growth is clear across the board: in losses, spending, and the number of identified vulnerabilities. Addressing cybersecurity at the edge requires finding the necessary solutions for visibility and response. I want to take a moment to acknowledge and express gratitude to the many vendors, service providers, and companies on the front lines of what can only be described as a war zone in edge territory. A comprehensive approach to edge security might involve intrusion detection systems, Security Operations Centers (SOCs), firewalls, security system management, endpoint management solutions, log management solutions, event management solutions, and strategies for decreasing time for responding to an event that is detected by a tool or professional. I also want to highlight the incredible leaders and solutions in the Extended Detection and Response (XDR) space. They focus on device vulnerabilities and work diligently to reduce the meantime to detect and contain threats, using AI and other advanced technologies. For those on the front lines, I hope to bring more awareness to the sheer volume of activity and effort needed to stay ahead of the identified exploits that threaten organizations and individuals. Malicious actors' use of AI or Machine Learning Models (MLLs) is a growing concern, underscoring that edge territory is constantly evolving. A comprehensive approach to edge cybersecurity should begin with network awareness and extend to every connected device. This is a daunting challenge, as most organizations struggle to gather the necessary tools and ability to optimize awareness and response. Recent reports, such as one from Google’s Mandiant, show that the average dwell time—the time it takes to detect a cyber intrusion—has dropped to a record low of 2.24 months. As we continue to navigate edge territory, we, as a community, are working together more effectively to observe, identify, protect, and respond. This collective effort can potentially reduce the exponential growth of damage and chart a different course for the future. Recent reports, like Sophos' 2024 State of Ransomware in Healthcare, highlight the rapid increase in attacks on healthcare organizations, with incidents rising from 34% in 2021 to 67% in 2024. These statistics serve as a stark reminder that edge territory is expanding and becoming increasingly dangerous. Combined attack vectors or surface information offers a holistic view of edge territory. At the network level, monitoring vulnerabilities and traffic allows for responses. At the device level, observability from the network through the application and data layers covers every aspect of edge territory. One reason the Edge continues to evolve, and grow is the expansion of connected services and digital assets. As one analyst from Silicon Angle recently noted, "The edge is now space." I am excited to join my team in applying AI more holistically across edge-to-edge scenarios, offering greater visibility and empowering organizations to respond faster than ever with more connected analytics. With our DCX Offering, we have extended our awareness edge-to-edge and now provide automated detection and containment through isolation. This adds value to any existing solution, creating unprecedented metrics for success, with over 240,000 incidents detected and contained last year alone. We are proud to collaborate with writers and industry experts to provide our partners, vendors, and industry leaders with improved awareness of edge territory making the undefinable visible and approachable for any organization.                                                                   Follow Our Blog & News https://guarddog.ai/news/ https://guarddog.ai/news/

The Edge: How Do I Know I’ve Found It?

প্রান্ত: আমি কিভাবে জানব যে আমি এটি খুঁজে পেয়েছি?

The Edge: Woher weiß ich, dass ich es gefunden habe?

The Edge: ¿Cómo sé que lo he encontrado?

The Edge : Comment savoir si je l’ai trouvé ?

किनारा: मैं कैसे जानूँ कि मैंने उसे पा लिया है?

エッジ: 見つけたかどうかはどうすればわかるのでしょうか?

The Edge: 찾았는지 어떻게 알 수 있을까?

The Edge: Como sei que o encontrei?

Грань: как я узнаю, что нашел ее?

The Edge: Onu Bulduğumu Nasıl Anlarım?

The Edge: Làm sao tôi biết mình đã tìm thấy nó?

边缘：我怎么知道我找到了它？

How to Use Terraform to Configure AWS Verified Access With an OIDC Google Provider

Hi All! Here is my weekly wrap up email. If you love this content (please share it), but also… Check out my , connect with me on / , and Podcast YouTube Twitter Subscribe to my weekly newsletter Join our free slack community What’s in today’s newsletter? The Map Is Not the Territory Idea: Intelligence vs. Wisdom Question: Useful Learning Quote: Liz Elting, Bob Meers, Chris Smith, Why AI Can’t Replace You Podcast: How I Got Into And Managed to Walk Away from Burnout Article: Idea: The Map Is Not the Territory Ever tried navigating a bustling city with a map from the 1980s? Turns out, the city is the same, but the map has changed. , a bustling locale in New York, changed hands three times in a decade. On paper, every owner was a savvy entrepreneur. Yet, two of them failed, one succeeded wildly. The difference? Their perception of the territory. John’s Coffee Shop : Every business operates with models. Forecasts. Predictions. Templates. Maps. But, as Alfred Korzybski reminded us, "the map is not the territory." Fact John's first owner, a techie, automated everything. He trusted algorithms to dictate coffee preferences, manage inventory, and even select music. : technology-driven efficiency equals success. His map The second owner went retro. Vintage furniture. Manual registers. A return to the "good old days." : people long for nostalgia. His map The third, a young barista-turned-owner, constantly interacted with customers. She tweaked the menu based on conversations, adjusted seating arrangements from observations, and kept a flexible approach. : listen, adapt, and evolve. Her map Two static maps. One dynamic terrain. Guess who thrived? Our businesses, like cities, are dynamic, ever-changing. But we, time and again, clutch outdated maps thinking they'll guide us. didn’t dominate by following the traditional auto industry's map. They redrew it. Tesla didn’t rise by mimicking Blockbuster. They envisioned a new landscape. Netflix Yet, countless businesses cling to their maps. After all, it's reassuring to follow a blueprint. But what if that blueprint is outdated or just plain wrong? Best nautical map of its time. Top-notch navigation tools. But, it wasn’t the map that failed; it was the iceberg not on it. A dynamic, unforeseen component of the territory. Consider the Titanic. So, how do we operate in a world where our business maps might be leading us astray? : Every map has blind spots. Anticipate them. Embrace Uncertainty : The world changes. Regularly revisit and revise your maps. Stay Curious : Get out there. Feel the ground. Talk to people. Real-time feedback trumps theoretical models. Interact with the Terrain They had a map. A good one. But when the terrain changed with the rise of digital streaming, their map became obsolete. Remember Blockbuster’s decline? Conversely, , under Jobs, was known to pivot on a dime. iPod's success? iPhone’s creation? Responses to a changing territory. Apple Lastly, a nod to , the author who’s talked extensively about "Black Swan" events. Events so rare, so unpredictable, they’re not on anyone’s map. Yet, they shape terrains. Nassim Taleb Businesses that thrive, Taleb argues, aren’t those with the best maps, but those most adaptable when off the map. So, as you chart your business journey, remember: Your map is a guide, not gospel. The real magic happens when you dare to traverse the unmapped, the unpredictable, the unknown. Because in the end, it's not about having the best map, but being the best explorer. Question: Intelligence vs. Wisdom What Is The Difference Between Intelligence & Wisdom? It is often measured by tests, such as , that assess logical, verbal, and mathematical skills. Intelligence can help you solve problems, learn new things, and perform tasks. Intelligence is the ability to acquire, process, and apply information. IQ It is often gained by observation, reflection, and practice. Wisdom can help you understand yourself, others, and the world. Wisdom is the ability to use knowledge and experience to make sound judgments. A few places to start. Intelligence is based on the functions of the brain, such as memory, reasoning, and perception. Wisdom, on the other hand, is based on the insights of the mind, such as . The Cognitive Perspective. intuition, empathy, and morality Intelligence is influenced by the genes, environment, and education of the individual. Wisdom is influenced by the age, culture, and values of the individual. The Developmental Perspective. Intelligence is useful for achieving goals, creating innovations, and advancing knowledge. Wisdom is useful for avoiding mistakes, making decisions, and finding meaning. The Practical Perspective. It's in the balance where you really thrive. They can support each other and enhance each other's value. Intelligence and wisdom are not mutually exclusive. So, don't just be smart. Because Be wise. intelligence without wisdom can be dangerous. Quote: Useful Learning - Dr. Barbara Oakley “It’s not what you know that matters. What matters is how well you can use what you know when you need it. In other words, it’s not the knowledge you have crammed into your head that’s important; it’s the knowledge that you can access and use when you need it.” It’s not what you know. It’s what you do with that knowledge. Seek growth & continual learning, not perfection (because perfection doesn’t exist). Take knowledge, make it relevant, make it applicable. Do something with it. ( ) Share On Twitter Podcast: Liz Elting, Bob Meers, Chris Smith, Why AI Can’t Replace You 1. Liz Elting - CEO at Elizabeth Elting Foundation | | YouTube Spotify Apple Liz Elting is a distinguished entrepreneur, philanthropist, and business leader, known for her remarkable journey that spans five countries. In 1992, she founded TransPerfect from an NYU dorm room, growing it into the world's largest language solutions company with over $1.1 billion in revenue and a presence in 100+ cities. She is a celebrated advocate for women's empowerment and a sought-after speaker, with her book, "Dream Big and Win: Translating Passion into Purpose and Creating a Billion-Dollar Business," poised to inspire others to follow in her footsteps. Recognized as one of Forbes' Richest Self-Made Women, Liz Elting continues to shape the business landscape with her passion and dedication. 2. Bob Meers - Ex-CEO at Reebok & LuLulemon, CEO at Better for All | | YouTube Spotify Apple Bob Meers is a highly accomplished CEO with a history of leading several prominent companies (LuLulemon, Reebok). Currently at the helm of Better for All, a unique line of PHBH home compostable bioplastic cups championing environmental sustainability, Bob brings a wealth of leadership experience to the organization. Previously, Meers served as CEO of Lululemon Athletica, Inc., from December 2005 to June 2008, taking a small yoga apparel business to a billion-dollar international public enterprise. Before that, Meers served as President & CEO of Reebok. During Meers’ 15-year tenure at Reebok, the company grew from $13 million to $3.5 billion in sales. 3. Chris Smith - Co-Founder of Curaytor | The Conversion Code | | YouTube Spotify Apple Chris Smith is the Co-Founder of Curaytor (an Inc. 500 fastest-growing business) and he was named top 4 best marketers under 40, according to the American Marketing Association. His book, The Conversion Code, is taught at colleges like Johns Hopkins University and he has been a guest lecturer at NYU. Chris used the blueprint in this book to quickly grow his company to eight figures in annual recurring revenue, without raising any venture capital. His work has been featured in AdWeek, Forbes, Fortune, and many other publications. 4. Why AI Can't Replace You | | YouTube Spotify Apple In this Lessons episode, we explore the unique value of human creativity and how to cultivate and maintain it in the age of rapid AI advancement. I'll discuss how the world is rapidly evolving, with AI taking over roles traditionally held by humans. But where does human ingenuity fit in this landscape? I’ll also discuss the unique attributes humans possess - our capacity to empathize, innovate, and imagine, which even the most advanced AI cannot replicate. How I Got Into And Managed to Walk Away from Burnout Article: Everyone is an advocate of not over-working. But we all fall into burnout. How does this happen? What do we do to get out of it? Well, here’s an article that gives us an answer. Read it here. My Links Success Story (Top 10 Business Podcast) Newsletter (321k Subs) Social Media Also published . here

It's Not About Having the Best Map, but Being the Best Explorer

এটি সেরা মানচিত্র থাকার বিষয়ে নয়, সেরা এক্সপ্লোরার হওয়ার বিষয়ে

Es geht nicht darum, die beste Karte zu haben, sondern darum, der beste Entdecker zu sein

No se trata de tener el mejor mapa, sino de ser el mejor explorador

Il ne s'agit pas d'avoir la meilleure carte, mais d'être le meilleur explorateur

यह सर्वश्रेष्ठ मानचित्र होने के बारे में नहीं है, बल्कि सर्वश्रेष्ठ एक्सप्लोरर होने के बारे में है

重要なのは最高の地図を持っていることではなく、最高の探検家であることです

최고의 지도를 갖는 것이 아니라 최고의 탐험가가 되는 것

Não se trata de ter o melhor mapa, mas de ser o melhor explorador

Дело не в лучшей карте, а в том, чтобы быть лучшим исследователем

Önemli olan En İyi Haritaya Sahip Olmak Değil, En İyi Kaşif Olmaktır

Vấn đề không phải là có bản đồ tốt nhất mà là trở thành nhà thám hiểm giỏi nhất

不是拥有最好的地图，而是成为最好的探险家

The Corner Pub.

Tarzan the Terrible by Edgar Rice Burroughs, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . Home Home Within an hour of the fall of Lu-don and Mo-sar, the chiefs and principal warriors of Pal-ul-don gathered in the great throneroom of the palace at A-lur upon the steps of the lofty pyramid and placing Ja-don at the apex proclaimed him king. Upon one side of the old chieftain stood Tarzan of the Apes, and upon the other Korak, the Killer, worthy son of the mighty ape-man. And when the brief ceremony was over and the warriors with upraised clubs had sworn fealty to their new ruler, Ja-don dispatched a trusted company to fetch O-lo-a and Pan-at-lee and the women of his own household from Ja-lur. And then the warriors discussed the future of Pal-ul-don and the question arose as to the administration of the temples and the fate of the priests, who practically without exception had been disloyal to the government of the king, seeking always only their own power and comfort and aggrandizement. And then it was that Ja-don turned to Tarzan. "Let the Dor-ul-Otho transmit to his people the wishes of his father," he said. "Your problem is a simple one," said the ape-man, "if you but wish to do that which shall be pleasing in the eyes of God. Your priests, to increase their power, have taught you that Jad-ben-Otho is a cruel god, that his eyes love to dwell upon blood and upon suffering. But the falsity of their teachings has been demonstrated to you today in the utter defeat of the priesthood. "Take then the temples from the men and give them instead to the women that they may be administered in kindness and charity and love. Wash the blood from your eastern altar and drain forever the water from the western. "Once I gave Lu-don the opportunity to do these things but he ignored my commands, and again is the corridor of sacrifice filled with its victims. Liberate these from every temple in Pal-ul-don. Bring offerings of such gifts as your people like and place them upon the altars of your god. And there he will bless them and the priestesses of Jad-ben-Otho can distribute them among those who need them most." As he ceased speaking a murmur of evident approval ran through the throng. Long had they been weary of the avarice and cruelty of the priests and now that authority had come from a high source with a feasible plan for ridding themselves of the old religious order without necessitating any change in the faith of the people they welcomed it. "And the priests," cried one. "We shall put them to death upon their own altars if it pleases the Dor-ul-Otho to give the word." "No," cried Tarzan. "Let no more blood be spilled. Give them their freedom and the right to take up such occupations as they choose." That night a great feast was spread in the pal-e-don-so and for the first time in the history of ancient Pal-ul-don black warriors sat in peace and friendship with white. And a pact was sealed between Ja-don and Om-at that would ever make his tribe and the Ho-don allies and friends. It was here that Tarzan learned the cause of Ta-den's failure to attack at the stipulated time. A messenger had come from Ja-don carrying instructions to delay the attack until noon, nor had they discovered until almost too late that the messenger was a disguised priest of Lu-don. And they had put him to death and scaled the walls and come to the inner temple court with not a moment to spare. The following day O-lo-a and Pan-at-lee and the women of Ja-don's family arrived at the palace at A-lur and in the great throneroom Ta-den and O-lo-a were wed, and Om-at and Pan-at-lee. For a week Tarzan and Jane and Korak remained the guests of Ja-don, as did Om-at and his black warriors. And then the ape-man announced that he would depart from Pal-ul-don. Hazy in the minds of their hosts was the location of heaven and equally so the means by which the gods traveled between their celestial homes and the haunts of men and so no questionings arose when it was found that the Dor-ul-Otho with his mate and son would travel overland across the mountains and out of Pal-ul-don toward the north. They went by way of the Kor-ul-JA accompanied by the warriors of that tribe and a great contingent of Ho-don warriors under Ta-den. The king and many warriors and a multitude of people accompanied them beyond the limits of A-lur and after they had bid them good-bye and Tarzan had invoked the blessings of God upon them the three Europeans saw their simple, loyal friends prostrate in the dust behind them until the cavalcade had wound out of the city and disappeared among the trees of the nearby forest. They rested for a day among the Kor-ul-JA while Jane investigated the ancient caves of these strange people and then they moved on, avoiding the rugged shoulder of Pastar-ul-ved and winding down the opposite slope toward the great morass. They moved in comfort and in safety, surrounded by their escort of Ho-don and Waz-don. In the minds of many there was doubtless a question as to how the three would cross the great morass but least of all was Tarzan worried by the problem. In the course of his life he had been confronted by many obstacles only to learn that he who will may always pass. In his mind lurked an easy solution of the passage but it was one which depended wholly upon chance. It was the morning of the last day that, as they were breaking camp to take up the march, a deep bellow thundered from a nearby grove. The ape-man smiled. The chance had come. Fittingly then would the Dor-ul-Otho and his mate and their son depart from unmapped Pal-ul-don. He still carried the spear that Jane had made, which he had prized so highly because it was her handiwork that he had caused a search to be made for it through the temple in A-lur after his release, and it had been found and brought to him. He had told her laughingly that it should have the place of honor above their hearth as the ancient flintlock of her Puritan grandsire had held a similar place of honor above the fireplace of Professor Porter, her father. At the sound of the bellowing the Ho-don warriors, some of whom had accompanied Tarzan from Ja-don's camp to Ja-lur, looked questioningly at the ape-man while Om-at's Waz-don looked for trees, since the GRYF was the one creature of Pal-ul-don which might not be safely encountered even by a great multitude of warriors. Its tough, armored hide was impregnable to their knife thrusts while their thrown clubs rattled from it as futilely as if hurled at the rocky shoulder of Pastar-ul-ved. "Wait," said the ape-man, and with his spear in hand he advanced toward the GRYF, voicing the weird cry of the Tor-o-don. The bellowing ceased and turned to low rumblings and presently the huge beast appeared. What followed was but a repetition of the ape-man's previous experience with these huge and ferocious creatures. And so it was that Jane and Korak and Tarzan rode through the morass that hems Pal-ul-don, upon the back of a prehistoric triceratops while the lesser reptiles of the swamp fled hissing in terror. Upon the opposite shore they turned and called back their farewells to Ta-den and Om-at and the brave warriors they had learned to admire and respect. And then Tarzan urged their titanic mount onward toward the north, abandoning him only when he was assured that the Waz-don and the Ho-don had had time to reach a point of comparative safety among the craggy ravines of the foothills. Turning the beast's head again toward Pal-ul-don the three dismounted and a sharp blow upon the thick hide sent the creature lumbering majestically back in the direction of its native haunts. For a time they stood looking back upon the land they had just quit—the land of Tor-o-don and GRYF; of JA and JATO; of Waz-don and Ho-don; a primitive land of terror and sudden death and peace and beauty; a land that they all had learned to love. And then they turned once more toward the north and with light hearts and brave hearts took up their long journey toward the land that is best of all—home. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Edgar Rice Burroughs (2020). Tarzan the Terrible. Urbana, Illinois: Project Gutenberg. Retrieved October 2022 https://www.gutenberg.org/cache/epub/2020/pg2020-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org , located at https://www.gutenberg.org/policy/license.html .

The chiefs and principal warriors of Pal-ul-don gathered in the great throneroom

With DevOps and Continuous Delivery gaining traction, one might ask whether the principles behind Lean and Agile are still relevant. How do they compare to the 5 Continuous Delivery principles, and what do any differences mean for software development teams? The beginnings of lightweight software delivery Throughout the 1990s, a revolution was brewing in the software development industry. The early phased models divided the delivery process into skill-based steps, with designs and documents used to run approval processes to control a project. The process for delivering software was heavyweight and slow, with little indication that the overheads reduced the risks they tried to mitigate. A collection of lightweight methods emerged, designed to generate fast feedback and iteratively adapt the plan based on new information. Rather than controls and approvals, developers used small batches to manage the risk and provide frequent opportunities to change direction. The Agile Manifesto emerged from this adaptive and lightweight methods community in 2001, with Lean Software Development arriving a couple of years later. Agile and Lean provided a -based approach to software development. You could test whether an approach was Agile or Lean by testing it against a set of core statements defining each method's philosophy. values and principles Continuous Delivery emerged from the Lean and Agile communities, providing the most concrete practices and capabilities to achieve frequent and safe software delivery. Apart from Extreme Programming, most software development methods deal with requirements management and communication structures. Continuous Delivery takes on the rest of the value stream and provides a pathway to an efficient and reliable delivery pipeline. InfoQ publishes an annual report on software development culture and methods. They style the report after Geoffrey Moore's concept. Moore famously visualizes a technology adoption lifecycle as a bell curve spread across 3 standard deviations. Crossing the Chasm The chart is divided into 5 groups with different attitudes to new technology: Innovators (-3) Early adopters (-2) Early majority (-1) Late majority (+1) Laggards (+3) The early majority and late majority represent two-thirds of the adoption lifecycle. Still, for new technology (or, in the case of InfoQ, a new idea) to move into the majority, it must cross the chasm from the early adopters to the mainstream majorities. While adaptive modes of software delivery are embedded in the late majority, the capabilities needed for continuous modes of delivery are still making their way across the chasm. Some practices (such as DevSecOps) have made the leap, while other key elements, like team topologies and empowered teams, remain at the early adopter stage. So, with DevOps and Continuous Delivery gaining traction, it's a great time to compare the 5 principles of Continuous Delivery with the 12 Agile principles and the 7 Lean principles. Comparing Agile, Lean, and Continuous Delivery principles Agile, Lean, and Continuous Delivery each provide a set of principles. This helps us compare their fundamental structures. There are other techniques and capabilities in Lean and Continuous Delivery that don't have comparable elements in Agile. The Agile Manifesto was intended to be a broad litmus test of the agility of other specific methods, such as Extreme Programming, Scrum, and Disciplined Agile, so it didn't define further details. Lean expands on its principles by describing techniques covering the whole software development process with advice on planning, design, testing, and maintenance. Continuous Delivery uses the deployment pipeline to focus efforts on improving the flow of change, from the code commit to the software running in production. Specific technical capabilities are described in detail to enable the . early and continuous delivery of valuable software The principles are the only directly comparable elements of these 3 approaches. Continuous Delivery principles There are 5 principles of Continuous Delivery: Build quality in Work in small batches Computers perform repetitive tasks, and people solve problems Relentlessly pursue continuous improvement Everyone is responsible The principles can be arranged into a reinforcing relationship, where the first 3 principles act as drivers of continuous improvement, for which everyone involved is responsible. Agile principles comparison In general, Continuous Delivery principles are consistent with . The Agile Manifesto For example, working in small batches is widely understood to help achieve several of the Agile principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Simplicity - the art of maximizing the amount of work not done - is essential. The phrasing of the principle "work in small batches" is concise and easy to follow in practice. This Continuous Delivery principle contributes to the attainment of half of the Agile principles. There is also an amplification effect when you combine the 5 principles. To "deliver working software frequently", you need to work in small batches, increase automation, and build quality in. Two Agile principles are not covered by Continuous Delivery: Business people and developers must work together daily throughout the project. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Continuous Delivery is centered on the delivery pipeline, which means the process of identification, inception, and initiation aren't a direct concern of Continuous Delivery. Additionally, in the front matter of the book, the authors highlight that the book was created according to the ideas it contained. The contributors and editors worked using different tools and from separate locations. They used version control and automated builds to form a delivery pipeline for the book. They didn't work together daily or convey information face-to-face. Continuous Delivery As an industry, many organizations that hadn't attempted to work remotely are now ready to experiment with distributed working. This will further challenge the need for real-time face-to-face coordination as asynchronous communication becomes more common and familiar. Regarding word counts, Continuous Delivery principles are conveyed in 21 words, rather than 180 words for Agile principles. A combination of hindsight and incisive editing has given us a compass to check our direction, with the detail provided in the specific practices of Continuous Delivery. It's easy to get bogged down in the details of implementing Continuous Delivery — tools, architecture, practices, politics — if you find yourself lost, try revisiting these principles and you may find it helps you re-focus on what's important." — Jez Humble You don't have to throw out The Agile Manifesto to move forwards; it's part of the geography that Continuous Delivery and DevOps are building on. The industry will continue to discover new and better ways of developing software. It's increasingly evident that technical practices and cultural capabilities are vital. Lean principles comparison The Lean principles are already brief and actionable. There's complete alignment between Lean and Continuous Delivery, with no unmapped areas. With Agile, Continuous Delivery offered a concise alternative to 10 Agile principles. In the case of Lean, Continuous Delivery aligns entirely with the principles. Each approach provides a different perspective that applies to various organization segments. In an organization that has fully adopted both Lean and Continuous Delivery, the respective principles are helpful to different groups. Lean principles and techniques are leadership tools, while Continuous Delivery provides an approach specific to the individual contributors' delivery efforts. For example, automation is a practical attack vector for eliminating waste, delivering quickly, and building integrity into the system with Continuous Delivery. Conclusion Continuous Delivery provides a concise set of principles that align with 10 of the 12 Agile principles and complement Lean, providing a different perspective on achieving similar goals. All 3 sets of principles are consistent with modern management philosophy and provide different ways to review and re-focus your software delivery efforts. You can use the Continuous Delivery principles to guide your software delivery efforts and refer back to Agile and Lean principles to find further inspiration for your improvement efforts. Also published here.

A Comparison of Agile, Lean, and Continuous Delivery

When you run any C-program, its executable image loaded into RAM of computer in an organized manner which known as process address space or memory layout of C program. Here I have tried to show you the same thing in two parts . /!\: Originally published @ . www.vishalchovatiya.com In the Part 1 i.e. "Overview", we will see segment-wise overview & in Part 2  i.e. "Example", we'll see How C program stored in RAM memory? with example. Part 1: Overview The memory layout of C program organized in the following fashion: Text segment Data segment Heap segment Stack segment Note: It’s not just these 4 segments, there are a lot more but these 4 are the core to understand the working of C program at the machine level. HIGHER  ADDRESS                                                                                                        
   +------------------------+                                                                             
   |  Unmapped or reserved  | Command-line argument & Environment variables                                                                          
   |------------------------|------------------------                                                                          
   |     Stack segment      | |                                                                                                
   |           |            | | Stack frame                                                                                    
   |           v            | v                                                                                                
   |                        |                                                                                                  
   |           ^            | ^                                                                                                
   |           |            | | Dynamic memory                                                                                 
   |     Heap segment       | |                                                                                                
   |------------------------|------------------------                                                                          
   |   Uninitialized data   |                                                                                                  
   |------------------------| Data segment                                                                                     
   |    Initialized data    |                                                                                                  
   |------------------------|------------------------                                                                          
   |                        |                                                                                                  
   |      Text segment      | Executable code                                                                                  
   |                        |                                                                                                  
   +------------------------+                                                                                                  
         LOWER  ADDRESS Text segment Text segment contains executable instructions of your C program, its also called code segment also. This includes all functions making up the program( too), both user-defined and system. main() The text segment is sharable so that only a single copy needs to be in memory for different executing programs, such as text editors, shells, and so on. Usually, the text segment is read-only, to prevent a program from accidentally modifying its instructions. Data segment There are two subsections of this segment 1. Initialized data It contains both static and global data that initialized with non-zero values. This segment can be further classified into the read-only area and read-write area. For example, The global string defined by and a statement like an outside the (i.e. global) would be stored in initialized read-write area. char string[ ] = "hello world" int count=1 main And a global statement like ; makes the variable read-only and to be stored in initialized read-only area. const int A=3 A 2. Uninitialized data (BSS segment) An uninitialized data segment also called the BSS( ‘Block Started by Symbol’ ) segment. Which contains all global and static variables that initialized to zero or do not have explicit initialization in source code. For example, The global variable declared as would be stored in the uninitialized data segment. A statement like static will also be stored in this segment cause it initialized with zero. int A int X=0 If you do not initialize a global variable, by default value is zero. This flushing memory content is usually done by program loader(i.e. ) /lib/ld-linux.so.2 Heap segment The heap segment is an area where dynamically allocated memory (allocated by , , and for C++) resides. malloc() calloc() realloc() new When we allocate memory through dynamic allocation techniques(in other words, run-time memory allocation), program acquire space from OS and process address space grows. We can free dynamically allocated memory space (by using or ). Freed memory goes back to the heap but doesn’t have to be returned to OS (it doesn’t have to be returned at all), so unordered / eventually, cause heap fragmentation. You can learn more about . free() delete malloc free how malloc works here When we use dynamic allocation to acquire memory space we must keep track of allocated memory by using its address. Stack segment The stack segment is an area where local variables stored. By saying local variable means that all those variables which are declared in every function including in your C program. I have written a detailed article about the . main() function stack frame here When we call any function, the stack frame created and when a function returns, the stack frame destroyed/rewind including all local variables of that particular function. A stack frame contains some data like return address, arguments passed to it, local variables, and any other information needed by the invoked function. A stack pointer(SP) which is a special function register of CPU keeps track of stack by each push & pop operation onto it, by adjusted stack pointer to next or previous address. The direction of the stack & heap growth completely depends on the compiler, ABI, OS and hardware. Part 2: Example We have taken a simple example as shown in tittle along with its memory layout. As we discussed in the previous part(i.e. Overview) how executable image of our program divided into the different segment and stored in memory(RAM). Now we understand those blocks by using our example code presented above. Loader A loader is not a segment but kind of program interpreter which reads a different segment from the binary & copy it in RAM in proper fashion. There is a binary utility command by which you can see different segments & path of the loader in binary as follows: $ readelf --segments ./a.out 
Elf file type is EXEC (Executable file)
Entry point 0x8048300
There are 9 program headers, starting at offset 52
Program Headers:
  Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
  PHDR           0x000034 0x08048034 0x08048034 0x00120 0x00120 R E 0x4
  INTERP         0x000154 0x08048154 0x08048154 0x00013 0x00013 R   0x1
      [Requesting program interpreter: /lib/ld-linux.so.2]
  LOAD           0x000000 0x08048000 0x08048000 0x00608 0x00608 R E 0x1000
  LOAD           0x000f08 0x08049f08 0x08049f08 0x00118 0x00124 RW  0x1000
  DYNAMIC        0x000f14 0x08049f14 0x08049f14 0x000e8 0x000e8 RW  0x4
  NOTE           0x000168 0x08048168 0x08048168 0x00020 0x00020 R   0x4
  GNU_EH_FRAME   0x0004c4 0x080484c4 0x080484c4 0x00044 0x00044 R   0x4
  GNU_STACK      0x000000 0x00000000 0x00000000 0x00000 0x00000 RW  0x10
  GNU_RELRO      0x000f08 0x08049f08 0x08049f08 0x000f8 0x000f8 R   0x1
 Section to Segment mapping:
  Segment Sections...
   00     
   01     .interp 
   02     .interp .note.ABI-tag .hash .dynsym .dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .plt.got .text .fini .rodata .eh_frame_hdr .eh_frame 
   03     .init_array .fini_array .jcr .dynamic .got .got.plt .data .bss 
   04     .dynamic 
   05     .note.ABI-tag 
   06     .eh_frame_hdr 
   07     
   08     .init_array .fini_array .jcr .dynamic .got As I have mentioned earlier, there is not only 4 segment as you can see above, but there are a lot of segments which usually depends on compiler & . ABI Above you can see, , , , etc. segments are there. But a stack segment is not shown as its created at a run time & decided by OS(precisely loader & kernel). .data .bss .text in the program header defines the name & path of loader which going to load the current binary image into the RAM by reading these segments. Here it is INTERP /lib/ld-linux.so.2. You can read more about binary . file format ELF here Text segment When you compile C code, you get executable image(which may be in any form like , , , or no extension etc). This executable image contains text segment which you see by Binutils command and it looks like follows: .bin .exe .hex .out $ objdump -d <binary_name> .....
080483f1 <main>:
 80483f1:  8d 4c 24 04            lea    0x4(%esp),%ecx
 80483f5:  83 e4 f0               and    $0xfffffff0,%esp
 80483f8:  ff 71 fc               pushl  -0x4(%ecx)
..... This is executable instructions stored in the text segment as a read-only section and shared by the processes if requires. These instructions read by CPU using program counter and stack frame created in the stack at the time of execution. Program-counter points to the address of the instruction to executed which lies in the text segment. Data segment Initialized Data segment A ; stored in the read-only area. So you can not modify it accidentally. const int x = 1 While a string & stored in the read-write area because we don’t use a keyword like const which makes variable read-only. char str[] = "Hi!"; static int var = 0; Uninitialized Data segment In our program, declared global goes to this area of storage because it is not initialized or initialized to zero by default. int i Heap segment When you compile your program, memory space allocated by you i.e. all locals, static & global variables fixed at compile-time. But when code needs memory at run-time, it approach OS by calling functions like , , etc. malloc() calloc() When OS provides dynamic memory to process it shrinks stack limit pointer which initially points to uninitialized data segment start(the technical word is “program break”, read about it ). here As a result heap segment grows. That’s why there is no line between heap & stack segment. An arrow indicates its growth of direction. In the example code, we allocate 1-byte dynamic memory using function and stored its address in pointer to keep track of that memory or to access it. malloc() ptr This is a local variable of main hence it’s in main’s stack frame, but memory pointed by it is in a heap which I have shown by . ptr *ptr Stack segment The usual starting point(not entry point which is different) of any program is , which is also a function hence, stack frame is created for it while execution. Although there are many functions called before main which I have discussed . main() here As you can see in image, stack frame of is created before function as we called it nested. main() func() As the execution overs its local variable a and its stack frame will destroy(rewind is a precise word here), same goes for function also. func( ) main() And this is how stack grows & shrinks. Intuitive FAQs Q. How do you determine the stack growth direction ? Simple…! by comparing the address of two different function’s local variables. A. *main_ptr = ; *func_ptr = ; { a; func_ptr = &a; } { a; main_ptr = &a;
    func();
    (main_ptr > func_ptr) ? ( ) : ( ); ;
} int NULL int NULL void func () int int main () int printf "DOWN\n" printf "UP\n" return 0 Q. How do you corrupt stack deliberately ? Corrupt the SFR values stored in the stack frame. A. { a; (&a, , ); } {
    func(); ;
} void func () int memset 0 100 // Corrupt SFR values stored in stack frame int main () return 0 Q. How you can increase stack frame size ? alloca() is the answer. Google about it or see . A. this

How C program stored in RAM memory

2018 was a big year for ethics and rights, as new forms of technology and media clashed with what we consider acceptable behaviour in a human society. Now, with companies like building that are ever more personal, we need to continue to develop our notion of what it means to do the right thing. ours digital tools We believe that a key component of the coming generation of AI-powered technology will be . By plugging our physiological and behavioural data into smart systems, they will be able to understand our moods and learn to respond appropriately. We can look forward to this empathic technology bringing us richer, more rewarding human-machine interaction. But it also gives us plenty to be concerned about. digital empathy Below are some of the main issues that my team and I are considering a lot these days, as our species ventures into an unmapped landscape of increasingly smart, connected technology. Legislation vs Innovation: finding the right level of governance. Social Heuristics: doing ‘the right thing’ by default. Personal Data: new models for ownership & control. Transhumanism: extending rights beyond the flesh. The Business Dilemma: ethically profiting with other people’s data. Addressing each in turn then… 1. Legislation vs Innovation The one thing we know about the future is that we don’t know anything. Nobody can tell you exactly what flavours of human-machine interaction will materialise over the coming years or where exactly to draw the ethical line on them. No doubt our world will eventually be furnished with appropriate legislation, guidance and norms but they will probably follow some early mistakes, not preempt them. A recent example is , which launched here in Europe this year, in response to years of questionable treatment of users’ personal data. A measure like GDPR is important but it is also a relatively small step, following behind the huge technological and social lunges we have been taking as a species. Formal policy is often outdated by the time it is released. GDPR It’s not just that legislation often comes around too late. It may also be useful, even necessary, for the law to stay out of the way in the early stages of disruptive innovation. We’ve seen this with the extent to which the internet has maintained a Wild West-style freedom of access. This may have led to pains like fake news and industry-crushing data piracy, but it has also united, educated and entertained the world like nothing before it. Hence the current stink about preserving , as the world wrestles for a settled position in the long term. net neutrality 2. Social Heuristics I suspect we will see a similar evolution unfold for the kind of empathic technology that my peers and I are developing, which is currently just entering the initial lift in the . A few disparate services have emerged and people are starting to find out what works for them and what doesn’t. Over the next handful of years, riding the coattails of the AI explosion, companies like ours are venturing on empathic tech becoming ubiquitous, bundled as part of bigger packages like smart vehicles, smartphones, smartwatches, smart homes… ‘smart’ anything. During that transitional phase we can’t expect government and law to help keep us on the right path, and perhaps we shouldn’t. Instead, we need to lean on the fuzzier framework of social norms and heuristics. You know, good ol’ human relationships. innovation-adoption curve I fear it would be a waste of energy to lobby people not to use services that they don’t entirely trust from the outset, even though such behaviour should be a given. I know I’m guilty of it. We’ve seen how easily people give up their data in return for entertaining or useful services, especially if they get them cheaper. We saw this with social networks, which are traded for free against our provision of personal data, and now we have to deal with shit like the . Okay, so users should be discerning, but on the flip-side organisations can’t dodge responsibility by punting the bullshit line that their users don’t mind sacrificing a little freedom and privacy to get stuff for free. Cambridge Analytica scandal Now mechanisms like GDPR are standing up to personal data abuse but people have still been burned along the way. Organisations can’t wait for legislation before taking responsibility on their own initiatives to mitigate such invasive incidents. It feels like a total cop-out to say this, but organisations (public and private) who adopt intimate behaviour like physiological or psychological data analysis simply need to . They need to avoid exploiting their users. And us users need to keep our eyes open for the signs of such exploitation, rather than blindly adopting the next shiny feature offered to us. do the right thing 3. Personal Data Some of the principles behind GDPR might provide a good kick-off for the steps we should take towards the next generation of digital rights, rules and ethics. Underlying GDPR is increased empowerment and ownership for the user, with respect to their data. To the individual user, GDPR aims to provide rights over their data, such as to be informed, gain access, and erase it. That’s a good start but what if we extrapolate it further? With a little imagination, perhaps we could work towards a more sweeping regulation framework for our digital lives. Ultimately, every individual user should own their personal data wherever it travels, globally, and have the power to govern how it is used. Of course there are massive practicality issues with this notion of global data ownership. It would not only require huge community support but also some changes to the fundamental architecture of digital services. But technologies like the blockchain are already promising potential solutions, such as digital self-sovereign identity ( ). as neatly explained here 4. Transhumanism 2018 marked the 70th anniversary of the . Things have changed since then. Universal Declaration of Human Rights Just six days before the UDHR was issued, George Orwell submitted his final manuscript for , describing a dystopian future of universal surveillance that has continued to feel more pertinent with each passing decade. In the same year, Manchester University, . It consisted of seventeen instructions. How differently do we need to think about rights now, when each of us carries an incomprehensibly powerful computer in our pocket? What will constitute appropriate behaviour when technology can think for itself? Nineteen Eighty-Four fired up the world’s first electronic stored-program computer It is not so much that we are marching blindly into an age of AI-enabled technology, that the tech is rising up to enshroud us where we stand. Doing nothing won’t keep you away from increasingly smart, complex and pervasive digital systems. Accordingly, any provisions to protect and empower us must be as wide-reaching as the innovation. Perhaps a new declaration of universal rights is needed for the generations that will live with AI and IoT. If so, these rights may need to apply beyond what most people would currently consider ‘human’. Our species has a long history of self-modification, augmenting our natural abilities with technology, from fire and clothing to hearing aids and smartphones. It is easy to promote a different set of ethics for ‘them’ machines as for ‘us’ humans, while we continue to blur the lines between the two. At the same time, with every data-point we generate through our online activities, we sculpt ever more detailed digital versions of ourselves. Thus, with the continued blending of human, cyborg, AI and digital self, we may have to devise a set of ethics that applies to the whole continuum — perhaps eliciting a . Universal Declaration of Transhuman Rights 5. The Business Dilemma We’re a startup, still glaring through rosy lenses at the digital utopia we imagine building for future generations. It’s easy for us to preach and prophesy at this early stage, while technology like empathic artificial intelligence is still nascent. We are only starting to stake out our ethical position on this new ground. But already we face commercially driven challenges to the kind of company we want to be. It’s not easy to say no to clients and projects that could secure your business for the next few months. We’ve done it a few times but it’s financially painful. Additionally, when we publicly define our ethical standpoint in an inherently unknowable future — claims that could affect our reputation or limit our addressable market — we feel vulnerable, exposed. But we’re not alone. Anyone building a business model that is significantly reliant on the storage, analysis or transaction of personal user data, or any other intimate human-machine interaction, cannot ignore the ethical implications of their work. They must draw a line and stay behind it. As scary as it might be to do this, it’s not courageous, it’s just the right thing to do. But take heart, we’ve found that our clients and customers, which are typically huge global brands, appreciate it. They’re run by humans too. And given the choice, many of them prefer the responsible path. Doing the right thing is often good for business. New Society in the Digital Human Age Back in May, our CEO & Co-Founder Gawain Morrison sat on some of the panels at , where members of a global community were gathered to discuss a wide range of issues about rights in the digital age. A few days later, GDPR kicked in. Positive activities like these are playing out against a backdrop of some hugely contentious events like the Facebook scandal and the net neutrality debate. There’s something in the air right now. RightsCon This piece is only intended to be a broad kick-off exercise to extend a conversation to a wider audience. Much more needs to be said, and done. Details need to be fleshed out. Solutions need to be tested, selected and implemented. But we don’t want to leave it any longer. As we continue to expose our machines to increasingly intimate and accurate data about our bodies, minds and actions, our machines are simultaneously creeping further towards our position on the spectrum of human identity. We are plugging ourselves into the Internet of Just-About-Everything, which is making our digital selves smarter, more pervasive and more capable by the day. Our digital selves need our love, and we need to figure out a new paradigm of ethics and rights for our digital future. Further Reading A couple of related stories from us: How to Engineer Trust in the Age of Autonomy Alexa, Hug Me: Exploring Human-Machine Emotional Relations

Digital Humans need Digital Ethics

Hey there, setting up an Ingress Controller on your Kubernetes cluster? After reading through many articles and the official docs, I was still having a hard time setting up Ingress. But after numerous attempts I managed to setup an nginx-ingress-controller to forward outside traffic to my in-cluster services, handling HTTP and HTTPS. This writeup is a step by step guide to do this. nginx-ingress-controller nginx-ingress-controller Pssst… incase you are a newbie to Kubernetes like me, here is a nice writeup that explains Ingresses. Kubernetes Ingress_A lot of people seem confused about how Ingress works in Kubernetes and questions come up almost daily in Slack. It’s…_medium.com Kubernetes Ingress Kubernetes Ingress _A lot of people seem confused about how Ingress works in Kubernetes and questions come up almost daily in Slack. It’s…_medium.com The Scene We will setup a simple “hello-world” api and expose the api using the nginx-ingress-controller on a local cluster using Minikube. nginx-ingress-controller nginx-ingress-controller Minikube Minikube TL;DR — Here is a boilerplate that reflects what is explained. TL;DR — Here is a boilerplate that reflects what is explained. Here Steps Step 1: Creating the service to be exposed Assuming that you already have Kubectl and Minikube setup, let’s deploy our hello-world api and expose it within our cluster as a NodePort Service. We will be using a simple api for the purpose of the demo. The source code can be found here. hello-world NodePort Service NodePort Service here here The config file consists of the deployment and the service. Normally we separate them into individual files. kubectl create -f hello-world.yaml Now you should be able to see the created resources when you run kubectl get all | grep hello-world Step 2: Creating a default backend to be used by the nginx-ingress-controller We need to provide a default backend for the ingress-controller. The default backend is the default service that Nginx falls backs to if it cannot route a request successfully. The default backend needs to satisfy the following two requirements : default backend default backend serves a 404 page at /
serves 200 on a /healthz serves a 404 page at / serves 200 on a /healthz The nginx-ingress-controller project has an example default backend. kubectl create -f default-backend.yaml kubectl create -f default-backend.yaml Step 3: Creating secrets to specify the SSL certificate for Nginx Create a self-signed certificate using OpenSSL. The common name specified while generating the SSL certificate should be used as the host in your ingress config. We create secrets for the given key, certificate and dhparam files. Use corresponding file names for the key, certificate and dhparam. Create a self-signed certificate using OpenSSL common name common name host host kubectl create secret tls tls-certificate --key <key-file>.key --cert <certificate-file>.crt kubectl create secret generic tls-dhparam --from-file=<dhparam-file>.pem kubectl create secret generic tls-dhparam --from-file=<dhparam-file>.pem Step 4: Enable ingress on Minikube Minikube versions > v0.14.0 ships with Nginx ingress setup as an add-on. It can be enabled by simply running: v0.14.0 v0.14.0 minikube addons enable ingress Enabling the add-on provisions the following: a configMap for the Nginx loadbalancer.
the nginx-ingress-controller.
a service that exposes a default Nginx backend pod for handling unmapped requests. a configMap for the Nginx loadbalancer. configMap configMap the nginx-ingress-controller. nginx- ingress-controller ingress-controller a service that exposes a default Nginx backend pod for handling unmapped requests. service Step 5: Setting up the nginx-ingress-controller Now we create a service for the controller. The service is of type LoadBalancer so that it is exposed outside the cluster. LoadBalancer LoadBalancer The config consists of the deployment and service for the nginx-ingress. The following can be observed from the config : The secret for the default SSL certificate and default-backend-service are passed as args.
The image nginx-ingress-controller:0.9.0-beta.5 is used. I have tried the later beta releases. This seems to be a more stable for our usecase.
The tls-dhparam secret is mounted on a volume to be used by the controller. The secret for the default SSL certificate and default-backend-service are passed as args. default SSL certificate default SSL certificate default-backend-service default-backend-service The image nginx-ingress-controller:0.9.0-beta.5 is used. I have tried the later beta releases. This seems to be a more stable for our usecase. nginx-ingress-controller:0.9.0-beta.5 The tls-dhparam secret is mounted on a volume to be used by the controller. tls-dhparam tls-dhparam Create the controller by running: kubectl create -f nginx-controller.yaml We should be able to see the created resources with the exposed IP address after a few seconds. To get the IP on Minikube run. minikube service nginx-ingress --url Running a Curl request to the exposed endpoint should give us a response from the default-backend as we still haven’t configured our ingress to point to our hello-world api. Curl default-backend curl http://<nginx-service-IP>:<port> http://<nginx-service-IP>: default backend - 404% Step 6: Configure Ingress rules Coming to the part where we will be spending most of our time. We provide the forwarding rules to the ingress. We use annotations here to pass configuration params to the underlying ingress-controller, Nginx in our case. You can find more about annotations here. here here nginx.org/ssl-services is used to specify the service that is to be load balanced using HTTPS
We specify the hosts, paths and their corresponding service handlers. nginx.org/ssl-services is used to specify the service that is to be load balanced using HTTPS nginx.org/ssl-services nginx.org/ssl-services nginx.org/ssl-services is used to specify the service that is to be load balanced using HTTPS We specify the hosts, paths and their corresponding service handlers. kubectl create -f ingress.yaml We now have an Nginx web server configured that routes traffic for api.sample.com to our configured hello-world-svc. It falls back to the default-backend service for unhandled requests. api.sample.com api.sample.com hello-world-svc hello-world-svc default-backend service default-backend service Also you might want to update /etc/hosts file to resolve your host to your minikube IP. Assuming your Minikube IP is 192.168.99.101 Your entry should look like. /etc/hosts 192.168.99.101 192.168.99.101 api.sample.com You should be able to access the exposed endpoints via https. GET api.sample.com/:namePOST api.sample.com/:namePUT api.sample.com/:name Adding the annotation ingress.kubernetes.io/ssl-redirect: “true” to the ingress.yaml config enables traffic through HTTP and HTTPS. ingress.kubernetes.io/ssl-redirect: “true” ingress.yaml Conclusion Conclusion Ingress does allow you to configure multiple Virtual Hosts, Sticky sessions, Path rewrites and also custom configs, providing a powerful, flexible routing mechanism for Kubernetes. For more info on nginx-ingress-controller visit https://github.com/nginxinc/kubernetes-ingress https://github.com/nginxinc/kubernetes-ingress https://github.com/nginxinc/kubernetes-ingress A similar procedure can be used to deploy to AWS, GKE instead of Minikube. Kubernetes and Ingress in particular is constantly evolving I will try my best to keep this updated. Boy Scout Oath. Kubernetes and Ingress in particular is constantly evolving I will try my best to keep this updated. Boy Scout Oath. Boy Scout Oath. Good Reads https://medium.com/@Oskarr3/setting-up-ingress-on-minikube-6ae825e98f82
http://danielfm.me/posts/painless-nginx-ingress.html
https://daemonza.github.io/2017/02/13/kubernetes-nginx-ingress-controller/ https://medium.com/@Oskarr3/setting-up-ingress-on-minikube-6ae825e98f82 https://medium.com/@Oskarr3/setting-up-ingress-on-minikube-6ae825e98f82 http://danielfm.me/posts/painless-nginx-ingress.html http://danielfm.me/posts/painless-nginx-ingress.html https://daemonza.github.io/2017/02/13/kubernetes-nginx-ingress-controller/ https://daemonza.github.io/2017/02/13/kubernetes-nginx-ingress-controller/ Hope you enjoyed reading this as much as I enjoyed writing it. If you think this will be of help to someone? Do not hesitate to share. If you liked it, tap the clap below so other people will see this here on Medium. Don’t forget to show some love by following the blog! Hope you enjoyed reading this as much as I enjoyed writing it. If you think this will be of help to someone? Do not hesitate to share. If you liked it, tap the clap clap below so other people will see this here on Medium. Don’t forget to show some love by following the blog! following the blog! *Update on 11 November 2018* Added RBAC in the example setup. Thanks to Jens Madsen for his contribution. *Update on 11 November 2018* Added RBAC in the example setup. Thanks to Jens Madsen for his contribution. *Update on 11 November 2018* *Update on 11 November 2018* Jens Madsen

Setting up Nginx Ingress on Kubernetes

The main aim of this piece is to grasp the workings of mapped types in and explore various typical scenarios. I frequently come across mapped types in my work. In this guide, I'll explain how mapped types can be utilized and the assistance provided by utility types. TypeScript Let’s say, that you have an object, that describes some entity, like a person. interface Person {
	name: string;
	secondName: string;
	age: number;
    description: string;
	email: string;
    id: number;
} And you want to have a , that stores what component to render for each field when rendering Person on a page. For that, we might use something called a mapped type. hashmap type PersonInputType = {
  [key in keyof Person]: () => React.JSX.Element;
} Here, returns the union type of all the keys in interface. keyof Person What that means is, that type looks like this: PersonInputType type PersonInputType = 'name' | 'secondName' | 'age' | 'description' | 'email'; Now, suppose that you don’t have components mapped out for each property from Person. For example, there is probably no component should be rendered for the id key. One thing you can do is, add an optional parameter. type PersonInputType = {
  [key in keyof Person]?: React.Component;
} But what if you want everything to be mapped out except for ID. One way to go about that is to use Pick from Typescript to list all the keys from the object we need. type PersonInputType = {
  [key in keyof Pick<Person, 'name' | 'secondName'>]: () => React.JSX.Element;
} But it would be annoying to list all the needed keys just so one element would be excluded. For that, we can use Omit. type PersonInputType = {
  [key in keyof Omit<Person, 'id'>]: () => React.JSX.Element;
} Now, that looks better. Let’s continue with utility types. I’ve demonstrated that you can make properties from the original type by using ‘?’ at the end. Also, you can use a Partial utility type. For example: type PersonInputType = {
  [key in keyof Partial<Person>]: React.Component;
} Partial makes every key from that object optional. Now what if, the situation was reversed? Some of the Person properties would be optional, but in the mapped type, you need all types to be required and defined. Then we can use Required. type PersonInputType = {
  [key in keyof Required<Person>]: React.Component;
} Let’s also consider . As the name suggests typeof returns the type of an object. When it might be useful to use both keyof and typeof? For example, you have an enum, describing app states. typeof enum AppStates {
  'READY' = 'READY',
  'LOADING' = 'LOADING',
  'ERROR' = 'ERROR'
} And now you need a hashmap to specify text messages for each state. How to use these keys from the enum? You can do the following type AppStatesInfo = {
  [key in keyof typeof AppStates]: string;
} Here, here returns the typeof an object, and we already discussed and now we can combine both. You can also avoid using keyof and typeof in this case and just write it shorter: typeof keyof type AppStatesInfo = {
  [key in AppStates]: string;
} Does the same thing. The one problem here might be, that enums a lot of times are capitalized, no specific reason, just sort of a convention. But keys in a hashmap aren’t. We can again come back to utility types, and make keys lowercase. type AppStatesInfo = {
  [key in Lowercase<AppStates>]: string;
} I think this might cover a lot of everyday cases. Mapped types help you derive types from interfaces, objects, and enum you have in your application to connect one type to others.

Working With Mapped Types in TypeScript

Stories, News & Mentions about UMAPPED

Categories

Trending Topics

Stories, News & Mentions about UMAPPED

Umapped’s Stories on HackerNoon

Categories

Trending Topics