Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[cherry-pick] config: fix runAsUser inconsistency with images 馃崹 #3368

Merged
merged 1 commit into from
Oct 12, 2020

Conversation

vdemeester
Copy link
Member

Changes

The distroless nonroot image define a user with the uid 65532 and
not 1001. The deployment should use that uid to make sure it works anywhere.

Signed-off-by: Vincent Demeester vdemeest@redhat.com
(cherry picked from commit 4f5a71c)
Signed-off-by: Vincent Demeester vdemeest@redhat.com

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

Fix inconsistent uid for the controller and webhook deployment, resulting in failure of installing tekton pipeline on minikube (and other platforms.)

The distroless `nonroot` image define a user with the uid 65532 and
not 1001. The deployment should use that uid to make sure it works anywhere.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
(cherry picked from commit 4f5a71c)
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@tekton-robot tekton-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Oct 12, 2020
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 12, 2020
@vdemeester
Copy link
Member Author

/kind bug

@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label Oct 12, 2020
@vdemeester vdemeester added this to the Pipelines v0.17 milestone Oct 12, 2020
@dlorenc
Copy link
Contributor

dlorenc commented Oct 12, 2020

/approve

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dlorenc

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 12, 2020
@jerop
Copy link
Member

jerop commented Oct 12, 2020

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 12, 2020
@vdemeester
Copy link
Member Author

/retest

@jerop
Copy link
Member

jerop commented Oct 12, 2020

/test pull-tekton-pipeline-integration-tests

@tekton-robot tekton-robot merged commit 75ef55b into tektoncd:release-v0.17.x Oct 12, 2020
@vdemeester vdemeester deleted the cherry-pick-3342 branch October 12, 2020 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants