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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: