-
Notifications
You must be signed in to change notification settings - Fork 6
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
Implement Eventing Auth Kyma Controller #16
Conversation
Kyma controller watches Kyma CRs and creates EventingAuth CRs accordingly
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 should adapt the documentation
- Kyma CRD needs to be in the cluster for local development. I also see that we are not mentioning make install in Running on the cluster, it's only mentioned here.
- Running on the cluster is a little bit different, since KymaCR should be the trigger not EventingAuth
- EVENTING_AUTH_CR_NAME might be better replaced with KYMA_CR_NAME in the readme
* Prevent reconciling every minute * Improve documentation * Don't create/delete kcp-system namespace * Test improvements
controllers/kyma_controller.go
Outdated
if err != nil { | ||
if apiErrors.IsNotFound(err) { | ||
return ctrl.Result{ | ||
RequeueAfter: r.defaultRequeuePeriod, |
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 that in this case we should not set a RequeueAfter, otherwise this object will be constantly reconciled, even after deletion.
I think I'll remove the defaultRequeuePeriod
in my integration test PR, since this was only introduced to control the reconcile for the tests. And it's a better option set the SyncPeriod oder the manager used for the tests and keep the default behaviour.
RequeueAfter: r.defaultRequeuePeriod, |
Description
Implement Kyma Controller that watchers Kyma CR and creates a EventingAuth CR correspondingly.
Changes proposed in this pull request:
Related issue(s)
#13