Mirantis Brings OpenStack to Kubernetes, Adding Private Cloud Capabilities to Mirantis Cloud Native Platform

The post Mirantis Brings OpenStack to Kubernetes, Adding Private Cloud Capabilities to Mirantis Cloud Native Platform appeared first on Mirantis | Ship Code Faster.
To help customers ship code faster, the new Mirantis OpenStack for Kubernetes combines Mirantis’ track record of enterprise success with both Kubernetes and OpenStack.
Campbell, CA, December 10, 2020 — Mirantis, the open cloud company, today announced the first in a planned series of enhancements to the Mirantis Cloud Native Platform, enabling customers to ship code faster on a Kubernetes foundation that provides simplicity, cloud choice and security. This first release, already available to Mirantis Container Cloud customers via continuous updates, adds the ability to deploy, scale, and update private clouds on Kubernetes substrates.
Building on this foundation, Mirantis today released Mirantis OpenStack for Kubernetes — a containerized edition of the open-source infrastructure-as-a-service (IaaS) platform chosen by Mirantis customers across industries and geographies to build some of the largest and best-performing private clouds in the world.
“Kubernetes and containers are superior technologies for building and releasing applications that run anywhere, scale gracefully, are resilient, and that can be updated without service downtime,” said Shaun O’Meara, global field CTO at Mirantis. “We engineered Mirantis Cloud Native Platform to deliver, monitor, and update Kubernetes clusters, anywhere — on bare metal, private, or public clouds — providing a simple, self-service experience for customers.”
Mirantis OpenStack for Kubernetes provides a feature-rich, mature environment for hosting both legacy apps and modern use cases such as Network Functions Virtualization, mobile network operations, and large-scale scientific computing. And it provides this without operational headaches — under the hood, leveraging Kubernetes to ensure configurability, resilience, robustness and seamless updates for OpenStack running on top of it.
“Organizations still need virtual machines and private cloud infrastructure to make them easy to consume and manage at scale — in many cases, hosting their most valuable applications,” said O’Meara. “At the same time, almost all are now moving forward with containers and Kubernetes, because they know these technologies will help them ship code faster and run applications with unprecedented resilience, scale, and economy. So Mirantis Cloud Native Platform addresses this whole continuum of needs, with maximum choice, simplicity, and security.”
By delivering a batteries-included, secure by default, and certified implementation of Kubernetes everywhere, and using it as a substrate for managing key applications and technologies, Mirantis Cloud Native Platform and Mirantis Container Cloud can deliver a simple cloud-like experience that supports all the development and hosting models organizations need (VMs, containers, orchestrators); managing the entire platform stack on any infrastructure (bare metal, private clouds, public clouds), and providing a unified management experience to smoothly operationalize these complex technologies across a diverse multi-cloud.
To learn more about Mirantis OpenStack for Kubernetes visit: https://www.mirantis.com/software/mirantis-openstack-for-kubernetes/ The post Mirantis Brings OpenStack to Kubernetes, Adding Private Cloud Capabilities to Mirantis Cloud Native Platform appeared first on Mirantis | Ship Code Faster.
Quelle: Mirantis

Announcing Mirantis OpenStack for Kubernetes

The post Announcing Mirantis OpenStack for Kubernetes appeared first on Mirantis | Ship Code Faster.
Today, Mirantis announced the general availability of Mirantis OpenStack for Kubernetes, a new offering now included in the Mirantis Cloud Native Platform. Existing users of Mirantis Container Cloud (formerly Docker Enterprise Container Cloud) will automatically receive the update, which lets them deploy containerized OpenStack control planes, Ceph storage, and compute hosts on Mirantis Kubernetes Engine (formerly Docker Enterprise/UCP).
What does this announcement mean?
Easy to use, resilient private clouds – Pragmatically, it means customers can use Mirantis Cloud Native Platform to air-drop classic private cloud capacity anywhere they have physical host capacity to run it (such as bare metal datacenters at HQ; distributed server farms at satellite locations; colos; medium-scale ‘edge’ server racks, etc. And then it lets them manage, observe, scale, and update this capacity via the same, smooth, public-cloud-like, centrally-administered, continuously-updated, self-service-oriented user experience Mirantis Container Cloud wraps around Kubernetes clusters.
In fact, if someone needs easy, self-service delivery of dev/test/production Kubernetes clouds in tandem with classic, mature virtual-machine hosting capability, they can use Mirantis Container Cloud to deploy Mirantis OpenStack, and then again to deploy Mirantis Kubernetes Engine clusters on virtual machines managed by OpenStack. Given the bare metal capacity, there’s probably no easier, faster way to bootstrap private infrastructure-as-a-service and use it to deliver dynamic container orchestration capability.
OpenStack — product of one of the world’s largest and most formidable open source communities — just celebrated its tenth anniversary. The Register and others marked the occasion with articles discussing the framework’s dominance in telecommunications, where it’s a preferred host for Network Functions Virtualization workloads, among other fields. OpenStack is today a very mature IaaS cloud solution that’s remarkably easy to use — complete with a sleek web interface (Horizon) and comprehensive APIs.
Why OpenStack on Kubernetes?
Using Kubernetes as a substrate for OpenStack solves “challenges” historically associated with running big, production OpenStack clouds (some of which will sound familiar to Kubernetes users).
MOS clusters leverage native Kubernetes features for resilience and adaptability. They use K8s operators to maintain cluster state, horizontal pod autoscaling to expand control-plane capacity under load, and seamless, zero-downtime Kubernetes rolling updates of OpenStack and other components. Containerized OpenStack components execute on Mirantis Container Runtime (formerly Docker Engine – Enterprise), which provides DISA STIG security, FIPS-140-2 encryption, and other characteristics making them suitable for use in gov/mil, financial services, and other regulated sectors.   
Mirantis Cloud Native Platform delivers Mirantis OpenStack for Kubernetes the same way  it does Mirantis Kubernetes Engine child clusters: ready for work, centrally administered, observed, and with Mirantis Container Cloud providing a single point of integration with corporate directory and other services. Mirantis OpenStack for Kubernetes clusters are delivered pre-instrumented and integrated with StackLight metrics, so users get observability out of the box. Mirantis Container Cloud also provides a single point of integration with enterprise directory, notifications, ticketing, etc., and top-level identity and access management, so Mirantis OpenStack clusters can be delivered with users, teams, tenants, SSH keys, etc. already provisioned for immediate use and secure access.

Kubernetes: Zamboni for the Multi-Cloud Hockey Rink
Mirantis OpenStack for Kubernetes also proves a point that Mirantis has embraced (and debated) internally for several years: that Kubernetes can work very well as a substrate for delivering and managing complex and even reputedly “tricky” applications, while giving users maximum choice in where their applications run.
As Shaun O’Meara, Global Field CTO at Mirantis, says in the press release: “Kubernetes and containers are superior technologies for building and releasing applications that run anywhere, scale gracefully, are resilient, and that can be updated without service downtime.” A modern workload constellation like containerized OpenStack can leverage Kubernetes directly for performance (for example, by scaling control-plane components out, horizontally, to deal with particular kinds of bursty load); resilience; optimal scheduling; failed-workload restarts; operator-based storage management; etc., and draw on its built-in lifecycle management features and associated best-practice for managing updates with zero or minimal impact on service availability.
And Kubernetes — or at least, Mirantis Kubernetes Engine: a Kubernetes distribution engineered to have minimal dependencies on host and OS — can “manage down” as well. For Mirantis Cloud Native Platform and Container Cloud, this means simpler, more reliable, and more highly-optimizable logic for managing bare metal, and for addressing the particular requirements and opportunities presented by private- and public-cloud substrates.
In short, Kubernetes means managing the whole stack more reliably, and delivering that seamless, simple, cloud experience for managing Kubernetes (and now OpenStack, and soon other enabling technologies) across the multi-cloud.
Early Adopters Show the Way
Current Mirantis OpenStack customers are enthusiastically evaluating and working with Mirantis OpenStack on Kubernetes, which lets them improve the efficiency and agility of their OpenStack private cloud implementations while also gaining a unified model for providing Kubernetes (and Swarm) orchestration across the multi-cloud. Several are also using Mirantis OpenStack to host Kubernetes clusters used as foundations for platform-as-a-service, serverless computing, and similar frameworks.
Enterprises, financial services, and other orgs are also using Mirantis OpenStack for Kubernetes to resource-manage high performance computing on bare-metal OpenStack compute nodes, using this capacity for machine-learning, big data analytics, media processing, and other initiatives. Mirantis Container Cloud, OpenStack, and Kubernetes give these organizations great flexibility to allocate compute dynamically and share expensive hardware economically among jobs, projects, and teams.
Infrastructure and service providers, meanwhile, are adopting Mirantis OpenStack for Kubernetes as a foundation for ambitious public IaaS offerings, as well as initiatives providing centralized infrastructure for managing large fleets of IoT devices and the data and transactional loads they generate. Telco operators are applying Mirantis OpenStack for Kubernetes for hosting NFV workloads, and for new trials around 5G edge computing.
To schedule a live demo of Mirantis OpenStack for Kubernetes, click here.
The post Announcing Mirantis OpenStack for Kubernetes appeared first on Mirantis | Ship Code Faster.
Quelle: Mirantis

Lens 4.0 Kubernetes IDE is here

The post Lens 4.0 Kubernetes IDE is here appeared first on Mirantis | Pure Play Open Cloud.
There’s been a lot of excitement around here about Lens lately. And why not? With more than 1.3 million downloads and close to 10,000 stars on Github since its inception in March 2020, Lens has quickly become the world’s most popular IDE for Kubernetes, and with release of Lens 4.0, that’s likely to not just continue, but accelerate.
In particular, large enterprises are beginning to see the true value of Lens. Many of them feel the complexity of Kubernetes is slowing down adoption, preventing them from seeing the container ROI they were expecting.
Lens is a user-friendly desktop application for all your kubernetes platforms. It enables users to easily onboard and operate their applications in Kubernetes, improving time to market and productivity, and increasing ROI. It is a standalone application for MacOS, Windows, and Linux operating systems, and an open source project that dramatically simplifies application development for Amazon EKS, Google GKE, Microsoft AKS, Mirantis Container Cloud, Red Hat Openshift, and other CNCF-certified Kubernetes distributions.
In fact, we’re so excited about the quality and value of Lens that we’ve added it to the lineup of products for which we provide commercial support and services.
Enterprise Support, Training and Services for Lens
Mirantis is the biggest contributor to, and in the driver’s seat of, the Lens open source project, and with all our know-how and insights into the Lens IDE user base, we have designed a suite of value-added services to help enterprises in their journey towards adopting, integrating, and unlocking the full potential of Lens at scale. With these value-added services, enterprises using Lens will enjoy faster time to market, productivity and ROI for their container infrastructure investments. These value-added services include:

Technical Support:  Just like for any other enterprise-grade solution, you’ll be able to get professional technical support to help you through any problems that you encounter, whether you’re running on Windows, MacOS, or Linux, with a first response time of 4 business hours.
Professional Services: We’ve seen how powerful Lens can be in remaking the way your developers create the software that runs your business, but as they say, “with great power comes great responsibility.”  Mirantis provides professional services to ensure that your Lens deployments comply with any IT governance or guardrails you have in place, and we can help you create your own custom extensions to help Lens give you even more of a leg up over the competition.
Training:  Mirantis Training provides private operator or developer track courses, and even training in extensions development.

Have we piqued your curiosity?  Schedule a demo to see what Lens can do.
Lens 4.0 New Features
The strength of the Lens Kubernetes IDE is in the way in which it takes managing Kubernetes clusters and workloads and the many, many, MANY objects and settings they involve and makes it not just straightforward, but simple. As Miska Kaipiainen, senior director of engineering and principal of the Lens open source project says in the community’s blog announcing the new release, “These users are using Lens because it provides the full situational awareness for everything that runs in Kubernetes. It’s lowering the barrier of entry for people just getting started and radically improving productivity for people with more experience.”

Lens 4.0, which was released a few days ago, takes that utility to the next level with the addition of the Extensions API. The Extensions API means that any company, vendor, or individual developer can create plugins for Lens, enabling a seamless experience between their products and Kubernetes clusters.
We have been working with our partners and friends in the cloud native ecosystem to refine Lens 4.0 extension API capabilities. Some of these vendors have already made their first extensions available for public use, while others are still iterating. In the near future, you can look forward to extensions from companies such as:

Ambassador Labs (formerly Datawire)
Aqua Security
Carbon Relay
Carbonetes
Clastix
Eagle AI
Kong
nCipher
Nu Skin International
StackRox
Wohlig Transformation

You can also create a Lens extension of your own or become a partner. To learn more, join us next Tuesday, December 15, when the Lens Kubernetes IDE User Group is hosting a virtual workshop, How to Build a Lens Extension.
Meanwhile, we want to congratulate the Lens community on this milestone, and remind you to watch this space for more information on creating extensions of your own!
If you haven’t tried Lens yet, check out the Getting Started with Lens blog.
 
The post Lens 4.0 Kubernetes IDE is here appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

Mirantis to take over support of Kubernetes dockershim

The post Mirantis to take over support of Kubernetes dockershim appeared first on Mirantis | Pure Play Open Cloud.
The rumors of dockershim’s demise have been greatly exaggerated. If you follow the Kubernetes ecosystem, you may have been caught up in the consternation excitement over the announcement that starting with the soon-to-be-released Kubernetes 1.20, users will receive a warning that dockershim is being deprecated, and will be removed in a future release. For many people this has sparked a moment of panic, but take a deep breath, everything is going to be OK.
Even better news, however, is that Mirantis and Docker have agreed to partner to maintain the shim code standalone outside Kubernetes, as a conformant CRI interface for the Docker Engine API. For Mirantis customers, that means that Docker Engine’s commercially supported version, Mirantis Container Runtime (MCR), will be CRI compliant. We will start with the great initial prototype from Dims at https://github.com/dims/cri-dockerd and continue to make it available as an open source project, https://github.com/Mirantis/cri-dockerd. This means that you can continue to build Kubernetes based on the Docker Engine as before, just switching from the built in dockershim to the external one. We will work together on making sure it continues to work as well as before and that it passes all the conformance tests and continues to work just like the built in version did. Mirantis will be using this in Mirantis Kubernetes Engine, and Docker will continue to ship this shim in Docker Desktop.
In the beginning…
If you work with Kubernetes, you know that it orchestrates containers. For many people, “container” means “Docker”, but that’s not strictly true. Docker revolutionized containers and brought them into common usage, and as such, the Docker Engine was the first (and originally the only) container runtime to be supported by Kubernetes.
But that was never the Kubernetes community’s long term plan.
Long term, the community wanted the ability to run many different types of containers (remember rkt?) and as such, created the Container Runtime Interface (CRI), a standard way for container engines to communicate with Kubernetes. If a container engine is CRI compliant, it can run in Kubernetes with no extra effort.
The first CRI-compliant container engine was containerd, which was derived from the guts of … wait for it… Docker. You see, Docker is more than just a container runtime; it includes other pieces that are meant for human consumption, such as the user interface. So Docker pulled out the pieces that were actually relevant as containerd, and it became the first CRI-compliant runtime. It then donated containerd to the Cloud Native Computing Foundation (CNCF). The cri-containerd component is runtime agnostic and supports multiple Linux operations systems, as well as Windows.
However, that left one problem. Docker itself still wasn’t CRI-compliant.
What is dockershim?
Just as Kubernetes started out with built-in support for Docker Engine, it also included built-in support for various storage volume solutions, network solutions, and even cloud providers. But maintaining these things on an ongoing basis became too cumbersome, so the community decided to strip all third party solutions out of the core, creating the relevant interfaces, such as:

Container Runtime Interface (CRI)
Container Network Interface (CNI)
Container Storage Interface (CSI)

The idea was that any vendor could create a product that automatically interfaces with Kubernetes, as long as it is compliant with these interfaces.
That doesn’t mean that non-compliant components can’t be used with Kubernetes; Kubernetes can do anything with the right components. It just means that non-compliant components need a “shim”, which translates between the component and the relevant Kubernetes interface. For example, dockershim takes CRI commands and translates them into something Docker Engine understands, and vice versa. But with the drive to take third-party components like this out of the Kubernetes core, dockershim had to be removed.
As dramatic as this sounds, however, it’s less of an issue than you think; the images you build with docker build are compliant with the underlying standard CRI uses, so they are still going to work with Kubernetes.
What happens now that built in dockershim support is deprecated in Kubernetes?
For most people, the deprecation of dockershim is a non-issue, because even though they’re not aware of it, they’re not actually using Docker per se; they’re using containerd, which is CRI compliant. For those people nothing will change.
Some people, however, including many Mirantis customers, are running workloads that are dependent on dockershim in order to work seamlessly with Kubernetes.
Because it’s still a necessary real-world component for many companies, Mirantis and Docker have agreed to continue supporting and developing dockershim, and to continue its status as a standalone open source component.
So what does this mean in actuality?
If you’re using containerd directly, you don’t have to worry about this at all; containerd will work with the CRI. If you’re a Mirantis customer, you also won’t have to worry about this; dockershim support will be included with the Mirantis Container Runtime, making it CRI-compliant.
Otherwise, if you’re using the open source Docker Engine, the dockershim project will be available as an open source component, and you will be able to continue to use it with Kubernetes; it will just require a small configuration change, which we will document.
So even though this came as a shock to many people, nobody is being left out in the cold.
If you’re looking for more information, the community has put out an FAQ and blog post giving more detailed information.
The post Mirantis to take over support of Kubernetes dockershim appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

Recommended Reads for International Day of Disabled Persons

WordPress.com, as my colleague Anne recently wrote, continues to be a space for people to tell their personal stories and amplify their voices. Today, International Day of Disabled Persons, we’d like to highlight a few perspectives and thoughtful reads to raise awareness of the myriad experiences of disabled people.

This reading list is merely a starting point — be sure to explore more posts tagged with “disability” in the WordPress.com Reader, for example. We hope it introduces you to writers and disability rights advocates whose work you may not be familiar with.

“How to Properly Celebrate a Civil Rights Law During a Pandemic in Which Its Subjects Were Left to Die” at Crutches and Spice

Imani Barbarin at Crutches and Spice writes about life, current events, entertainment, and politics from the perspective of a Black woman with cerebral palsy. Read her reflections on the death of actor Chadwick Boseman, or the anniversary of the Americans With Disabilities Act (which turned 30 this year), excerpted below.

Prior to the pandemic, disabled people were told that the accessibility we needed was cost-prohibitive and unlikely to be implemented only to watch as the institutions that barred our inclusion make those tools available now that nondisabled people needed them. We called for polling places and voting procedures to be made accessible only to watch as politicians shut down polling places in predominantly black neighborhoods. We begged for businesses to be inclusive and accessible to disabled customers only for accessibility to be pitted against small businesses and workers’ rights.And now, unironically, they celebrate.They celebrate not weighed down by their own words calculating the amount of acceptable death it would take to reopen the economy. They post our pictures celebrating their own “diversity and inclusion” without confronting the fact they only became accessible because of a pandemic and as they loudly push to reopen, they amplify our voices for now with no plan to continue to include the disability community as businesses start to reopen.I’m angry.But I am also filled with love and gratitude for my community.

#ADA30InColor at Disability Visibility Project

Founded by Alice Wong, The Disability Visibility Project is a community focused on creating and sharing disability media and culture. You’ll find a range of content, including oral histories, guest blog posts, and a podcast hosted by Wong and featuring conversations with disabled people.

If you’re not sure where to start, dive into the 13 posts in the #ADA30InColor series — it includes essays on the past, present, and future of disability rights and justice by disabled BIPOC writers. Here are excerpts from two pieces.

More than anything, however, it was my blindness that allowed me to experience perhaps the biggest impact of this transition. Being able to attend a “regular” school as opposed to the school for the blind and take classes with sighted peers every day, becoming friends with classmates who have different types of disabilities, having Braille placards by every classroom door at a school not intended solely for only blind students, meeting blind adults with various jobs — ranging from chemist to statistician to lawyer — was my new reality. Even as a teenager, I knew it was a great privilege to be in this new reality — America, where there were laws in place to protect the rights of disabled people to live, study, play, and work alongside the nondisabled. At the same time, this reality began to feel like a multi-layered burden as I began to form and understand different elements of who I am: a disabled, 1.5 generation Korean-American immigrant. “Building Bridges as a Disabled Korean Immigrant” by Miso Kwak

Even with medical documentation on file, disabled BIPOC face added suspicion, resistance, and stigma from instructors, particularly for invisible disabilities. We are also stereotyped in racially coded ways as unreasonable, aggressive, and “angry” when we self-advocate. We are especially heavily policed in graduate and professional programs, and this is apparent in our representation — while 26 percent of adults in the US have a disability, only 12 percent of post-baccalaureate students are students with disabilities. This is even lower among some ethnicities — only 6 percent of post-baccalaureate Asian American students have a disability.  “The Burden and Consequences of Self-Advocacy for Disabled BIPOC” by Aparna R.

“My Favorite Wheelchair Dances” at Alizabeth Worley

Alizabeth Worley is a writer and artist with moderate chronic fatigue syndrome. She writes about topics like health and interabled marriage (her husband has cerebral palsy). In a recent post, Alizabeth compiles YouTube clips of beautiful and inspiring wheelchair dances, some of which are from Infinite Flow, an inclusive dance company. Here’s one of the dances she includes in her list, featuring Julius Jun Obero and Rhea Marquez.

“The Intersection of Queerness and Disability” at Autistic Science Person

Ira, the writer at Autistic Science Person, explores the parallels between queerness and disability, and the way other people make assumptions about their body.

I often put down Female for medical appointments even if there’s a Nonbinary option, as I don’t want to “confuse” them. It’s just easier for everyone, I think. I worry about backlash I would receive, or the confused looks I would get if I put down Nonbinary. I think about people tiptoeing around my gender. I can’t deal with even more self-advocacy in a medical visit as an autistic person, so it’s just not worth it, I think. I’m reminded of the time I carried folding crutches to my unrelated medical appointment. Both the staff and doctor asked me why I brought crutches when I was “walking normally.” I had to explain that I needed them on my walk back for my foot pain. Both explaining my disability and explaining my gender — explaining the assumptions around my body is exhausting.

No matter what, people will make assumptions. Both ableism and cisnormativity are baked into our brains and our society. The things people have to do to accommodate us and acknowledge us involves unlearning their preconceptions. Society really doesn’t want us to do that. This is why there is so much defensiveness for both providing accommodations and acknowledging someone’s gender, pronouns, and name. People don’t want to do that work. They don’t want to be confronted with structural changes, the issue of gender norms, and the problems that disabled people face every day. They just want to go on with their lives because it’s easier to them. It’s easier for them to ignore our identities.

“The Last Halloween, The First Halloween” at Help Codi Heal

“The first Halloween my daughter could walk was the last Halloween that I could,” writes Codi Darnell, the blogger at Help Codi Heal. In a post reflecting on her fifth Halloween in a wheelchair, Codi reflects on change, pain, and the firsts and lasts in her life.

It was all automatic — all done without realizing the ways these simple acts of motherhood were deeply engrained in my identity. All done with zero understanding that something so simple could be snatched away — and how painful it would be when it was.Because a year later I would not hold her hand up the stairs or scoop her up and onto my hip. I wouldn’t stand beside her at the door or see her face light up when — in her big two-year-old voice — she managed all three words “trick-or-treat”. A year later, I would understand the fragility of our being and know intimately the pain of things taken away. But I would still be there. 

“Even If You Can’t See It: Invisible Disability and Neurodiversity” at Kenyon Review

At Kenyon Review, author Sejal A. Shah writes a personal essay on neurodiversity, depression, academia, and the writing life.

Maybe things would have turned out differently had I requested accommodations, had I known about the Americans with Disabilities Act (ADA, 1990), had I understood my “situation,” as my aunt calls it, counted as a disability. The ADA law was amended in 2008 to include bipolar disorder. I began my job in 2005 and finished in 2011. It would have been helpful to know about the law and my rights under it.I didn’t know the laws then; I didn’t know them until writing this essay. I looked normal; I passed. Would my career have turned out differently had I been willing to come out (for that’s what it felt like, an emergence into a world that might not accept me)? I was certain the stigma of having a major mood disorder would have hurt me professionally. Even had I disclosed my disorder, HR and my supervisors may not have agreed to modifications in my work responsibilities. I would still have needed to advocate for myself — would still have needed the energy to provide documentation and persist. For years, I had been ashamed, alarmed, and exhausted from trying to keep my head above water.

“The Outside Looking In” at Project Me

Project Me is the blog of Hannah Rose Higdon, a Deaf Lakota woman who grew up on the Cheyenne River Sioux Reservation. In “The Outside Looking In,” Higdon offers a glimpse into her experience as a child who was born hard of hearing, and whose family had very little access to the support she needed. (Higdon is now profoundly Deaf.)

I look up as my uncle talks to me. I nod. I smile. And I pretend I know just exactly what is going on. The truth is I have no clue what he’s saying or why he’s laughing, but I laugh too and mimic his facial expressions. I would never want to draw any more attention to myself than necessary. You see, I might only be 5 years old, but I know just how important it is to pretend.

“How to Center Disability in the Tech Response to COVID-19” at Brookings TechStream

Organizer, attorney, and disability justice advocate Lydia X.Z. Brown calls on the tech industry to carefully consider how policy affects marginalized communities, looking at algorithmic modeling in hospitals, contract tracing and surveillance, and web inaccessibility.

For disabled people who are also queer, trans, or people of color, the deployment of algorithmic modeling increases the risk of compounded medical discrimination. All marginalized communities have long histories and ongoing legacies of surviving involuntary medical experimentation, coercive treatment, invasive and irreversible procedures, and lower quality of care — often justified by harmful beliefs about the ability to feel pain and quality of life. These health care disparities are exacerbated for people who experience multiple forms of marginalization.

Spoonie Authors Network

The Spoonie Authors Network features work from authors and writers about how they manage their disabilities or chronic illnesses and conditions. Managed by Cait Gordon and Dianna Gunn, the community site also publishes resources and produces a podcast. Explore posts in the Featured Author or Internalized Ableism categories, like the piece below, to sample some of the writing.

When my neurologist suggested that I get a parking pass, I turned it down.“I’d rather that go to someone more deserving,” I said. “There are people out there who are far more disabled than I am. Let the pass go to one of them.”“You have difficulty walking. What would happen if it was icy or there were other difficult walking conditions?” she said kindly. “This is for your safety.”I nodded and accepted the parking pass, even though I felt it made me look weak. I wasn’t disabled enough to warrant a parking pass. I can walk. I didn’t need it, I told myself.“Not Disabled Enough” by Jamieson Wolf

More recommended sites:

Deafinitely WanderlustUnpacking Disability Have Wheelchair Will TravelLeaving EvidenceSimply EmmaGin & LemonadeAutistic Collaboration

Note on header image: Six disabled people of color smile and pose in front of a concrete wall. Five people stand in the back, with the Black woman in the center holding up a chalkboard sign that reads, “disabled and HERE.” A South Asian person in a wheelchair sits in front. Photo by Chona Kasinger | Disabled and Here (CC BY 4.0)
Quelle: RedHat Stack

Run With Us! Join the 2020 wwwp5K Movement

If you’re like us, you’re eager to send 2020 off to the dustbin of history. So grab your running/walking/yoga shoes and join us as we resurrect the historic #wwwp5K and celebrate reaching the 2020 finish line! As an added incentive and in the spirit of the season, we’ve also created a special wwwp5K Givz page, where participants can make a donation to three of our favorite charities: Black Girls Code, Internet Archive, and the WordPress Foundation. Automattic will match every dollar donated to any organization through the Givz page, up to $50,000.

What’s a 5K?

A 5K is the equivalent of about 3.1 miles. The virtual run will work on the honor system, but if you want to be accurate, apps like Strava, Garmin Connect, Runkeeper, Fitbit, and many others can help you measure the right distance.

Sounds awesome! How do I participate?

The virtual wwwp5K officially kicks off tomorrow, December 1, and will be open through December 31st. You can run, skip, walk, hop, walk backwards, or even swim the equivalent distance in an indoor pool — as long as you’re practicing appropriate safety precautions given local conditions and staying healthy, your activity counts.

Everyone is welcome! WordPress fans, friends, and family, as well as Automatticians around the world.

When you’re done, don’t forget to post a selfie on your WordPress site and tag it with “wwwp5k” so that we can share the love and others can read about your experience. Of course, you can also blog about your journey preparing for the wwwp5K, but most of all, we’d love to see your smiling face and happy shoes as you complete the 5K.

Is there swag?

What would a virtual run be without swag with a custom logo? To commemorate the 2020 run, we’ve created a limited edition technical shirt featuring the official wwwp5K Wapuu!

They’ll be available for purchase in the WordPress Swag Store starting tomorrow until supplies last, so don’t forget to place your order.

Will you be joining us? Let us know in the comments!
Quelle: RedHat Stack

How to set up k0s Kubernetes: A quick and dirty guide

The post How to set up k0s Kubernetes: A quick and dirty guide appeared first on Mirantis | Pure Play Open Cloud.
For a couple of weeks now, we’ve been talking about the k0s project, a simple way to get Kubernetes up and running.  In this quick and dirty guide, we’ll give you all the background you need to get started.
The Kubernetes architecture of k0s consists of a single binary that includes everything you need to run Kubernetes on any system that includes the Linux kernel.  Putting it to use is straightforward:

Download the k0s binary
Create a server to instantiate the Kubernetes control plane
Create a Kubernetes worker
Access the cluster

Of course you can add additional controllers or servers, but let’s start with the very simplest version:  a single server running everything you need.
Create a single node Kubernetes cluster with k0s
The first thing we need to do is create a server that will act as the k0s controller.  Note that I didn’t say controller node; you can see Jussi Nummelin’s blog for an explanation of the particular way in which k0s implements the Kubernetes architecture, but the controller processes run directly on the host, and not in pods, so there’s no “master” node.
The host itself doesn’t have to be huge; for this blog I used an AWS t2.medium instance (2 CPUs, 4GB RAM) running Amazon Linux 2.  Just make sure that port 6443 is open so that you can contact the cluster later.
Now you can install k0s with a simple one line command:
sudo curl -sSLf k0s.sh | sudo sh
(Note that there’s no “magic” k0s.sh script you’re missing.  This is the same as sudo curl -sSLf http://k0s.sh | sudo sh)
Once the script downloads, all you need to do is start the server:
sudo k0s server –enable-worker &
That’s it.
You can avoid getting bowled over with logging messages by instead using:
sudo k0s server –enable-worker </dev/null &>/dev/null &
You could also start just the server and create the worker somewhere else, but we’ll talk more about that in a minute.  Now let’s access the new cluster.
Access the k0s cluster
Accessing the cluster is a matter of simply installing kubectl (if necessary) and pointing to the KUBECONFIG file.
When you create the server, k0s creates a KUBECONFIG file for you, so copy it to your working directory and point to it:
sudo cp /var/lib/k0s/pki/admin.conf ~/admin.conf
export KUBECONFIG=~/admin.conf
Now you can access the cluster itself:
kubectl get namespaces
NAME              STATUS   AGE
default           Active   5m32s
kube-node-lease   Active   5m34s
kube-public       Active   5m34s
kube-system       Active   5m34s
Notice that if you look for the nodes, there is no master node:. Remember, k0s implements the control plane as naked processes.
kubectl get nodes
NAME             STATUS   ROLES    AGE    VERSION
ip-172-31-8-33   Ready    <none>   5m1s   v1.19.3
But what happens if we try to access the cluster from another server, such as via a tool such as Lens?
Accessing k0s from outside the cluster: Customizing the k0s Kubernetes cluster
Now let’s look at accessing the cluster from an external server.  We can easily get the KUBECONFIG file:
scp -i k0s.pem ec2-user@<SERVER_IP>:~/admin.conf .
export KUBECONFIG=admin.conf
From there, we’ll want to use the public IP address of the server rather than localhost, so open the admin.conf file and edit the server address.  For example, in my case, the public IP of my server is 52.10.92.152:
apiVersion: v1
clusters:
– cluster:
server: https://52.10.92.152:6443
certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURBRENDQWVpZ0F3SUJBZ0lVRzhGakJZVVNZOFBrOWNjcTVhK3lFenNBNXAwd0RRWUpLb1pJaHZjTkFRRUwKQlFBd0dERVdNQlFHQTFVRUF4TU5hM1ZpWlhKdVpYUmxjeTFqWVRBZUZ3MHlNREV4TWpNd016TXpNREJhR…

Now if we were to test this connection, we’d see something odd.
kubectl version
Client Version: version.Info{Major:”1″, Minor:”19″, GitVersion:”v1.19.0″, GitCommit:”e19964183377d0ec2052d1f1fa930c4d7575bd50″, GitTreeState:”clean”, BuildDate:”2020-08-26T14:30:33Z”, GoVersion:”go1.15″, Compiler:”gc”, Platform:”windows/amd64″}
Unable to connect to the server: x509: certificate is valid for 127.0.0.1, 172.31.8.33, 172.31.8.33, 172.31.8.33, 10.96.0.1, not 52.10.92.152
So we’re making the connection, and Kubernetes is working, but the credentials are incorrect.  To solve this problem, we need to configure k0s to include the public IP address.
To start, we can export the actual configuration file k0s will use:
sudo k0s default-config > k0s.yaml
We can then edit that file to add the public IP, and any other address at which we want to call the server:
apiVersion: k0s.k0sproject.io/v1beta1
kind: Cluster
metadata:
name: k0s
spec:
api:
address: 172.31.8.33
sans:
– 172.31.8.33
– 172.31.8.33
– 52.10.92.152
extraArgs: {}
controllerManager:
extraArgs: {}
scheduler:
extraArgs: {}
storage:
type: etcd
kine: null
etcd:
peerAddress: 172.31.8.33
network:
podCIDR: 10.244.0.0/16
serviceCIDR: 10.96.0.0/12
provider: calico
calico:
mode: vxlan
vxlanPort: 4789
vxlanVNI: 4096

Next restart the k0s server. Because it’s running as a background process, the easiest way to do this is to simply restart the machine, then restart k0s:
sudo k0s server –enable-worker &
From here everything should Just Work; the KUBECONFIG file stays the same:
kubectl version
Client Version: version.Info{Major:”1″, Minor:”19″, GitVersion:”v1.19.0″, GitCommit:”e19964183377d0ec2052d1f1fa930c4d7575bd50″, GitTreeState:”clean”, BuildDate:”2020-08-26T14:30:33Z”, GoVersion:”go1.15″, Compiler:”gc”, Platform:”windows/amd64″}
Server Version: version.Info{Major:”1″, Minor:”19″, GitVersion:”v1.19.3″, GitCommit:”1e11e4a2108024935ecfcb2912226cedeafd99df”, GitTreeState:”clean”, BuildDate:”2020-11-11T20:21:36Z”, GoVersion:”go1.15.4″, Compiler:”gc”, Platform:”linux/amd64″}
You can also access the Kubernetes cluster with Lens by importing the KUBECONFIG.
Add additional nodes to the Kubernetes cluster
Scaling the cluster is just a matter of adding additional worker nodes or control planes. To do that, you’re going to need a token so the new server knows where to “phone home”. To generate that, go to the control plane:
k0s token create –role=worker
Obviously, in this case we’re creating a new worker node.  You’ll wind up with a really long string of text such as:
H4sIAAAAAAAC/2yV0Y7iOhKG7/speIGZYycwpxtpLyZgBwIxY8dlJ74LcYZAnBBCGtKs9t1XzcxIu9K5K1f9+n7Lsup/ybujKvvr8dzOJzf8Urj361D21/nLl8nvev4ymUwm17K/lf18Ug1Dd53/9Rf+2/vq46+vX31//m069Z+iouyH489jkQ/ll/x9qM79cfj4YvMhn0+2CRq2CV4IsJE8BkuhIkjARBxREM8ZGhY1jhIQgSBsybXqDKJ+AlFgkFPiUYV5HRmlmNnRoN9pdiqkqja+o2XLApZ+v1skhIZuu8ddlK/MSdZUCLhvuKOBRZYIZRl3dMUlVQLoVMKsirHptKs2VnUZNOOplPSilQgMGD9eOSaImkrdMYvwN5l2TJCoEm1xLw/dnxn935mEqC2JuXClFgbNNK8pU0SkdknNXplZ1mAd0y6TqTBxrXzjWZoDDmJil+DT1cKxKDsxAqAWXFHFgaAEImIRfWoTRG+fbwIgNuJUj4k2Yo/GSwzFQ5Ea21ZV3DdqJ6000rV5YxIFh41Br57Ba79MFTXSabuk5zxUZ5nG9xyGkyDTMVHfe1YrY0IcMXe4JSSiuXIKlhHOkIEyZKBSg8BxnD/Mujyc77BSjx3N+iKluVTnj3gVxBqmvvGpA1dgvXRLvYp7mYohTxnX4YjzU7RV3ut9j88986b3Ag0CMGNlas+2ji6LpvA2XpUomX2opTE2HJZlSo86XE/F8TruqHvfEZpmzYzJZjzHYOKSBlJoK/K22pQy7uNavPNH5vPU1SDXnsDFJoHDNCe4YvUbk+HhpkI+TaRI9aprdaN2GV57WetcDEWfLzOUeW871bzds1MQ5pDdWWqrzUPFWw/PRBtFW4+J/HsHVkbpHhSTsJ7tidMljQabKmN0NLNt8MOc3FWmNMlQtEjUYcz8SNnQcBMKynyC42X0zrVlvKaB8DqR11GwqHHAiA1ipWqxspQf33wAFVjkFrzpAiBRK51ZQ40XXGdTARFwEAHA4SZhfReIjEoLYjBNeR2B1vG0COtNvhIQO3HM0niqaJerlE/L5hWXZNorQne8sX2hqz6HYmYfwecffIiaBhKx4NM/98+ocGvPtsGuOA5Ek1mjDt2Ce+NHhkRrH8zFyjUK22P2MXgQ2ladTMZTty5OgnKotCbDKFJz2hM1JqvgaFD30ErdsjS7m4fd7pYCWczWi5MZEvJm2GIIslZxtjSyeAhPhfHNYuILNDttUYUV5ahsA1FqGPWK+rIRIDxbs1asi1YEpol6CKuLaSgkTbbJfSvLpR2s300zn8LeZzf5cLdd6pgO6WVP7h97sKMljoJUs7zmD4nED+1oLGp6grDok6UxQNmHQviy02tPfe9kTsa7BJtlaTHdNxneK/deoA52cL1tvegae2+UUbvereBum8IT8HaL26CRtUmVDC5GsiYmHS1klTJZjDtpr4vm9RajyN/iIGLp4WFOxlmCRrMUUxsO25KwXqRUJ83IchJhaCqyRdW3QkcO2i4FhO7xyhL14A+r3yIZWpw0fLMPVZVj5f+QaPN7N1NZ8wNHKlHEhQmwQBF47uUtP//rZTJp86acT2p0fSnO7VCOw6+Y+FX/iok/mfFUfTber8/T+7505fBlfz4P16HPu/+nvfd92Q5f/pCezfrY2vlkcW5/Hg8vXV/+LPuyLcrrfPLv/7x8Up/mvyH/gH8aP68wnOuynU9qN15n+Ovl56OyaLj8ffC+9f3x9PLfAAAA////I+m0AwcAAA==
This may seem excessive, but this is actually just a KUBECONFIG that’s been BASE64-encoded. The benefit here is that you can put the worker node anywhere, as long as it can access the control plane over the network.
To create the worker, instantiate a new server (if necessary) and install k0s:
sudo curl -sSLf k0s.sh | sudo sh
Then just go ahead and join the cluster:
sudo k0s worker “long-join-token”
As in:
k0s worker “H4sIAAAAAAAC/2yV0Y7i…”
Now if you were to go back to kubectl and check for nodes, you’d see the new node in your list, as in:
kubectl get nodes
NAME               STATUS   ROLES    AGE   VERSION
ip-172-31-14-157   Ready    <none>   81s   v1.19.3
ip-172-31-8-33     Ready    <none>   11h   v1.19.3
You can also increase the robustness of the cluster by creating an additional control plane.  Again, start by creating the token:
k0s token create –role=controller
And again, on your new server, install k0s and start the server just as you started the worker:
sudo curl -sSLf k0s.sh | sudo sh
sudo k0s server “long-join-token” &
As in:
sudo k0s server “H4sIAAAAAAAC/3RV0Y…” &
This time, though, if you check for nodes, you won’t see the addition, because there are no master nodes in the k0s Kubernetes architecture:
kubectl get nodes
NAME               STATUS   ROLES    AGE   VERSION
ip-172-31-14-157   Ready    <none>   23m   v1.19.3
ip-172-31-8-33     Ready    <none>   11h   v1.19.3
Note that until the community creates a command for leaving the cluster (currently in progress) if something happens to your second controller, the cluster itself will be borked, so don’t add this unless you need to.
Where to go from here
k0s is exciting, but it’s still pretty young, so work is simultaneously very fast but the community would very much like any feedback or contributions. Meanwhile, we’d like to hear when you’re doing with k0s, and what you’d like to see us talk about, so let us know in the comments!
The post How to set up k0s Kubernetes: A quick and dirty guide appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

Join Us in Honoring Transgender Day of Remembrance

Today, November 20th, people around the world pause to bear witness to Transgender Day of Remembrance, a day dedicated to honoring the memory of those murdered because of anti-transgender prejudice. Transgender Day of Remembrance reminds us to fight against forces that devalue transgender lives every day. To bring awareness to this important day, we want to pause to share a few stories of transgender people who have found their voice on WordPress.com. We posed a question: “What does Transgender Day of Remembrance mean to you?” Below, we’ve shared a few responses from creators on our platform.

We welcome you to share your own response on your site. In the meantime, read slowly and soak in the hard-fought words of the brave voices who are willing to share their experiences. 

Dr. SA Smythe (They/Them) of essaysmythe.com:

Some of us have been counted, but most of us are counted out—unthought and unthinkable. And so we do it ourselves. We account for Tony McDade. We are accountable to Muhlaysia Booker. We recall Riah Milton. We recollect the fierce life of one of our greatest contemporary remembrancers, the trans griot Monica Roberts. We name the nonbinary people who continue to be treated as unnameable as we slip through the matrix of binary gender. The competing racialized pandemics of our time continues to be intensified for trans people, especially Black trans women, in this year as with any other. We live with that reality and demand non-trans people do the same because our resilience is nothing without their reckoning for the violence they allow to continue against us. Trans Day of Remembrance is not only about how trans people have been stolen from us too soon, but how we continue to survive and thrive and persist against all odds. Has there ever been anything as beautiful as that?Read more

Laura Kate Dale (She/Her) of laurakbuzz.com:

Going and spending some time in the company of other trans people was wonderful. I got to see trans people from a variety of backgrounds, some who had grown old and found love, and see proof that I could live a long and happy life as a trans woman. But the tone of the evening was contrasted by sitting with the knowledge of why we were all gathered, the knowledge of far too many lives cut far too short. I was surrounded by the trans people who had survived and thrived, as well as the memories of those who had not.Read more

Nicole Eldridge (She/Her) of transgendersupport.org:

My name is Nicole Eldridge. I’ve been transgender since third grade. As I started to transition, I would read stories online about transgender people dying. This is absolutely terrifying if you want to do what they did. I never gave up and transitioned. Transgender Day of Remembrance means to me that we remember the transgender people that have died and carry out their goal of an equal future for all transgender people. Every time I listen to a Transgender Day of Remembrance speech, it brings me back to Martin Luther King’s speech, “I Have a Dream.” What King said about everyone being equal and having equal opportunities is so true when I hear the transgender people’s names who have died. It breaks my heart to hear all of the transgender people that died for the year. In spite of the hatred toward transgender people, I rise above it all and help transgender people all over the world with my website transgendersupport.org. This is what Transgender Day of Remembrance means to me.

Tallulah Ker-Oldfield (She/Her) of transrites.wordpress.com

Trans people are nothing new. Gender and its expressions have been changing throughout cultures, and trans people have existed throughout history with notable examples in the many ancient pantheons, including deities. There’s nothing new to consider, no trans question – we’ve been here all along, and the only terrible things that happened because of it happened to us… ***And so I’m remembering trans lives lost this year, and trans lives filled with trauma, and everything that trans people have to do to simply… be. If you ever thought this year was scary, oppressive, isolating, challenging to get through and potentially fatal to be around people… you’ve been living a lot of the worst parts of the trans experience. Yet I’m remembering the powerful joy of my community, how our bonds through the pandemic have been strong, how well accustomed we immediately became to 2020, having lived our own version of it for most of our lives, creating found families, love, laughter, understanding and sometimes rainbows out of the unforgiving raw material of compromise.Read more

To read more writing by transgender people, explore these sites on WordPress.com:

letsqueerthingsup.comautistichoya.nettransprov.wordpress.comgendermom.wordpress.com

We pride ourselves on being a platform where anyone can share their perspective, and we’re honored to be able to create a space for the personal stories of transgender-identifying individuals. Take the time to read their words and remember that it’s not enough to honor transgender people just one day each year. What we do matters every day. Follow these sites and others you come upon and, as a result, show your support in the days to come. 
Quelle: RedHat Stack