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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fetch installed tekton component version from ConfigMap #278

Merged
merged 1 commit into from
Jun 30, 2021

Conversation

vinamra28
Copy link
Member

Changes

As part of TEP-0041 version of tekton pipelines will be stored in a new
ConfigMap and that ConfigMap is given special permissions so that in
heavy RBAC enforced environment any user authenticated to the cluster
can still fetch the version even if they don't have permissions to view
the other resources which are associated with tekton-pipelines.

With pipelines 0.25 version this configmap would be available so
fetching the version from configmap and if the configmap is not present
then it will check for the version present on the label (backward
compatible).

Signed-off-by: vinamra28 [email protected]

Submitter Checklist

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

See the contribution guide for more details.

@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 12, 2021
@vinamra28 vinamra28 changed the title Fetch installed tekton component version from CM Fetch installed tekton component version from ConfigMap Jun 12, 2021
As part of TEP-0041 version of tekton pipelines will be stored in a new
ConfigMap and that ConfigMap is given special permissions so that in
heavy RBAC enforced environment any user authenticated to the cluster
can still fetch the version even if they don't have permissions to view
the other resources which are associated with tekton-pipelines.

With pipelines 0.25 version this configmap would be available so
fetching the version from configmap and if the configmap is not present
then it will check for the version present on the label (backward
compatible).

Signed-off-by: vinamra28 <[email protected]>
@sm43
Copy link
Member

sm43 commented Jun 28, 2021

/meow
/approve

@tekton-robot
Copy link

@sm43: cat image

In response to this:

/meow
/approve

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/test-infra repository.

@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sm43

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 Jun 28, 2021
@PuneetPunamiya
Copy link
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 30, 2021
@tekton-robot tekton-robot merged commit 12b9234 into tektoncd:main Jun 30, 2021
@vinamra28 vinamra28 deleted the implement-tep-0041 branch June 30, 2021 13:22
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. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants