-
Notifications
You must be signed in to change notification settings - Fork 203
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
Fix to deploy TektonHub in custom namespace #1865
Conversation
The following is the coverage report on the affected files.
|
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.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester 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 |
/hold With this PR we are removing the deletion part completely. I need sometime to verify this change. Thanks for the PR @pratap0007 |
why do we want to delete all other namespaces other than |
4632397
to
9290eba
Compare
The following is the coverage report on the affected files.
|
4f3fc26
to
d18c7ef
Compare
/remove-hold |
d18c7ef
to
cfe514b
Compare
ObjectMeta: metav1.ObjectMeta{ | ||
Name: th.Spec.TargetNamespace, | ||
}, | ||
} |
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 think we need to add the ownerRef as well
cc @jkandasa @piyush-garg
cfe514b
to
14c7d81
Compare
"targetNamespace", th.Spec.GetTargetNamespace(), | ||
err, | ||
) | ||
tc, _ := r.operatorClientSet.OperatorV1alpha1().TektonConfigs().Get(ctx, v1alpha1.ConfigResourceName, metav1.GetOptions{}) |
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 still feel this would not work when TektonConfig is nil
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.
can you please explain the case when TektonConfig could be nil, so I can check once this ?
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.
Meaning TektonHub is independent of TekttonConfig, so ideally we should not check for the namespace of TektonConfig, we can directly check if the namespace mentioned in TektonHub is present or not and based on that we can directly create that
For ref: 51fff50#diff-1c3da4772ce1a38a45935ea0814741d91d7803c96d9aef2b0f10b00f6d8b33f3L864-L875
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, thank you
c075649
to
5ddd585
Compare
5ddd585
to
540be87
Compare
This will add the fix for targetnamespace deletion it will delete the namespace only if namespace contains ownerreference of same reconcilation Signed-off-by: Shiv Verma<[email protected]>
540be87
to
6b32b71
Compare
The following is the coverage report on the affected files.
|
/test pull-tekton-operator-integration-tests |
/lgtm |
/cherry-pick release-v0.69.x |
@pratap0007: new pull request created: #2050 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/test-infra repository. |
Changes
This will add the fix for targetnamespace deletion
it will delete the namespace only if namespace contains
ownerreference of same reconcilation
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
make test lint
before submitting a PRSee the contribution guide for more details.
Release Notes