Most people avoid criticism. I did the opposite.

I asked AI to give me an unfiltered assessment of myself—no ego, no politics, no spin.

The verdict?
Brutally honest. Occasionally funny. Sometimes uncomfortable. And annoyingly accurate.

Interest

Here’s a sample of what AI had to say about me:
➡️ “You’re a strategist, not a coder.”
➡️ “Your work is invisible until it fails.”
➡️ “You balance cost, speed, scalability, and security daily (and it’s as fun as it sounds).”

At first, I laughed. Then I winced. Then I realized: these reflections weren’t just true about me—they captured the reality of Enterprise Architecture itself.

Take a few examples from my own work:

• Strategic Thinking > Firefighting
  At my organization, I’ve focused on long-term positioning instead of chasing today’s quick fixes.

  One example: When evaluating cloud solutions, I resisted the temptation to optimize for immediate convenience. Instead, I pushed for designs that avoided vendor lock-in — using standards and portable integration patterns so we wouldn’t be boxed in later. That foresight preserved flexibility and negotiating power.

  Another: Rather than cranking out one-off reports to satisfy immediate demands, I governed and steered a global data strategy. By aligning models, pipelines, and governance, we built a foundation leaders can trust. It took more effort upfront, but it prevented the chaos of conflicting numbers and gave us enterprise-wide insights.

• Governance Without Bureaucracy
  Governance doesn’t have to mean red tape. When we set up the global architecture governance forum and introduced RACI models, it wasn’t about adding hurdles—it was about speeding up decision-making and giving teams clarity.

• Truth Over Comfort
  During our legacy-to-modernization discussions, I had to say the unpopular thing: leaving old platforms “as-is” might save time now, but it would cripple us in the future. That wasn’t the message people wanted—but avoiding millions in wasted investment was worth the discomfort.

• Long-Term Value > Short-Term Wins
  I’ve pushed for embedding AI-first practices into our daily workflows—from ServiceNow ticket generation to AI-powered FinOps analysis. It felt disruptive at first, but now AI is part of how we operate, saving time and boosting accuracy.

• Translation, Not Jargon
  Architecture diagrams and frameworks mean little if they stay abstract. My role has been to make them real.

  When we scaled our Kubernetes clusters globally, I didn’t tell leadership about “node classes, Ceph OSD tuning, or container orchestration.” Instead, I explained it as:

  • “This design keeps shipments moving even if a data center goes down.”
  • “This approach avoids millions in future cloud overspend.”
  • “This is how we make sure AI workloads don’t collapse when volume spikes.”

  That translation mattered. Engineers saw the technical depth, but executives saw customer impact, cost control, and resilience. That’s how EA avoids being “ivory tower” — by making architecture outcomes tangible.

Brutal Reflection (Straight from the AI)

Here’s the part that stung a little—but rang true:

• “You’re a strategist, not a coder.”
  Fair. My value isn’t in patching microservices; it’s in ensuring we don’t build the wrong thing to begin with.
• “Your work is invisible until it fails.”
  Exactly. Few people think about the hundreds of nodes, thousands of containers, terabytes of storage in our clusters—until something goes down. Then everyone remembers.
• “You balance cost, speed, scalability, and security daily.”
  Dead on. It’s a constant tension: FinOps pushing for efficiency, business demanding speed, tech needing scalability, and security reminding us of guardrails. Some days it’s a high-wire act—but it’s also what keeps us resilient.
• “You’re operations minded.”
  True—but that doesn’t mean I work in operations. My role isn’t to run systems day-to-day. It’s to design so operations can succeed: stable platforms, clean handoffs, and scale that doesn’t collapse under pressure. Operations runs the train; I make sure the tracks don’t crumble a year from now.

Desire

Why does this matter? Because Enterprise Architecture isn’t about me—it’s about protecting and enabling the whole organization.

• It prevents tomorrow’s crises before they start.
• It helps teams avoid reinventing the wheel (and duct-taping it badly).
• It gives leaders confidence that technology isn’t just aligned with strategy—it’s driving it.

But architecture doesn’t work in isolation. It only works because of the engineers, analysts, operators, and leaders who bring it to life. My role is to make sure their work scales, lasts, and connects to the bigger picture.

And that’s exactly what AI reminded me: sometimes the hardest truths about yourself are also the clearest truths about your role.

Action

So here’s my challenge to you:

If you asked AI to describe your values at work—what would it say? Would you agree with it? Would you want to read it?

A Little Humor Helps

🚀 This Isn’t a Thought Experiment — It’s Our Daily Reality

Last Tuesday, one of our developers used AI to write API documentation. He shaved off three hours of work — not by cutting corners, but by focusing on what actually matters.
And he wasn’t an outlier.

At the organization I work for, moments like that happen every day. Not in a lab. Not on a roadmap. For us, AI-first isn’t a talking point — it’s how we work. A mindset we bring into meetings, projects, goal-setting, even how we reflect at the end of each week.

We didn’t start with a massive plan. We started with a single question — one we now ask every week:

“What did you rethink with AI this week?”

That question is our quiet revolution. It challenges people to look at their day-to-day with fresh eyes. And that small shift? It changes everything.

🧠 Understanding AI: Let’s Get Real

If we’re going to live and breathe this, we need clarity.

Most of what we call AI today — the tools we actually use — fall under “weak AI.” That’s not an insult. It means these systems are built to handle specific tasks: summarizing documents, rewriting code, analyzing patterns. They don’t think — but they get results.

“Strong AI,” the stuff of movies and late-night debates, doesn’t exist yet. And honestly, we’re not worried about it. What we have today is enough to transform how we work — if we’re brave enough to use it.

AI is like a power tool in your hand. It doesn’t replace the craftsperson — it sharpens their edge.

🔧 Everyday Use Cases of Weak AI

🔁 What They All Have in Common

• Focused intelligence — Optimized for one task
• No real “understanding” — Doesn’t reason like a human
• Human-in-the-loop — Needs prompts, review, and validation
• Limited scope — Can’t adapt outside their domain

🔥 How We Made AI Part of Our Culture

What made this real for us wasn’t a memo. It was action — repeated, simple, human action.

I didn’t just endorse AI — I used it, and I shared examples in team meetings. That made it safe for others to try. More importantly, we built a space where trying something new (and maybe failing) wasn’t just accepted — it was encouraged.

Every time someone said, “Hey, I used AI for this and it saved me an hour,” they shared it. That’s how culture shifts — not with banners, but with courage.

📍 Real Stories from Inside Our Team

These aren’t initiatives. They’re habits. This isn’t theory — it’s how we work.

🎓 Learning by Doing

The organization I work for sent me through Tangram AI training — not just slides and a certificate, but 12+ hours of pre-work and five intense days of hands-on labs. I came back energized, not just informed. Because when leaders feel it, they spread it. What you cannot see in the photo is the team was operating trucks, managing paperwork, and moving containers from trucks to ships all with our hands!

💻 Coding with a Second Brain

In development, AI became a co-pilot — helping us write code, document changes, and build smarter. I mentioned an example at the beginning of this article.

🗂️ Rethinking Goals, Together

When it came time to write team goals, we didn’t start from scratch. We used large language models to draft, edit, and refine. The result was clear, collaborative, and aligned — not just approved.

🧠 AI in the Background — Quietly Powerful

In operations, AI became an invisible helper. It pulled insights from emails, created executive summaries, even opened ServiceNow tickets. Hours saved. Clarity gained. Here’s and example prompt you can try:

“Need a brilliant presentation about how to use ServiceNOW as not only a support tool but also a knowledgebase. This should include cool meaningful pictures and artwork including an inspirational Video at the end!”

💰 Smarter FinOps

We use AI to break down Kubernetes costs, assist with chargebacks, and guide teams toward better architecture. It’s like having a CFO and cloud engineer in your pocket — running 24/7.

🔬 Decision-Making on Another Level

When weighing canonical vs. unstructured data models, AI didn’t make the decision — but it surfaced the insights that mattered. It filtered articles, decks, and discussions — turning noise into clarity.

❗ The Truth: AI Isn’t Coming for Your Job

Let’s kill the fear-mongering. AI isn’t here to take your job — it’s here to take the junk work off your plate.

What’s really at stake? Your time. Your focus. Your ability to do your best thinking.

The real threat isn’t AI. It’s the person next to you who’s figured out how to use it — and now gets more done, with better insight and less stress.

Use it to:

• Automate grunt work — so you can focus on strategy
• Accelerate decision-making — with faster, clearer inputs
• Amplify your strengths — by offloading the robotic tasks

Start small. Pick one task this week to rethink with AI — and reclaim your edge.

🎯 Final Thought: This Isn’t About Tools. It’s About Trust.

At the organization I work for, AI isn’t future-facing — it’s already part of how we work. Every day. In real ways.

It’s not perfect. Neither are we. But when we use AI consistently, we’re not just saving time — we’re creating space to think, lead, and connect.

This isn’t humans vs. AI. It’s humans with AI — thinking bigger, working better, growing faster.

👋 Want to Start?

In your next team meeting, try asking: ‘What did you rethink with AI this week?’ It won’t just change the conversation — it might change your culture.

Quick and Easy guide to Beeline shortcuts for kubectl

I absolutely love open-source and believe 100% that it’s the best way to develop software. In the last few years I dedicated and invested much of my time in Kubernetes and containerization. I love working with the command line. Seriously I don’t think there is a more effective way to interact in a computing environment for development, administration or just outright tinkering. Don’t get me wrong, I have nothing against UI/GUI and they are great in a pinch and a great way to familiarize yourself with an application. I use kubectl quite extensively and eventually the typing becomes a bit exhausting for repetitive tasks. There are lot’s of extensions available for kubectl but I wanted to create something straight forward and easy to use and even extend if you want to. It’s called Beeline and it is a number of shortcuts and aliases for zsh and bash. It was designed to use on the command-line, integrated with autocomplete, and also in a bash script that is easy to read and follow for many procedural tasks like installing a helm chart.

This post will give you the same two minute introduction about Beeline and its possibilities, followed by the typical 10 minute hands-on guide to set up and get to know Beeline yourself. If you’ve got 10 minutes to spare and finally want to be more proficient with Beeline: read on! Otherwise, if you already use zsh and already installed oh-my-zsh, just us the /quick primer/

TLDR; This is the lazy version. . .

#####  Setup Beeline

## Defaults if you like
export KS_CONTEXT='cities'
export KS_NAMESPACE='kube-system'

[[ ! -f ~/.beeline.k8s ]]  \
&& curl -s -L https://github.com/262life/beeline/releases/latest/download/beeline.sh  > ~/.beeline.k8s

source ~/.beeline.k8s
##### End of Beeline

That’s it. Type kh to get a list of shortcuts.

Full Installation

To use the shortcut scripts it is required that you have setup either bash or zsh completion in advance. Beeline will enable kubectl’s auto completion on your behalf.

Installing ZSH

This has been tested on macOS, Ubuntu, and Windows WSL2.

I highly recommend changing your login shell to zsh. It is now the macOS default. For Ubuntu or WSL2, the following will install zsh. If prompted, choose any defaults.

sudo apt install zsh

and to enable autocomplete for zsh on all of the supported environments, install oh-my-zsh as follows:

sh -c "$(curl -fsSL https://raw.github.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

To enable these shortcuts you must source them into your shell. This is dependent on the shell you are using. You can either download the desired version you would like or if you are lazy like me do something like this if you use zsh:

#####  Setup Beeline

## Defaults if you like
export KS_CONTEXT='cities'
export KS_NAMESPACE='kube-system'

[[ ! -f ~/.beeline.k8s ]]  \
&& curl -s -L https://github.com/262life/beeline/releases/latest/download/beeline.sh  > ~/.beeline.k8s

source ~/.beeline.k8s
##### End of Beeline

Take note to edit the KS_CONTEXT and KS_NAMESPACE values to your liking.

Restart your shell and you should be good to go!

Now, review the usage documentation

Getting started with Beeline

At the heart of Beeline are the two most important and essential shortcuts; kc and kn. These control the context of the session you are in. Wait? Did I say session? kubectl sets the contexts in the config file and if multiple windows are open as the same user, it’s shared right? Well with Beeline that is not the case! You can have multiple windows open or even multiple shells and the context stays with the current shell! Cool right?

Example:

[B:cities:kube-system] liottar:/Users/liottar$ kc cities rook-ceph
Context "cities" modified.
Property "current-context" set.
[B:cities:kube-system] liottar:/Users/liottar$ kn kube-system

Cluster    : Cities Cluster / Location: St. Augustine FL
Context    : cities
Namespace  : kube-system

Context "cities" modified.
Property "current-context" set.

About the config files

If you have a number of kubernetes clusters to manage like I do, one of the more complicated aspects of kubectl becomes managing the config files. This file can become long and extremely hard to read even for expert users.

Beeline takes care of this allowing you to keep a separate config file for each cluster like this example:

apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: LS0tLS1CRUdJTiBDRL35SUZJQ0FURS0tLS0tCk1JSUJlRENDQVIyZ0F3SUJBZ0lCQURBS0JnZ3Foa2pPUFFRREFqQWpNU0V3SHdZRFZRUUREQmhyTTNNdGMyVnkKZG1WeUxXTmhRREUyTWpBMk5UUTBNall3SGhjTk1qRXdOVEV3TVRNME56QTJXaGNOTXpFd05UQTRNVE0wTnpBMgpXakFqTVNFd0h3WURWUVFEREJock0zTXRjMlZ5ZG1WeUxXTmhRREUyTWpBMk5UUTBNall3V1RBVEJnY3Foa2pPClBRSUJCZ2dxaGtqT1BRTUJCd05DQUFSaTJmSDNJY3QzZS9VSUtaS2hFOVRQeVJBYVBnNzRuY1VxQUlCUVI5YmYKMGJNaFpUVVhlWjhnUnRNZVFwY1lqZ1pHWEtXZVV5SW5LZFBmYlZuMU4zazhvMEl3UURBT0JnTlZIUThCQWY4RQpCQU1DQXFRd0R3WURWUjBUQVFIL0JBVXdBd0VCL3pBZEJnTlZIUTRFRmdRVTZkVWdqU1BuQU83OGpqYm9WVlJWCm1BV1BMVjB3Q2dZSUtvWkl6ajBFQXdJRFNRQXdSZ0loQUtMT0Ivd2hpQmJFd2prUE5wQ0VqZTFnYWM4Z3hZS2QKSWdKOFB6QUFzQkJ0QWlFQXU5TWw0R0wxN1ZPNEk3L0FRWmVBUnJQK3JxVlpzR3crMzBWbHVlMGtXakU9Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
    server: https://cluster.internaldomain.com:6443
  name: cities
contexts:
- context:
    cluster: cities
    namespace: 
    user: cities
  name: cities
current-context: cities
kind: Config
preferences: {}
users:
- name: cities
  user:
    client-certificate-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1J3X4rVENDQVRlZ0F3SUJBZ0lJY05rbFVtTUcwL1l3Q2dZSUtvWkl6ajBFQXdJd0l6RWhNQjhHQTFVRUF3d1kKYXpOekxXTnNhV1Z1ZEMxallVQXhOakl3TmpVME5ESTJNQjRYRFRJeE1EVXhNREV6TkRjd05sb1hEVEl5TURVeApNREV6TkRjd05sb3dNREVYTUJVR0ExVUVDaE1PYzNsemRHVnRPbTFoYzNSbGNuTXhGVEFUQmdOVkJBTVRESE41CmMzUmxiVHBoWkcxcGJqQlpNQk1HQnlxR1NNNDlBZ0VHQ0NxR1NNNDlBd0VIQTBJQUJENEJrczQwK00xZjJLUkcKLzdHR2tHZkNVOWdUT2JKeDZxVEdVbG9TSzZha3htcmwzaEdTb2FKbjc1S1F4OWw2cW5aZFJmWmFSazN2NnZEUQpCeXhtU0NLalNEQkdNQTRHQTFVZER3RUIvd1FFQXdJRm9EQVRCZ05WSFNVRUREQUtCZ2dyQmdFRkJRY0RBakFmCkJnTlZIU01FR0RBV2dCVEVzT1pPU2VnMDh6OTNSVFhob1g3SmVwVG9mekFLQmdncWhrak9QUVFEQWdOSUFEQkYKQWlFQXEwVmhyTXpnVk80WDYyWDg1QXBNZ1haa0EwTE11NUFNWitRTlBZaGVLOTRDSUM3N0RpTVlXQXlXZFdkcQoydjZpdGZJeDhqbTl6d0JldXFTTjd3TzJYKzBsCi0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0KLS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJkakNDQVIyZ0F3SUJBZ0lCQURBS0JnZ3Foa2pPUFFRREFqQWpNU0V3SHdZRFZRUUREQmhyTTNNdFkyeHAKWlc1MExXTmhRREUyTWpBMk5UUTBNall3SGhjTk1qRXdOVEV3TVRNME56QTJXaGNOTXpFd05UQTRNVE0wTnpBMgpXakFqTVNFd0h3WURWUVFEREJock0zTXRZMnhwWlc1MExXTmhRREUyTWpBMk5UUTBNall3V1RBVEJnY3Foa2pPClBRSUJCZ2dxaGtqT1BRTUJCd05DQUFUMG5oUXIwNWpqa3RrSmVZMXJUUGN3T2poWXpCTk92dnZyT1hLdU9hTmMKSWFyYVMxV1Zibmthb1NJRW40OGNmVmdmUmNlcGw3Y0kvT3ltajA1Y3dYWjNvMEl3UURBT0JnTlZIUThCQWY4RQpCQU1DQXFRd0R3WURWUjBUQVFIL0JBVXdBd0VCL3pBZEJnTlZIUTRFRmdRVXhMRG1Ua25vTlBNL2QwVTE0YUYrCnlYcVU2SDh3Q2dZSUtvWkl6ajBFQXdJRFJ3QXdSQUlnSjBiRlVmUk5tRE15WjUzRFpnRllLWWNLTitlelhOSVcKMVRSTkdDcWZ3NzBDSUVDTitiOTJva0NSYUtGeFlVcE4xYW1NMmoyMjd6NGdaenZYUDNibWR4eEUKLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=
    client-key-data: LS0tLS1CRUdJTiBFQyBQUklWQVRFIEtFWS0tLS0tCk1IY0NBUUVFSU02dS9DaExlZkx0AHNrcGI2ZHMveFQxQlVsdGVzZFB0ZkxXNUFOZEVLSmZvQW9HQ0NxR1NNNDkKQXdFSG9VUURRZ0FFUGdHU3pqVDR6Vi9ZcEViL3NZYVFaOEpUMkJNNXNuSHFwTVpTV2hJcnBxVEdhdVhlRVpLaApvbWZ2a3BESDJYcXFkbDFGOWxwR1RlL3E4TkFITEdaSUlnPT0KLS0tLS1FTkQgRUMgUFJJVkFURSBLRVktLS0tLQo=

As you can see, it’s easy to read as a single YAML file therefore quote effect. How do you make use? Just add one or many of these files one for each cluster in your $HOME/.kube file and give it a .cfg extension and that’s all you need to do. Beeline will take care of the rest.

Note: Do NOT remove the config file as it will be used as well.

Practical Examples

Set context and namespace

[B:cities:kube-system] liottar:/Users/liottar/projects/262life/beeline$ kc cities rook-ceph

Cluster    : Cities Cluster / Location: St. Augustine FL
Context    : cities
Namespace  : rook-ceph

Context "cities" modified.
Property "current-context" set.
Context "cities" modified.
Property "current-context" set.
[B:cities:rook-ceph] liottar:/Users/liottar/projects/262life/beeline$

Get context and namespace

[B:cities:kube-system] liottar:/Users/liottar$ kc

Cluster    : Cities Cluster / Location: St. Augustine FL
Context    : cities
Namespace  : kube-system

Context "cities" modified.
Property "current-context" set.

Get all pods with wide output

[B:cities:rook-ceph] liottar:/Users/liottar$ kgp -owide
NAME                                                     READY   STATUS      RESTARTS   AGE   IP              NODE       NOMINATED NODE   READINESS GATES
csi-cephfsplugin-2xt6f                                   3/3     Running     3          55d   192.168.1.241   moscow     <none>           <none>
csi-cephfsplugin-provisioner-78d66674d8-fxkk4            6/6     Running     0          55d   10.42.2.11      florence   <none>           <none>
csi-cephfsplugin-provisioner-78d66674d8-qqvvh            6/6     Running     0          55d   10.42.0.20      miami      <none>           <none>
csi-cephfsplugin-rhsj2                                   3/3     Running     3          55d   192.168.1.243   miami      <none>           <none>
csi-cephfsplugin-sgwmj                                   3/3     Running     3          55d   192.168.1.242   florence   <none>           <none>
csi-rbdplugin-68x8h                                      3/3     Running     3          55d   192.168.1.243   miami      <none>           <none>
csi-rbdplugin-j5sqc                                      3/3     Running     3          55d   192.168.1.242   florence   <none>           <none>
csi-rbdplugin-m5ccj                                      3/3     Running     3          55d   192.168.1.241   moscow     <none>           <none>
csi-rbdplugin-provisioner-687cf777ff-4t8cv               6/6     Running     6          55d   10.42.1.131     moscow     <none>           <none>
csi-rbdplugin-provisioner-687cf777ff-ddvzq               6/6     Running     0          55d   10.42.0.21      miami      <none>           <none>
rook-ceph-csi-detect-version-v9ggr                       0/1     Completed   0          54d   10.42.0.19      miami      <none>           <none>
rook-ceph-mds-rsliotta-fs-a-5db685547d-z6mz2             1/1     Running     332        67d   10.42.1.123     moscow     <none>           <none>
rook-ceph-mds-rsliotta-fs-b-588755bd54-pt75s             1/1     Running     0          55d   10.42.2.15      florence   <none>           <none>
rook-ceph-mgr-a-69f7b69cc-bb4vj                          1/1     Running     275        67d   10.42.1.124     moscow     <none>           <none>
rook-ceph-mon-c-7dbbcc9769-s9gcg                         1/1     Running     0          55d   10.42.0.16      miami      <none>           <none>
rook-ceph-mon-d-66787cb764-lqhm7                         1/1     Running     1          58d   10.42.1.129     moscow     <none>           <none>
rook-ceph-operator-785bf4fff4-6sr42                      1/1     Running     1          55d   10.42.1.130     moscow     <none>           <none>
rook-ceph-osd-0-685bd594cd-6fnx7                         1/1     Running     0          55d   10.42.2.21      florence   <none>           <none>
rook-ceph-osd-1-6d4dd94666-s5jz5                         1/1     Running     0          55d   10.42.2.14      florence   <none>           <none>
rook-ceph-osd-2-677478c46b-djd2p                         1/1     Running     0          55d   10.42.2.13      florence   <none>           <none>
rook-ceph-osd-3-6f8b9c845f-tdt2c                         1/1     Running     0          55d   10.42.2.18      florence   <none>           <none>
rook-ceph-osd-4-565b49d85c-cxtlb                         1/1     Running     0          55d   10.42.2.22      florence   <none>           <none>
rook-ceph-osd-5-65464f9b7d-l7q4j                         1/1     Running     0          55d   10.42.2.12      florence   <none>           <none>
rook-ceph-osd-6-9978758bf-jkdpl                          1/1     Running     0          55d   10.42.2.10      florence   <none>           <none>
rook-ceph-osd-7-58df8bbdc4-jt98j                         1/1     Running     0          55d   10.42.2.20      florence   <none>           <none>
rook-ceph-osd-prepare-florence-25x69                     0/1     Completed   0          53d   10.42.2.25      florence   <none>           <none>
rook-ceph-osd-prepare-miami-n6s6z                        0/1     Completed   0          53d   10.42.0.28      miami      <none>           <none>
rook-ceph-osd-prepare-moscow-kbcwz                       0/1     Completed   0          53d   10.42.1.137     moscow     <none>           <none>
rook-ceph-rgw-rsliotta-object-store-a-799f6644d4-7ffkk   1/1     Running     340        67d   10.42.1.118     moscow     <none>           <none>
rook-ceph-tools-6bc7c4f9fc-tx96t                         1/1     Running     1          67d   10.42.1.120     moscow     <none>           <none>

Get all pods with wide output but only names with osd in them

[B:cities:rook-ceph] liottar:/Users/liottar$ kf pod 'osd'
NAME                                                     READY   STATUS      RESTARTS   AGE
rook-ceph-osd-0-685bd594cd-6fnx7                         1/1     Running     0          55d
rook-ceph-osd-1-6d4dd94666-s5jz5                         1/1     Running     0          55d
rook-ceph-osd-2-677478c46b-djd2p                         1/1     Running     0          55d
rook-ceph-osd-3-6f8b9c845f-tdt2c                         1/1     Running     0          55d
rook-ceph-osd-4-565b49d85c-cxtlb                         1/1     Running     0          55d
rook-ceph-osd-5-65464f9b7d-l7q4j                         1/1     Running     0          55d
rook-ceph-osd-6-9978758bf-jkdpl                          1/1     Running     0          55d
rook-ceph-osd-7-58df8bbdc4-jt98j                         1/1     Running     0          55d
rook-ceph-osd-prepare-florence-25x69                     0/1     Completed   0          53d
rook-ceph-osd-prepare-miami-n6s6z                        0/1     Completed   0          53d
rook-ceph-osd-prepare-moscow-kbcwz                       0/1     Completed   0          53d

or the same with a wide output by creating a list with the kfl utility function to pass to kgp

[B:cities:rook-ceph] liottar:/Users/liottar$ kgp -owide $(kfl pod 'osd')
NAME                                   READY   STATUS      RESTARTS   AGE   IP            NODE       NOMINATED NODE   READINESS GATES
rook-ceph-osd-0-685bd594cd-6fnx7       1/1     Running     0          55d   10.42.2.21    florence   <none>           <none>
rook-ceph-osd-1-6d4dd94666-s5jz5       1/1     Running     0          55d   10.42.2.14    florence   <none>           <none>
rook-ceph-osd-2-677478c46b-djd2p       1/1     Running     0          55d   10.42.2.13    florence   <none>           <none>
rook-ceph-osd-3-6f8b9c845f-tdt2c       1/1     Running     0          55d   10.42.2.18    florence   <none>           <none>
rook-ceph-osd-4-565b49d85c-cxtlb       1/1     Running     0          55d   10.42.2.22    florence   <none>           <none>
rook-ceph-osd-5-65464f9b7d-l7q4j       1/1     Running     0          55d   10.42.2.12    florence   <none>           <none>
rook-ceph-osd-6-9978758bf-jkdpl        1/1     Running     0          55d   10.42.2.10    florence   <none>           <none>
rook-ceph-osd-7-58df8bbdc4-jt98j       1/1     Running     0          55d   10.42.2.20    florence   <none>           <none>
rook-ceph-osd-prepare-florence-25x69   0/1     Completed   0          53d   10.42.2.25    florence   <none>           <none>
rook-ceph-osd-prepare-miami-n6s6z      0/1     Completed   0          53d   10.42.0.28    miami      <none>           <none>
rook-ceph-osd-prepare-moscow-kbcwz     0/1     Completed   0          53d   10.42.1.137   moscow     <none>           <none>

As you see, you can combine the commands to make more shortcuts for yourself!

In summary, I hope this helps you get off to a good start with Beeline!

Table of contents ↓

1 Adding network bridge
2 Prerequisite
3 Creating a Linux network bridge
4 Disable or enable STP
5 Set up static or DHCP based IP address
6 Enable br0 network bridge interface
7 Verification network bridge
8 Conclusion

Advertisement Ubuntu 20.04 add network bridge (br0) with nmcli

The procedure to create and add a bridge interface on Ubuntu version 20.04 is as follows when you want to use Network Manager:

Open the Terminal app or log in using the ssh command
Find out information about the current Ubuntu network connection:
sudo nmcli con show
Then, add a new bridge called br0:
sudo nmcli con add ifname br0 type bridge con-name br0
Create a slave interface for br0 using enp0s31f6 NIC:
sudo nmcli con add type bridge-slave ifname enp0s31f6 master br0
Turn on br0 interface to get an IP via DHCP:
sudo nmcli con up br0
Static IP settings are discussed below for the br0 interface

Let us see all examples and instructions in detail to create a network bridge in Ubuntu Linux version 20.04 LTS server. Prerequisite for creating a Linux network bridge on Ubuntu 20.04

First thing, obtain information about the current Ubuntu Linux interface and IP address as we need this information later. Hence, type the following commands: $ nmcli con show $ nmcli connection show –active

Outputs:

NAME UUID TYPE DEVICE ETH0 71a189f2-9cb9-49f0-8464-37a6801740e3 ethernet enp0s31f6

So my server has an “ETH0” which uses the enp0s31f6 Ethernet interface. I am going to set up a bridge interface named br0 and add (enslave) an interface to enp0s31f6. Step 1 – Creating a network bridge named br0

The syntax is: $

$ sudo nmcli con add type bridge-slave ifname enp0s31f6 master br0 $ nmcli connection show

Ubuntu 20.04 add network bridge (br0) with nmcli command Step 2 – Disable or enable STP for network bridge

The primary purpose of Spanning Tree Protocol (STP) is to ensure that you do not create loops when you have redundant paths in your network. We can disable STP or enable as follows for br0: $ sudo nmcli con modify br0 bridge.stp no

Ubuntu 20.04 Linux nmcli command to enable STP with br0

$ sudo nmcli con modify br0 bridge.stp yes

Verification

$ nmcli con show $ nmcli -f bridge con show br0

Outputs:

bridge.mac-address: – bridge.stp: yes bridge.priority: 32768 bridge.forward-delay: 15 bridge.hello-time: 2 bridge.max-age: 20 bridge.ageing-time: 300 bridge.group-forward-mask: 0 bridge.multicast-snooping: yes bridge.vlan-filtering: no bridge.vlan-default-pvid: 1 bridge.vlans: –

Step 3 – Set up static or DHCP based IP for network bridge interface

We have not allocated any static IP address to our br0 interface. Hence, if the DHCP server is available, it should provide IP addresses and other settings. For instance, we can grab IP settings using DHCP as follows: $ sudo nmcli con up br0 $ ip a s br0 $ ping www.cyberciti.biz

However, on servers, we typically set up a static IP address. In this example, I am converting existing enp0s31f6 IP network settings to br0 settings as follows: IPv4 br0 settings

$ sudo nmcli connection modify br0 ipv4.addresses ‘192.168.2.25/24’ $ sudo nmcli connection modify br0 ipv4.gateway ‘192.168.2.254’ $ sudo nmcli connection modify br0 ipv4.dns ‘192.168.2.254’ $ sudo nmcli connection modify br0 ipv4.dns-search ‘sweet.home’ $ sudo nmcli connection modify br0 ipv4.method manual IPv6 br0 settings

$ sudo nmcli connection modify bridge0 ipv6.addresses ‘Your-Static-IPv6-Address’ $ sudo nmcli connection modify br0 ipv6.gateway ‘Your-Static-IPv6-Gateway-Address’ $ sudo nmcli connection modify br0 ipv6.dns ‘Your-Static-IPv6-DNS’ $ sudo nmcli connection modify br0 ipv6.dns-search ‘sweet.home’ $ sudo nmcli connection modify br0 ipv6.method manual Step 4 – Enable br0 network bridge interface on Ubuntu Linux

So far, we configured required network settings. It is time to turn it on our br0: $ sudo nmcli con up br0 $ nmcli con show

Wait for some time to activate settings. Step 5 – Verification network bridge settings

Use the ip command to view the IP settings for br0 bridge on Ubuntu box: $ ip a s $ ip a s br0

You can remove enp0s31f6 as br0 got a static IP address itself as enp0s31f6 will be in forwarding state: $ sudo nmcli connection delete enp0s31f6

or

$ sudo nmcli connection delete ETH0

Here is how it looks using the ip command: $ nmcli connection show $ ip a show br0 $ nmcli device

interface active and works with br0

$ ip a show enp0s31f6 $ ip r

Check Internet and local LAN connectivity using ping command

$ ping -c 4 www.cyberciti.biz $ ping -c 4 192.168.2.25

Show the link status of Ethernet devices and bridge devices on Ubuntu Linux machine: $ ip link show master br0 $ bridge link show $ bridge link show dev enp0s31f6

Verify and Create a Network Bridge in Ubuntu 20.04 Linux LTS server Conclusion

In this tutorial, you learned how to add and create a Linux Network Bridge on Ubuntu 20.04 LTS server. See nmcli docs online for more info. This entry is 8 of 11 in the Linux and Unix Network Bridging Tutorial series. Keep reading the rest of the series:

Debian Linux: Configure Network Interfaces As A Bridge / Network Switch
OpenBSD: Configure Network Interface As A Bridge / Network Switch
How To PFSense Configure Network Interface As A Bridge / Network Switch
FreeBSD: NIC Bonding / Link Aggregation / Trunking / Link Failover
How To Setup Bridge (br0) Network on Ubuntu Linux 14.04 and 16.04 LTS
Ubuntu setup a bonding device and enslave eth0+eth2
Setup Bonded (bond0) and Bridged (br0) Networking On Ubuntu
Ubuntu 20.04 add network bridge (br0) with nmcli command
CentOS 8 add network bridge (br0) with nmcli command
How to add network bridge with nmcli (NetworkManager) on Linux
Set up and configure network bridge on Debian Linux

About the author: Vivek Gite is the founder of nixCraft, the oldest running blog about Linux and open source. He wrote more than 7k+ posts and helped numerous readers to master IT topics. Join the nixCraft community via RSS Feed, Email Newsletter or follow on Twitter.

梁 Was this helpful? Please add a comment to show your appreciation or feedback ↓

Related Tutorials

CentOS 8 add network bridge (br0) with nmcli command
CentOS 8 add network bridge (br0) with nmcli command
How to add network bridge with nmcli (NetworkManager) on…
How to add network bridge with nmcli (NetworkManager) on…
How To Setup Bridge (br0) Network on Ubuntu Linux 14.04 and…
How To Setup Bridge (br0) Network on Ubuntu Linux 14.04 and…
OpenBSD: Configure Network Interface As A Bridge / Network…
OpenBSD: Configure Network Interface As A Bridge / Network…
Debian Linux: Configure Network Interfaces As A Bridge /…
Debian Linux: Configure Network Interfaces As A Bridge /…
How To PFSense Configure Network Interface As A Bridge /…
How To PFSense Configure Network Interface As A Bridge /…
How To Setup Bonded (bond0) and Bridged (br0) Networking On…
How To Setup Bonded (bond0) and Bridged (br0) Networking On…

Category List of Unix and Linux commands Ansible Check version • Fedora • FreeBSD • Linux • Ubuntu 18.04 • Ubuntu • macOS Backup Management Debian/Ubuntu • FreeBSD • RHEL Database Server Backup MySQL server • MariaDB Galera cluster • MariaDB TLS/SSL • MariaDB replication • MySQL Server • MySQL remote access Download managers wget Driver Management Linux Nvidia driver • lsmod Documentation help • mandb • man • pinfo Disk Management df • duf • ncdu • pydf File Management cat • cp • less • mkdir • more • tree Firewall Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04 • Ubuntu 24.04 KVM Virtualization CentOS/RHEL 7 • CentOS/RHEL 8 • Debian 9/10/11 • Ubuntu 20.04 Linux Desktop apps Chrome • Chromium • GIMP • Skype • Spotify • VLC 3 Modern utilities bat • exa Network Management Monitoring tools • Network services • RHEL static IP • Restart network interface • nmcli Network Utilities NetHogs • dig • host • ip • nmap • ping OpenVPN CentOS 7 • CentOS 8 • Debian 10 • Debian 11 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04 Power Management upower Package Manager apk • apt-get • apt • yum Processes Management bg • chroot • cron • disown • fg • glances • gtop • iotop • jobs • killall • kill • pidof • pstree • pwdx • time • vtop Searching ag • egrep • grep • whereis • which Shell builtins compgen • echo • printf System Management reboot • shutdown Terminal/ssh sshpass • tty Text processing cut • rev Text Editor 6 Text editors • Save and exit vim User Environment exit • who User Information groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • w User Management /etc/group • /etc/passwd • /etc/shadow • chsh Web Server Apache • Let’s Encrypt certificate • Lighttpd • Nginx Security • Nginx WireGuard VPN Alpine • Amazon Linux • CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04 • qrencode 8 comments… add one

unixpro Aug 10, 2020 @ 0:33

I think there’s a limitation with the standard Linux bridge when working with wireless adapters. Actually I think it’s a limitation with wireless link layer then authentication and trying to bridge Ethernet layer 2 over that authenticated stack if you get me.
Reply Link
perli Aug 31, 2020 @ 15:00

Hi, i have trouble withe getting an ip from the DHCP server to the bridge while the vm does get an ip. i would appreciate if you explain how to activate the br to work with dhcp , not based on if my dhcp server works in general (I’m on wireless). Thanks
Reply Link
PavelN Oct 6, 2020 @ 12:25

BTW: you have a typo in commands (missing con-name option) :
> Then, add a new bridge called br0:
sudo nmcli con add type bridge ifname br0

later in the page there is a proper syntax including “con-name” :
sudo nmcli con add ifname br0 type bridge con-name br0
Reply Link
     Vivek Gite Oct 26, 2020 @ 12:59

    Fixed it. Thanks for the tip and I appreciate your feedback.
    Reply Link
InnocentBystander Jan 26, 2021 @ 4:35

What is exactly ‘sweet.home’ in
sudo nmcli connection modify br0 ipv4.dns-search 'sweet.home'

Where does this value come from and what is the purpose/usage of this setting?

Thanks
Reply Link
     Vivek Gite Jan 27, 2021 @ 19:36

    That is my own domain search name set up in my DHCPD. So instead of typing ssh ‘mylaptop.sweet.home’, I type ‘mylaptop’. You can ignore sudo nmcli connection modify br0 ipv4.dns-search ‘sweet.home’ if you don’t have such fancy config.
    Reply Link
Beau G Apr 8, 2021 @ 13:21

Hello, I am getting the following error:

sudo nmcli con up br0
Error: Connection activation failed: Connection 'br0' is not available on device br0 because device is strictly unmanaged

nmcli con show
NAME                 UUID                                  TYPE      DEVICE
br0                  61d76e77-f193-4aea-94b2-02128aa5e8f1  bridge    --
bridge-slave-enp3s0  810348e4-c676-42d1-80c1-0414ce956130  ethernet  --

I restarted network manager. Nothing gives.
Reply Link
    Gautham Apr 8, 2021 @ 15:09

    Look like br0 is in managed state.

    sudo nmcli dev set {interface} managed {option}

    Your {interface} name such as eth0/enp3s0/br0. And {option} can be false, no, off, on, true, and yes. Try something as follows:

    sudo nmcli dev set br0 managed yes

    Reply Link

Leave a Reply

Your email address will not be published. Required fields are marked *

Comment *

Name

Email

Website

Use HTML <pre>…</pre> for code samples. Your comment will appear only after approval by the site admin.

Next FAQ: How to install KVM on Ubuntu 20.04 LTS Headless Server

Previous FAQ: Squid test config file for syntax errors       Search

FEATURED ARTICLES

1
30 Cool Open Source Software I Discovered in 2013
2
30 Handy Bash Shell Aliases For Linux / Unix / Mac OS X
3
Top 32 Nmap Command Examples For Linux Sys/Network Admins
4
25 PHP Security Best Practices For Linux Sys Admins
5
30 Linux System Monitoring Tools Every SysAdmin Should Know
6
40 Linux Server Hardening Security Tips
7
Linux: 25 Iptables Netfilter Firewall Examples For New SysAdmins
8
Top 20 OpenSSH Server Best Security Practices
9
Top 25 Nginx Web Server Best Security Practices
10
My 10 UNIX Command Line Mistakes

Sign up for my newsletter Sign up for my newsletter

➔
Linux shell scripting tutorial
➔
RSS/Feed
➔
About nixCraft

      ©2002-2022 nixCraft • Privacy • ToS • Contact/Email • Corporate patron Linode & Cloudflare

Original: https://www.cyberciti.biz/faq/ubuntu-20-04-add-network-bridge-br0-with-nmcli-command/

Editor’s Note (7/24/2021): We have updated this tutorial to include how you can boot your Raspberry Pi 400 from USB.

By default, Raspberry Pi boots up and stores all of its programs on a microSD memory card, which has a maximum theoretical bandwidth of 50 MBps on the Raspberry Pi 4 and just 25 MBps on prior models. In real-life, even the best microSD cards for Raspberry Pi get no faster than about 38 MBps in sequential writes. Using an external SSD as your main storage drive could speed things up significantly and, with a few commands and a simple firmware update, you can do just that.

In our real-life tests of a Raspberry Pi 4 with SSD last year we got impressive performance with sequential transfer rates as high as 140 MB / 208 MBps for reading and writing. You can also use a standard USB flash drive, though we found the performance worse than a microSD card on many tasks.

How to Boot Raspberry Pi 4 / 400 from USB

If you want to start with a fresh install of Raspberry Pi OS, simply follow the instructions in our tutorial on how to set up Raspberry Pi or how to do a Raspberry Pi headless install.

The latest versions of Raspberry Pi OS (as of April 29 2021 or later) have many of the necessary changes built-in. The Raspberry Pi Imager now has a much simpler means to prepare a Raspberry Pi 4 / 400 for USB boot. These instructions will set the Raspberry Pi 4 / 400 to look for a USB boot device, if none is found it will then boot from the micro SD card.

1. Download and install Raspberry Pi Imager from the Raspberry Pi website.

2. Insert a spare micro SD card into your computer. Note that this card will be erased.

3. Launch Raspberry Pi Imager and under Operating System scroll down to Misc Utility Images and left click to open the next menu.

(Image credit: Tom’s Hardware)

4. Select Bootloader and then Select USB Boot. This will return us to the main menu.

(Image credit: Tom’s Hardware)

5. Under Storage click on the button and select the micro SD card. Double check that you have the right drive before proceeding.

(Image credit: Tom’s Hardware)

6. Click on Write to download and write a configuration image to the micro SD card. When done remove the card from your computer.

(Image credit: Tom’s Hardware)

7. Insert the micro SD card into your Raspberry Pi 4 / 400 and power on. The green activity light will blink a steady pattern once the update has been completed. If you have an HDMI monitor attached, the screen will go green once the update is complete. Allow 10 seconds or more for the update to complete, do not remove the micro SD card until the update is complete.

8. Power off the Raspberry Pi and remove the micro SD card.

Keep in mind that, if you are using an external drive that saps a lot of power from the bus, you may have issues (which you could probably solve by using a drive that has its own power source or by using a powered USB hub).

For example, we had problems using a bus-powered, external Kingston HyperX SSD, which booted but – perhaps because of how much power it was using – none of our peripherals would work. A SATA SSD in a externally powered dock worked fine as did a USB Flash drive.

The docs are not clear as to what is acting as a DHCP server, but I see DHCP happening in the guest logs, so I will chalk it up to some Multipass magic.

The problem I was confronted with is that I could not ssh into these guests from elsewhere on the ipv4 network. Only from WSL on my Host machine. Now it’s possible that this is some windows firewall setting on my part. But I also think it’s possible that Multipass is setting up a bridge network without ingress.

To enable network access to your guest vms:

–Create a Virtual Switch on your network interface

• Open hyper-v manager.
• Action > Virtual Switch Manager
• Select External > Create Virtual Switch
  • Give the virtual switch a name
  • Select the Network Interface you want the switch to attach to and apply.

[

image.png881×586 106 KB

Attach

–Attach Guest to Virtual Switch

• With the guest powered off
• Right click on the Virtual Machine name that you want to access, and go to Settings.
• Select Add Hardware, Network Adapter.
• Navigate to the new Network Adapter and select the new Virtual Switch you added in the previous step.

–Make your guest aware of the new interface

• Open a shell to your guest, via Multipass
• ip link should show a new interface, probably eth1
• Make a backup of /etc/netplan/NN-cloud-init.yaml
• Observing proper YAML spacing, add the lines:

        eth1:
            dhcp4: true

So your /etc/netplan/NN-cloud-init.yaml should look approximately like:

network:
    ethernets:
        eth0:
            dhcp4: true
            match:
                macaddress: 00:15:5d:3d:39:02
            set-name: eth0
        eth1:
            dhcp4: true
    version: 2

• Run sudo netplan generate, you will be prompted if there are yaml errors.
• Run sudo netplan apply You may lose connection during this point.
• You may need to do a systemctl restart systemd-networkd.service or restart the guest via Multipass.
• If everything went well ip addr should show that you’ve leased an IP address.
• The guests disallow password logins, so copy your public ssh key to ~authorized_keys on the guest, to enable logging in.

I hope someone finds this helpful

Original Article: https://discourse.ubuntu.com/t/solution-multipass-not-reachable-from-outside-windows-10-networking-host/16392

So if you are using Linux distributions, RUFUS is not the way to go. But fear not. Just as the case with almost every other tasks, popular Linux distros such as Ubuntu has never failed to meet the user demands. Same is the situation when you need to convert ISO to bootable USB Media in Ubuntu, Linux Mint, or any Debian distros.

In this tutorial, I’m going to show you how to create a bootable USB Media in Ubuntu within a minute. So I assume you already have Ubuntu running on your PC.

For this tutorial, I will be making an Ubuntu ISO 18.04 bootable in a USB 4GB flash drive.

STEP 1: Downloading Balena Etcher Desktop App

Open the terminal… *Ctrl+Alt+T*

• Add Etcher debian repository: *Press the Enter keyboard after every command.*

echo "deb https://deb.etcher.io stable etcher" | sudo tee /etc/apt/sources.list.d/balena-etcher.list

• Trust Bintray.com’s GPG key:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 379CE192D401AB61

• Update and install:

sudo apt-get updatesudo apt-get install balena-etcher-electron

Ever feel like uninstalling it? Uninstall:

sudo apt-get remove balena-etcher-electronsudo rm /etc/apt/sources.list.d/balena-etcher.listsudo apt-get update

STEP 2: Open BalenaEtcher

Search BalenaEtcher from your Application Menu, or simply press the windows key and type ‘BalenaEtcher’.

Search for BalenaEtcher on ubuntu 18.04

STEP 3: The Final Step (Making the USB Bootable)

balenaEtcher environment

The environment is simple and straight forward:

• Select the image (iso file)
• Select the flash drive plugged in the PC
• Click on the Flash button, wait for the magic to happen

Grab a cup of coffee, while the magic happens…

flashing

validating

Boom!!! Magic Done. Your USB flash drive is bootable, unmount your drive, and go make yourself proud…

Flash complete

sudo umount /dev/sdc1

Original Article: https://medium.com/studevs/create-bootable-usb-media-in-ubuntu-using-balenaetcher-53f4b4010111

A workaround for this is to split the installer into smaller files, which requires the installation of a package manager, wimlib, that is installed through Homebrew. This will split the Windows installer file while creating the bootable disk.

To install Homebrew and create a bootable Windows 11 USB, open Terminal on your Mac from Finder > Applications and enter the following commands. Once you have entered a command, press Enter:

curl -fsSL -o install.sh https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh
/bin/bash install.sh

​

This process will download and install Xcode before installing Homebrew. Xcode is an integrated development environment (IDE) that is comprised of software development tools for macOS. The process may take a few minutes to complete.

You will be required to type in your Mac user password to authenticate yourself. You won’t see anything appear on the screen when you type it in, so just type it and press Enter to install Homebrew.

Once the installation is complete, enter the following command and press Enter to install wimlib:

brew install wimlib

You might get an error message saying command not found:brew, you may also see two commands in Terminal right at the end of the previous Homebrew installation. Enter the commands to activate Homebrew, followed by he command above again to get it working successfully.

​

Now, make sure your USB is connected to your Mac. Run the following command:

diskutil list

This will bring up a list of drives connected to your Mac. Find and note down the USB drive’s disk identifier, which should appear to the left of (external, physical), and should resemble disk2, disk3, and so on.

Use the following command to format the USB stick in Terminal (replace disk2 with your disk identifier):

diskutil eraseDisk MS-DOS WINDOWS11 GPT /dev/disk2

Terminal should now format your disk and rename it as WINDOWS11.

Mount the Windows 11 ISO from the Downloads folder on your Mac. You can do this by double-clicking on the ISO file, which should then show up in your Mac’s connected devices as CCCOMA_X64FRE_EN-US_DV9 or similar. Remember to match the file name exactly to the one above. If it’s different (due to a different language preference), make sure to change it accordingly in the commands below.

Since the installer file is bigger than 4GB, we’ll be using two separate commands to create the bootable disk. The first command will copy all the files apart from the install.wim file (which is 4.2GB) in size. The second command will use wimlib to split and copy the install.wim file to the USB stick.

Use the following command to copy the content of the ISO image—excluding the install.wim file—onto the USB drive:

rsync -vha --exclude=sources/install.wim /Volumes/CCCOMA_X64FRE_EN-US_DV9/* /Volumes/WINDOWS11

Then run the following command to split and copy the install.wim file:

wimlib-imagex split /Volumes/CCCOMA_X64FRE_EN-US_DV9/sources/install.wim /Volumes/WINDOWS11/sources/install.swm 3000

​

That’s it! Terminal should successfully create the bootable disk, which you can now use to boot a fresh Windows installation.

##

cp -R /etc/kubernetes/ssl /etc/kubernetes/ssl.backup
cp /etc/kubernetes/admin.conf /etc/kubernetes/admin.conf.backup
cp /etc/kubernetes/controller-manager.conf /etc/kubernetes/controller-manager.conf.backup
cp /etc/kubernetes/kubelet.conf /etc/kubernetes/kubelet.conf.backup
cp /etc/kubernetes/scheduler.conf /etc/kubernetes/scheduler.conf.backup

Now user kubeadm to upgrade the certs

• Note: 1.15 and above….

export https_proxy=proxyserver:3128
export no_proxy=172.18.2.220,172.18.2.221,172.18.2.222
export PATH=/usr/local/bin:$PATH
kubeadm alpha certs renew apiserver-kubelet-client
kubeadm alpha certs renew apiserver
kubeadm alpha certs renew front-proxy-client
kubeadm alpha kubeconfig user --apiserver-advertise-address 172.18.2.220 --client-name system:kube-controller-manager > /etc/kubernetes/controller-manager.conf
kubeadm alpha kubeconfig user --apiserver-advertise-address 172.18.2.220 --client-name system:kube-scheduler > /etc/kubernetes/scheduler.conf
kubeadm alpha kubeconfig user --apiserver-advertise-address 172.18.2.220 --client-name system:node:iahlvlkubfed1 --org system:nodes > /etc/kubernetes/kubelet.conf
kubeadm alpha kubeconfig user --apiserver-advertise-address 172.18.2.220 --client-name kubernetes-admin --org system:masters > /etc/kubernetes/admin.conf
cp  /etc/kubernetes/admin.conf ~/.kube/config

Master Node

export https_proxy=iahlproxy.logistics.corp:3128
export no_proxy=172.18.2.220,172.18.2.221,172.18.2.222
export PATH=/usr/local/bin:$PATH
kubeadm upgrade apply v1.16.9

Additional Master Nodes

export https_proxy=iahlproxy.logistics.corp:3128
export no_proxy=172.18.2.220,172.18.2.221,172.18.2.222
export PATH=/usr/local/bin:$PATH
kubeadm upgrade node

Restart kubelet and Services

service kubelet stop service kubelet start k delete pod $(k get pods -n kube-system | egrep ‘apiserver|controller|scheduler’ | awk ‘{print $1}’ | xargs )

Use this if autoresize does NOT work

• First we need the hostname that the PVC is running on. You get that as follows:

  [B:avengers:grafana] liottar:/Users/liottar$ kgp -owide
    NAME                       READY   STATUS    RESTARTS   AGE   IP             	NODE   NOMINATED NODE   READINESS GATES
    grafana-58ff767cd6-rlckq   1/1     Running   0          11m   10.233.76.199   *thor*  <none>           <none>
  

• Save the host is it running on. In this case thor
• Next, we need the pv name

  [B:avengers:grafana] liottar:/Users/liottar$ k get pvc
  NAME                STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
  grafana             Bound    *pvc-6089741d-6ec8-40c6-b127-f5df3c3f9bcf*   16Gi       RWO            rook-ceph-block   32m
  grafana-certs-pvc   Bound    grafana-certs-pv                           1Gi        ROX            manual            32m
  

• Save the PV name. In this case pvc-6089741d-6ec8-40c6-b127-f5df3c3f9bcf
• Now we need the rdb volume

  k describe pv pvc-6089741d-6ec8-40c6-b127-f5df3c3f9bcf
  Name:            pvc-6089741d-6ec8-40c6-b127-f5df3c3f9bcf
  Labels:          <none>
  Annotations:     pv.kubernetes.io/bound-by-controller: yes
                 pv.kubernetes.io/provisioned-by: rook-ceph.rbd.csi.ceph.com
  Finalizers:      [kubernetes.io/pv-protection]
  StorageClass:    rook-ceph-block
  Status:          Bound
  Claim:           grafana/grafana
  Reclaim Policy:  Retain
  Access Modes:    RWO
  VolumeMode:      Filesystem
  Capacity:        16Gi
  Node Affinity:   <none>
  Message:
  Source:
    Type:              CSI (a Container Storage Interface (CSI) volume source)
    Driver:            rook-ceph.rbd.csi.ceph.com
    FSType:            ext4
    VolumeHandle:      0001-0009-rook-ceph-0000000000000002-982bc493-c57c-11eb-b70e-be16494d8857
    ReadOnly:          false
    VolumeAttributes:      clusterID=rook-ceph
                           csi.storage.k8s.io/pv/name=pvc-6089741d-6ec8-40c6-b127-f5df3c3f9bcf
                           csi.storage.k8s.io/pvc/name=grafana
                           csi.storage.k8s.io/pvc/namespace=grafana
                           imageFeatures=layering
                           imageFormat=2
                           imageName=*csi-vol-982bc493-c57c-11eb-b70e-be16494d8857*
                           journalPool=replicapool
                           pool=replicapool
                           storage.kubernetes.io/csiProvisionerIdentity=1622684567259-8081-rook-ceph.rbd.csi.ceph.com
  Events:                <none>
  

  • Save the rbd image name, in this case csi-vol-982bc493-c57c-11eb-b70e-be16494d8857
• Now go into rook-ceph-tools

  k exec -itn rook-ceph rook-ceph-tools-7865b9c9f6-m75sq /bin/bash
  

• Resize the volume

   rbd resize --pool replicapool --image csi-vol-982bc493-c57c-11eb-b70e-be16494d8857 --size=18Gi
  exit
  

• Now…. Log into the host where the pvc is mounted, in this case Thor and execute the following commands:

  ssh centos@thor
  sudo -I  # You are now root - Beware and two pairs of eyes
  df -k | grep pvc-6089741d-6ec8-40c6-b127-f5df3c3f9bcf ### <— PV  from earlier
  /dev/rbd4                                                                                                                                               16448380    90116  16341880   1% /var/lib/kubelet/pods/a1183a36-df40-40ed-9188-68217dc87c81/volumes/kubernetes.io~csi/pvc-6089741d-6ec8-40c6-b127-f5df3c3f9bcf/mount
  

  • Note the device name…. In this example /dev/rbd4 resize2fs /dev/rbd4 exit exit
• k edit pv pvc-6089741d-6ec8-40c6-b127-f5df3c3f9bcf
  • Check the size of the device to make sure it matches what you put in the resize in ceps-tools
• Let’s check it

  [B:avengers:grafana] liottar:/Users/liottar$ k exec -it grafana-58ff767cd6-mxzbx /bin/bash
  kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
  bash-5.0$ df -k
  Filesystem           1K-blocks      Used Available Use% Mounted on
  overlay              251849584  81204868 157828332  34% /
  tmpfs                    65536         0     65536   0% /dev
  tmpfs                131897456         0 131897456   0% /sys/fs/cgroup
  /dev/sda7            1048309768    208876 994826524   0% /etc/pki
  /dev/sda5            201453840   2749648 188447808   1% /dev/termination-log
  shm                      65536         0     65536   0% /dev/shm
  /dev/sda4            251849584  81204868 157828332  34% /etc/resolv.conf
  /dev/sda4            251849584  81204868 157828332  34% /etc/hostname
  /dev/sda5            201453840   2749648 188447808   1% /etc/hosts
  */dev/rbd4             18512592     90072  18406136   0% /var/lib/grafana*
  /dev/sda5            201453840   2749648 188447808   1% /etc/grafana/grafana.ini
  tmpfs                131897456        12 131897444   0% /run/secrets/kubernetes.io/serviceaccount
  tmpfs                131897456         0 131897456   0% /proc/acpi
  tmpfs                    65536         0     65536   0% /proc/kcore
  tmpfs                    65536         0     65536   0% /proc/keys
  tmpfs                    65536         0     65536   0% /proc/timer_list
  tmpfs                    65536         0     65536   0% /proc/sched_debug
  tmpfs                131897456         0 131897456   0% /proc/scsi
  tmpfs                131897456         0 131897456   0% /sys/firmware