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
The spec.proxy field and 'proxy' key in secrets are no longer
supported. These fields were deprecated in v2.7 with the introduction
of spec.proxySecretRef as the recommended approach.
Signed-off-by: cappyzawa <[email protected]>
returnnil, nil, fmt.Errorf("invalid 'proxy' in secret '%s/%s'", secret.Namespace, secret.Name)
324
-
}
325
-
log.FromContext(ctx).Error(nil, "warning: specifying proxy with 'proxy' key in the referenced secret is deprecated, use spec.proxySecretRef with 'address' key instead. Support for the 'proxy' key will be removed in v1.")
err:=errors.New("specifying proxy with 'proxy' key in the referenced secret is deprecated, use spec.proxySecretRef with 'address' key instead. Support for the 'proxy' key is removed in v1")
321
+
log.FromContext(ctx).Error(err, "no longer supported.")
// TODO: Remove deprecated proxy handling when Provider v1 is released.
384
-
ifprovider.Spec.Proxy!="" {
385
-
log.FromContext(ctx).Error(nil, "warning: spec.proxy is deprecated, please use spec.proxySecretRef instead. Support for this field will be removed in v1.")
0 commit comments