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 Ingress controller performs periodic checks of service account permissions by fetching a test resource from your Google Cloud project. You will see this as a GET of the (non-existent) global BackendService with the name k8s-ingress-svc-acct-permission-check-probe. As this resource should not normally exist, the GET request will return "not found". This is expected; the controller is checking that the API call is not rejected due to authorization issues. If you create a BackendService with the same name, then the GET will succeed instead of returning "not found". - https://cloud.google.com/kubernetes-engine/docs/concepts/ingress#implementation_details
The resource 'projects/plt-k8s-tf39-sb/global/backendServices/k8s-ingress-svc-acct-permission-check-probe' was not found
Required 'compute.firewalls.get' permission for 'projects/plt-lz-networking-tfd8-sb/global/firewalls/gke-services-us-east4-a-009ac074-mcsd
compute.google.apis
The Ingress controller performs periodic checks of service account permissions by fetching a test resource from your Google Cloud project. You will see this as a GET of the (non-existent) global BackendService with the name k8s-ingress-svc-acct-permission-check-probe. As this resource should not normally exist, the GET request will return "not found". This is expected; the controller is checking that the API call is not rejected due to authorization issues. If you create a BackendService with the same name, then the GET will succeed instead of returning "not found". - https://cloud.google.com/kubernetes-engine/docs/concepts/ingress#implementation_details
trafficdirector.googleapis.com
The text was updated successfully, but these errors were encountered: