-
Notifications
You must be signed in to change notification settings - Fork 191
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
Pipeline deployment deletion can not kick off the reconcile function, leading to no deployment recreation #25
Comments
@nikhil-thomas I have not found out the reason. Do you have any clue? |
At present, the operator doesnot have that logic built into it. In the current implemetation, the deployment deletion event will be detected by the reconcile function, but it will be ignored either here:
or here:
|
we need to add the |
@nikhil-thomas I try to use
So I guess to resolve the issue, we need enhance |
@nikhil-thomas Here is what I found: if the reason is due to the IGNORE logic, then we should have at least the log message "" shows up, as "log.Info("reconciling config change")", but when I deleted the deployment, this message did not pop up in the log, which means the reconcile was not kicked off by the deployment deletion. @vincent-pli I was guessing it might be the reason you mentioned(serving-operator is using the a namespace-scope CR and the deployment change can call the reconcile function), but not verified so far. |
@vincent-pli, @houshengbo, thank you for catching it and filing an issue in operator-sdk project. I have raised a query in |
i got a reply from operator-sdk team
|
and
https://coreos.slack.com/archives/C3VS0LV41/p1566225013185700 |
in my opinion, let us wait for the operator-sdk update. it should be an simple change for us. |
@nikhil-thomas @houshengbo @vincent-pli
Please help me understand this better. Here is the test that I ran
Noticed the reconcile does indeed get called but it is ignored
If you don't see Reconcile being called, could you please ensure
the deployments have the Is this different to what you see? |
did you try deleting either the tekton-pipeline-controller or tekton-pipeline-webhook deployments |
of course :) |
@sthaha
It's about a |
@houshengbo @vincent-pli in |
That is what is expected. Operator-sdk give you a referece to the From a kubernetes stand point it makes sense ( Edge-Triggered: we get a notification that something has happened |
@vincent-pli, @houshengbo |
I use the standard approach, install |
in the context of this issue, the reconcile will be triggered if we use the
When we set `--namespace="", the operator watches all namespaces
We do this while development using Line 24 in 2273b82
I found out just now which is incorrectly set :) |
i have pushed a fix here: |
@nikhil-thomas |
@houshengbo shall we close this issue |
@nikhil-thomas I will verify it today. Thx. |
We close it, since it has been resolved. Next, we should make sure the deployment can be recreated after deletion. |
Using tkn-aac-sa as SA and using nightly-ci-github-hub-token
Expected Behavior
pipeline deployment deletion should kick off reconcile func, so that the pipeline deployment can be recreated.
Actual Behavior
no recreation of deployment, though deployment is registered:
Steps to Reproduce the Problem
Additional Info
The text was updated successfully, but these errors were encountered: