Consolidated example for Linkerd+Namerd
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kubernetes
- Domain
- infrastructure
Research direction
Start with k8s-daemonset/k8s/servicemesh.yml and compare it with the linked consolidated Kubernetes article and blog series. Determine how the existing Linkerd example should be extended with a Namerd setup, then add a corresponding sample whose configuration can be followed from the referenced example.
Written by the indexing model from the issue text.
Description
This article, and this example setup are great reference points for implementing the blog series, but it's missing examples of Namerd setup.
Maybe it would be nice to add a corresponding sample for Linkerd+Namerd?
- Dominant language
- Go
- Stars
- 444
- Forks
- 215
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linkerd/linkerd-examples
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
linkerd/linkerd-examples#274 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
linkerd/linkerd-examples#273 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
linkerd/linkerd-examples#259 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
linkerd/linkerd-examples#247 ·
-
additional test dimensions in lifecycle test environmentMay be free again @siggy claimed this 3014 days ago, and no pull request is open. Openbenchmarking in progress
linkerd/linkerd-examples#225 · 1 assignee ·
All issues in linkerd/linkerd-examples
Similar issues
-
[doc-healer] DDUw improvement: retry integrity-filtered issue reads with direct single-item lookupsOpenautomation documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
containerd/containerd#14476 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Infisical/infisical#8987 · 1 comment ·
Maintainers usually reply within 1 day
-
scan framework and scan control accept empty and whitespace-only policy names in Args validationPossibly taken @WKr1shna claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day