-
Notifications
You must be signed in to change notification settings - Fork 401
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
[feature request] Set K8s service host & port to Yurthub Proxy Host & Port in Yurthub Component #2158
Comments
masterServiceFilter has already implemented this capability. By default, Yurthub only caches request data for system components. If the business requires utilizing Yurthub's cache to operate during network outages, the corresponding User-Agent (UA) needs to be configured in the ConfigMap yurt-hub-cfg. reference: https:/openyurtio/openyurt/blob/master/docs/proposals/20220627-yurthub-cache-refactoring.md#41-enable-yurthub-to-distinguish-resources-with-same-name-but-different-versions-and-groups |
@zyjhtangtang I think that masterservice Filter can not solve the problem that mentioned in the issue. because masterservice filter only modify |
@techworldhello Thank you for raising the issue. Only pods without |
@techworldhello @rambohe-ch Yes, if the pod has already been set with |
@zyjhtangtang @rambohe-ch I've updated this issue to link to a new PR #2165, as it made sense to update |
What would you like to be added:
A filter in Yurthub that sets the
KUBERNETES_SERVICE_HOST
andKUBERNETES_SERVICE_PORT
environment variables to the Yurthub proxy host and IP. This enhancement would ensure node autonomy for edge nodes when they are operating offline.Why is this needed:
Some managed services may use an admission webhook to modify the
KUBERNETES_SERVICE_HOST
andKUBERNETES_SERVICE_PORT
environment variables, setting them to the public FQDN and port of the kube-apiserver. For these managed services to operate with Yurthub, the pods scheduled on edge nodes must be directed to Yurthub so that requests to the kube-apiserver can be proxied through it.We are requesting the implementation of a filter that would ensure all edge pods access the kube-apiserver via the Yurthub proxy. This filter would add logic without disrupting other users. If a user prefers to disable this filter in the future, they could do so by adding it to the --disabled-resource-filters startup parameter.
others
/kind feature
The text was updated successfully, but these errors were encountered: