This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
How to Set Up Workload Identity on AKS drafts one workload identity note for a lab AKS cluster you administer. Review it before you run it. Do not upgrade or resize a production cluster during the reading.
Do not expose the API to the internet. A cost note is not a bill. An upgrade waits until a person has written the version you are leaving and a way back.
The browser tool drafts text. It does not connect to the cloud account.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep. 10.0.0.0/16 is a sample prefix, not a network you publish unless you already use it.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the account named in the ticket. Read the draft, then the account, then decide.
Rollback is the previous file, the previous plan, or the lab resource you can delete because it was only a lab.
- Write the account, project, or repository, and confirm you administer it.
- Save the current file or export before any draft is applied.
- Read the draft and delete every line this ticket did not name.
- Replace account IDs, images, example.com, and any sample password.
- Apply nothing during the reading.
- Read the names back and compare them with the ticket.
- Stop. The next change is a different page.
Mistakes that outlive the statement
workload identity on AKS goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Applying a draft you did not read.
- The wrong account.
- A secret, an access key, or a kubeconfig in git.
- Two changes in one window.
- No copy saved before the change.
- A documentation address or example.com left in a file you apply.
- An ingress from 0.0.0.0/0 left in the file.
- Calling the generator output a finished production change.
- A production upgrade during the reading.
- The API exposed to the internet.
- A cost note treated as a bill.
Decisions to write down
One decision for workload identity on AKS: The cluster is a lab cluster you administer, or this stays a plan. The change is only workload identity. The platform is AKS. The current version or cost input is written. And nothing was applied during the reading.
Checks before you call it done
Confirm this before you call the change done: The cluster is written. The draft was read. Nothing was applied. The API is not open to every address. No secret is in the note. And a way back is written before any later upgrade. If one of those fails, stop.
# AKS: workload identity.
# Review before you run this against a cluster.
# Do not apply during the reading.
# 192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep. 10.0.0.0/16 is a sample prefix, not a network you publish unless you already use it.Before you leave the account
How to Set Up Workload Identity on AKS ends when the account in the note is the account in the ticket. If it is not, stop.
The draft stays a draft until a person has read the names in it. A generator does not log in, does not apply, and does not scan.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep. 10.0.0.0/16 is a sample prefix, not a network you publish unless you already use it.
prompt-for-this is a reminder that a secret is missing. It is not an access key, a token, or a password you save. An Azure secret draft may contain a sample password. Replace it. Do not file it.
One change is the window. If two things move and the result is wrong, you will not know which one did it.
If the same step fails twice, stop for the day. Restore the copy you took first.
A second person reads the account and the change aloud. If they cannot find them in the ticket, the note is not done.
This page is a planning guide. It is not a vendor manual, not an official standard, not legal advice, and not an audit opinion. You do not apply it against an account you do not administer.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.