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
I am trying to create an Internal HTTP Load Balancer (for https redirect purposes). Even though I have specifed a Target HTTP Proxy for the Forwarding Rule, I get this error:
Warning UpdateFailed 35s (x10 over 8m46s) computeforwardingrule-controller Update call failed: error applying desired state: summary: Error creating ForwardingRule: googleapi: Error 400: Invalid value for field 'resource.target': ''. No target or backend service specified for forwarding rule., invalid
Client Version: v1.22.4
Server Version: v1.21.5-gke.1302
Config Connector Version
1.71.0
Config Connector Mode
Deployed from the install-bundles/install-bundle-workload-identity/ directory in this repo.
Log Output
{"severity":"error","timestamp":"2022-01-21T16:44:49.937Z","logger":"computeforwardingrule-controller","msg":"error applying desired state","resource":{"namespace":"default","name":"https-redirect-foo"},"error":"summary: Error creating ForwardingRule: googleapi: Error 400: Invalid value for field 'resource.target': ''. No target or backend service specified for forwarding rule., invalid"}
Hi @nstogner, I was able to reproduce your issue. This looks like a bug on our side where the regional ForwardingRule does not correctly support the resourceReferences to use the TargetHTTPProxyRef. I will add a fix to update this that should be added to next week's release.
Bug Description
I am trying to create an Internal HTTP Load Balancer (for https redirect purposes). Even though I have specifed a Target HTTP Proxy for the Forwarding Rule, I get this error:
Additional Diagnostic Information
Kubernetes Cluster Version
Client Version: v1.22.4
Server Version: v1.21.5-gke.1302
Config Connector Version
1.71.0
Config Connector Mode
Deployed from the
install-bundles/install-bundle-workload-identity/
directory in this repo.Log Output
Steps to Reproduce
Steps to reproduce the issue
Apply the yaml below replacing
my-project
.YAML snippets
The text was updated successfully, but these errors were encountered: