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
While the default "safe" choice when inheriting an existing configuration is to not inherit labels and annotations, there will clearly be cases where doing so is beneficial. The current behavior is largely there to prevent inheriting configuration for a pod that is selected by a service, because that would cause the kdo pod to be automatically included in load balancing for the service.
It's possible that the current default is wrong. Options are:
By default, the --inherit flag means inherit everything, and there's a way to opt out of inheriting labels and annotations (just like there is to not inherit lifecycle and probes);
The current default makes sense and inheriting labels and annotations are opt-in;
The default is "smart" based on whether what is being inherited is a service or not.
The text was updated successfully, but these errors were encountered:
While the default "safe" choice when inheriting an existing configuration is to not inherit labels and annotations, there will clearly be cases where doing so is beneficial. The current behavior is largely there to prevent inheriting configuration for a pod that is selected by a service, because that would cause the kdo pod to be automatically included in load balancing for the service.
It's possible that the current default is wrong. Options are:
The text was updated successfully, but these errors were encountered: