-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Porch private authenticated registries functionality documentation #178
Conversation
…henticated repositories
✅ Deploy Preview for nephio ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
/approve |
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-external-private-repositories.md
Outdated
Show resolved
Hide resolved
/retest |
content/en/docs/porch/using-porch/using-authenticated-private-registries.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-authenticated-private-registries.md
Outdated
Show resolved
Hide resolved
/approve |
{{% /alert %}} | ||
|
||
This should generate a secret template, similar to the one below, which you can add to the *2-function-runner.yaml* file in the Porch catalog package found [here](https://github.com/nephio-project/catalog/tree/main/nephio/core/porch) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Catalin-Stratulat-Ericsson Secret generated like this kubectl create secret docker-registry XXXX --docker-server=https://index.docker.io/v1/ --docker-username=<your-name> --docker-password=<your-pword> --docker-email=<your-email>
Should also work I suppose? That creates a .dockerconfigjson
inside secrets.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- So long as the content being put into the secret is in the JSON format and follows the docker config.json schema it should work just fine.
- One side note i will say regarding doing it that way is that you would be leaving your password/token in plaintext in the terminal and also in the history of the machine which i don't believe should be encouraged or used as the preferred way to create the secret in the documentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay I agree with the second point but we can always remove it from the history using history -d <line-number>
/approve |
Once --> nephio-project/porch#126 is merged then this PR can be merged |
+1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another few wording/grammar comments
content/en/docs/porch/using-porch/using-authenticated-private-registries.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-authenticated-private-registries.md
Outdated
Show resolved
Hide resolved
content/en/docs/porch/using-porch/using-authenticated-private-registries.md
Outdated
Show resolved
Hide resolved
/approve |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arora-sagar, JamesMcDermott, liamfallon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Paired with PR #126
This provides documentation on how to configure porch to use external private authenticated registries.