Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

annotate files with inlined linkerd/namerd configs

Open
  • Is something wrong?
#146 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
42/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
kubernetes
Domain
documentation

Research direction

Start by reading k8s-daemonset/k8s/linkerd-ingress.yml around the linked embedded configuration, then inspect the other example files for similar inline Linkerd or Namerd configs. Done means adding comments that clearly separate Linkerd or Namerd configuration from the surrounding environment configuration.

Written by the indexing model from the issue text.

Description

help wanted

Some example files inline linkerd and namerd configs, for example, linkerd's config yaml is embedded in this k8s yaml:
https://github.com/linkerd/linkerd-examples/blob/master/k8s-daemonset/k8s/linkerd-ingress.yml#L8

It would be helpful to call this out with a comment, to indicate the delineation between linkerd config and environment config.

Dominant language
Go
Stars
444
Forks
216
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linkerd/linkerd-examples

All issues in linkerd/linkerd-examples

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.