The 6 essential questions
- Who is it about?
- What did they want?
- Why can't they get it?
- What did they do about it?
| --- | |
| ### | |
| ### Linkerd Namespace | |
| ### | |
| kind: Namespace | |
| apiVersion: v1 | |
| metadata: | |
| name: linkerd | |
| annotations: | |
| linkerd.io/inject: disabled |
| --- | |
| # | |
| # Buoyant Cloud Agent manifest for NYC1 | |
| # | |
| --- | |
| kind: Namespace | |
| apiVersion: v1 | |
| metadata: | |
| name: buoyant-cloud | |
| annotations: |
| # Inserts a blank line between shell prompts | |
| add_newline = true | |
| # Replace the "❯" symbol in the prompt with "➜" | |
| # [character] # The name of the module we are configuring is "character" | |
| # success_symbol = "[➜](bold green)" # The "success_symbol" segment is being set to "➜" with the color "bold green" | |
| # Disable the package module, hiding it from the prompt completely | |
| # [package] | |
| # disabled = true |
There is no one way to get into the kubernetes blog. Below are some options:
The Kubernetes Upstream Marketing team under ContribEx can help you tell a kubernetes story. With Blog posts you can:
| apiVersion: rbac.authorization.k8s.io/v1 | |
| kind: ClusterRole | |
| metadata: | |
| annotations: | |
| rbac.authorization.kubernetes.io/autoupdate: "true" | |
| labels: | |
| name: read-only | |
| namespace: '*' | |
| rules: | |
| - apiGroups: ["*"] |
| ## Bring your current branch up-to-date with master, and squash all your working commits | |
| ## commit any working changes on branch "${BRANCH}", then... | |
| ## rename the branch to reflect it has the unsquashed commits | |
| git branch -m ${BRANCH}-unsquashed | |
| ## crete a new local branch to start with the latest version of master | |
| git checkout master | |
| git pull |
jason_mo Jason Morgan Human person.
I hereby claim: