Skip to content
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

Investigate using watch API to refresh properties on K8sEnvironments #8

Open
xiaomi7732 opened this issue Apr 12, 2017 · 2 comments
Open
Assignees
Milestone

Comments

@xiaomi7732
Copy link
Member

No description provided.

@xiaomi7732 xiaomi7732 added this to the future milestone Apr 12, 2017
@xiaomi7732 xiaomi7732 self-assigned this Apr 12, 2017
@xiaomi7732 xiaomi7732 modified the milestones: vNext, future May 9, 2017
@xiaomi7732 xiaomi7732 modified the milestones: 1.0.0-beta2, future Jan 3, 2018
@xiaomi7732 xiaomi7732 modified the milestones: future, vNext Jan 12, 2018
@xiaomi7732 xiaomi7732 modified the milestones: vNext, future Feb 1, 2018
@xiaomi7732 xiaomi7732 modified the milestones: 1.0.0-beta5, future Feb 14, 2018
@xiaomi7732
Copy link
Member Author

Although the pull model is not ideal, it has been working. Watch, in theory, works better, the reliability is still a concern. Refer to issues like this for an example: kubernetes-client/csharp#884.

@xiaomi7732 xiaomi7732 modified the milestones: 6.0.0, backlog Jan 27, 2023
@xiaomi7732
Copy link
Member Author

One more data point: kubernetes-client/csharp#1168 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant