-
Notifications
You must be signed in to change notification settings - Fork 113
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
Documentation for the multiarch-native-buildah ClusterStrategy #1660
Documentation for the multiarch-native-buildah ClusterStrategy #1660
Conversation
/kind documentation |
/test "Release Note Linter / Release Note Linter (pull_request)" |
@aleskandro: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
a89f251
to
c4f18df
Compare
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SaschaSchwarze0 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 |
This PR proposes a new paragraph to document the Multiarch Native Buildah strategy proposed in #1634.
I see the other strategies leverage a relative path to link to the strategy in the document; however, those links are dead, AFAICU.
Therefore, I used GitHub permalinks. Are they okay with landing in the doc?
Relates to #1119
Release Notes
/kind documentation
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.