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
Is your feature request related to a problem? Please describe.
The CLI supports a --workload option, it should use the value of that option to obtain the selector and create the connector custom resource with that selector.
Describe the solution you'd like
The --workload flag will contain the value /resource-name>, e.g. --workload
deployment/backend. These are the resource types to check.
services
daemonsets
deployments
statefulsets
Additional context
This feature will be available only for kube platforms.
The text was updated successfully, but these errors were encountered:
nluaces
changed the title
CLI should use workload flag to get the selector and assign it to the connector custom resource
[v2] CLI should use workload flag to get the selector and assign it to the connector custom resource
Aug 22, 2024
Is your feature request related to a problem? Please describe.
The CLI supports a --workload option, it should use the value of that option to obtain the selector and create the connector custom resource with that selector.
Describe the solution you'd like
The
--workload
flag will contain the value /resource-name>, e.g. --workloaddeployment/backend. These are the resource types to check.
Additional context
This feature will be available only for kube platforms.
The text was updated successfully, but these errors were encountered: