Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Matching by selector doesn't work for some resources #568

Closed
1 task done
Bluesboy opened this issue Jul 12, 2024 · 2 comments
Closed
1 task done

[Bug]: Matching by selector doesn't work for some resources #568

Bluesboy opened this issue Jul 12, 2024 · 2 comments
Labels
bug Something isn't working needs:triage stale

Comments

@Bluesboy
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Affected Resource(s)

compute.gcp.upbound.io/v1beta2 - BackendService
compute.gcp.upbound.io/v1beta2 - URLMap
compute.gcp.upbound.io/v1beta2 - GlobalForwardingRule

Resource MRs required to reproduce the bug

Backend Service manifest:

apiVersion: compute.gcp.upbound.io/v1beta2
kind: BackendService
metadata:
  name: example-backend-service
  labels:
    example-label: test-selector
spec:
  forProvider:
    loadBalancingScheme: EXTERNAL_MANAGED

URLMap manifest:

apiVersion: compute.gcp.upbound.io/v1beta2
kind: URLMap
metadata:
  name: example-url-map
  labels:
    example-label: test-selector
spec:
  forProvider:
    defaultServiceSelector:
      matchLabels:
        example-label: test-selector

Steps to Reproduce

Create BackendService resource, refer it in URLMap resource and apply it.

What happened?

ReconcileError in URLMap resourse

Relevant Error Output Snippet

cannot resolve references: mg.Spec.ForProvider.DefaultService: no resources matched selector

Crossplane Version

1.16.0

Provider Version

1.5.0

Kubernetes Version

v1.30.1-gke.1329003

Kubernetes Distribution

GKE

Additional Info

Same thing happening with GlobalForwardingRule, if I refer by selector to TargetHTTPProxy with targetSelector, however ipAddressSelector works fine.

If I'm trying to refer to the BackendService with defaultServiceRef, resource give me
cannot resolve references: mg.Spec.ForProvider.DefaultService: cannot get referenced resource: BackendBucket.compute.gcp.upbound.io "example-backend-service" not found

@Bluesboy Bluesboy added bug Something isn't working needs:triage labels Jul 12, 2024
Copy link

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Oct 10, 2024
Copy link

This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs:triage stale
Projects
None yet
Development

No branches or pull requests

1 participant