Document that the `auth` config section from the wildcard entry is not supported

Open Beginner friendly
#359 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
80/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
documentation

Research direction

Open the linked Private Registry - Wildcard Support documentation and review its current explanation of wildcard configurations. Document that credentials from the auth config section of a wildcard entry are not supported, while preserving the existing scope of the page. Done means the limitation is clearly stated where wildcard support is described.

Written by the indexing model from the issue text.

Description

Wildcard configurations for both mirrors and configs should work consistently and allow pulling images when proper authentication is provided.
The documentation mentions wildcard support but does not specify limitations related to this case.

Relevant doc link: Private Registry - Wildcard Support

it is not intended that credentials would be looked up from the wildcard section.

Dominant language
Shell
Stars
33
Forks
198
Avg merge
8d 10h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

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 k3s-io/docs

All issues in k3s-io/docs

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.