You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we don't store jobNamespace as part of function metadata. If the broker restarts with a different job namespace, it will cause the function statefulset not deleted in the original job namespace and a new statefulset is created in the new job namespace.
In order to address the issue, we should consider adding the job namespace as part of function metadata when the function is created. Eventually, we should support updating the job namespace and handle the case the job namespace is changed at the function worker side.
This discussion was converted from issue #7743 on December 09, 2022 13:28.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Motivation
Currently, we don't store jobNamespace as part of function metadata. If the broker restarts with a different job namespace, it will cause the function statefulset not deleted in the original job namespace and a new statefulset is created in the new job namespace.
In order to address the issue, we should consider adding the job namespace as part of function metadata when the function is created. Eventually, we should support updating the job namespace and handle the case the job namespace is changed at the function worker side.
Beta Was this translation helpful? Give feedback.
All reactions