-
Notifications
You must be signed in to change notification settings - Fork 232
Updates tektonPipeline to make it independent of tektonConfig #600
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
Conversation
|
The following is the coverage report on the affected files.
|
|
@nikhil-thomas I have verified this PR resolve TargetNamespace issue |
Thanks @savitaashture 👍 @PuneetPunamiya Functionally this patch looks great. I have a few comments regarding code organization. We shall merge this once those are addressed. 🧑💻 |
ce3c09d to
c80fb40
Compare
|
The following is the coverage report on the affected files.
|
9aade37 to
38bd9a2
Compare
|
The following is the coverage report on the affected files.
|
|
The following is the coverage report on the affected files.
|
Can you add UT for this |
38bd9a2 to
f982a72
Compare
|
/hold |
|
The following is the coverage report on the affected files.
|
| } | ||
| } | ||
| } else { | ||
| labels := map[string]string{"operator.tekton.dev/targetNamespace": "true"} |
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.
I can see that the following label already exists at line https://github.com/tektoncd/operator/pull/600/files#diff-de56e5fd636d3b9b5ab99eb6197436045c5bc27187a3f59649bae7d66a8e7202R19, so do we still need to pass this label from here?
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 from the tektonConfig I have removed but in the tektonPipelines we need it
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.
why is it not needed in tektonConfig. I was thinking we will need it in both TektonConfig and TektonPipeline.
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.
It is needed in tektonConfig as well, but the reason I've remove this variable because, in the createTargetNamespace function itself I'm adding that label while creating the namespace. For ref: please see here
f982a72 to
8106861
Compare
|
The following is the coverage report on the affected files.
|
|
The following is the coverage report on the affected files.
|
4b36022 to
cd2b281
Compare
|
The following is the coverage report on the affected files.
|
|
/test pull-tekton-operator-integration-tests |
cd2b281 to
2e5673d
Compare
|
The following is the coverage report on the affected files.
|
2e5673d to
d0ab42a
Compare
|
The following is the coverage report on the affected files.
|
|
/hold cancel |
d0ab42a to
0051cdd
Compare
|
The following is the coverage report on the affected files.
|
0051cdd to
617022b
Compare
|
The following is the coverage report on the affected files.
|
|
/test pull-tekton-operator-integration-tests |
617022b to
cf46a04
Compare
|
The following is the coverage report on the affected files.
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: savitaashture, vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
- With the addition of operator version config map getting created
in tektonConfig, the targetNamespace was getting created in
tektonConfig reconciler, but if tektonConfig is not installed
and tektonPipeline is supposed to installed alone then it won't
be installed as it would miss the targetNamespace. So this patch
checks for the targetNamespace in tektonPipeline reconciler, if
it is not present then it creates the targetNamespace and also
the operator version config map i.e. makes tektonPipeline
independent of tektonConfig
Signed-off-by: Puneet Punamiya <ppunamiy@redhat.com>
cf46a04 to
529511c
Compare
|
The following is the coverage report on the affected files.
|
Changes
With the addition of operator version config map
operators-infogetting created in tektonConfig, the targetNamespace was getting
created in tektonConfig reconciler, but if
tektonConfigis not installedand
tektonPipelineis supposed to installed alone then it won'tbe installed as it would miss the targetNamespace.
So this patch checks for the targetNamespace in
tektonPipelinereconciler, if it is not present then it creates the targetNamespace
and also the operator version config map i.e. makes tektonPipeline
independent of tektonConfig
Signed-off-by: Puneet Punamiya ppunamiy@redhat.com
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.
Release Notes