-
Notifications
You must be signed in to change notification settings - Fork 87
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
run ocm control plane as a standalone binary #43
Comments
@qiujian16 thanks, another obstacle in standalone mode is how to scale out etcd. i think we could probably start by leveraging an etcd-operator to make it dynamically scalable? or an one-replica etcd in the first phase, then we can opt-in to install an etcd-operator to manage/adopt the etcd. |
leaving items to resolve:
|
video uploaded. https://www.youtube.com/watch?v=fTaU9dncgHY @qiujian16 |
the unexpected informer error bug fixed @qiujian16 |
use external etcd allowed @qiujian16 |
add |
this is done /close |
@qiujian16: Closing this issue. 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. |
Signed-off-by: suigh <suigh@cn.ibm.com>
Co-authored-by: red-hat-konflux <123456+red-hat-konflux[bot]@users.noreply.github.com>
It will be interesting to run ocm control plane in stand alone mode. It will involve integrating apiserver/controller/etcd in one single binary. We should also disable unused APIs on apiserver (e.g. nodes, pods etc.). We can start with a prototype and check how kcp does this.
cc @yue9944882 @ycyaoxdu
/kind feature
The text was updated successfully, but these errors were encountered: