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

[v2] when a connector is created in CLI using selector flag, a matching running pods must exist, or the command will timeout #1667

Open
lynnemorrison opened this issue Sep 19, 2024 · 0 comments
Assignees

Comments

@lynnemorrison
Copy link
Collaborator

lynnemorrison commented Sep 19, 2024

If you specify a selector instead of a host, then the associated connector(s) will only be configured when that selector
resolves to one or more running pods. As an enhancement to the connector CLI command, I thought it would be useful
to lookup if the pods exist and if not then return a warning indicating the failure. Currently the code will wait for the
timeout and then report an error. This is really not an error, it is just there is currently no matching pod. If a pod is
added later the connector CRD is updated with a configured condition.

@lynnemorrison lynnemorrison self-assigned this Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant