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
{{ message }}
This repository has been archived by the owner on May 6, 2020. It is now read-only.
The proxy should not (cannot) handle KSM now that an instance is being
launched per pod.
Partially fixesclearcontainers#176.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Socket activation is no longer required since a proxy instance
is launched by the runtime for each pod.
Fixesclearcontainers#176.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
The proxy should not (cannot) handle KSM now that an instance is being
launched per pod.
Partially fixesclearcontainers#176.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Socket activation is no longer required since a proxy instance
is launched by the runtime for each pod.
Fixesclearcontainers#176.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Now that the proxy can be run on a per pod/VM basis rather than as a host-level daemon service, we don't need socket activation or KSM.
See clearcontainers/runtime#795 which covers what the KSM functionality in the proxy will be replaced by.
The text was updated successfully, but these errors were encountered: