Replies: 4 comments
-
The kubernetes way is to create a status field in your CR for the remote ID and store it there. Then use that field value to poll the remote state. |
Beta Was this translation helpful? Give feedback.
-
👆 What @bobh66 said above, plus Kopf's daemons and/or timers to poll the status of the remote entity and do something when it changes. |
Beta Was this translation helpful? Give feedback.
-
Thank you all of you (@bobh66, @nolar) for your quick responses. Last question as I do not know all the internal of kubernetes : Is it safe to store the data on the status of the CR. As this part seems to be editable with kubectl |
Beta Was this translation helpful? Give feedback.
-
It's as safe as any other field - spec and metadata are also editable via kubectl |
Beta Was this translation helpful? Give feedback.
-
I we would like to create an operator that works with an external API. This API will be slow (about 1h) to realize the change. For earch CR (instance of the new CRD), we will make a call. The API will reply with an objectID, that we could use to poll the status. How can we store this objectID (in a k8s way). And which pattern should we use to follow a such long process.
Do you have any example on how to do this ?
Thanks in advance for your help !
Beta Was this translation helpful? Give feedback.
All reactions