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

Why can't ApisixRouteHTTPBackend cross-namespace? #2286

Closed
Tanc010 opened this issue Aug 27, 2024 · 1 comment
Closed

Why can't ApisixRouteHTTPBackend cross-namespace? #2286

Tanc010 opened this issue Aug 27, 2024 · 1 comment

Comments

@Tanc010
Copy link

Tanc010 commented Aug 27, 2024

Description

// ApisixRouteHTTPBackend represents an HTTP backend (a Kubernetes Service).
type ApisixRouteHTTPBackend struct {
// The name (short) of the service, note cross namespace is forbidden,
// so be sure the ApisixRoute and Service are in the same namespace.
ServiceName string json:"serviceName" yaml:"serviceName"
// The service port, could be the name or the port number.
ServicePort intstr.IntOrString json:"servicePort" yaml:"servicePort"
// The resolve granularity, can be "endpoints" or "service",
// when set to "endpoints", the pod ips will be used; other
// wise, the service ClusterIP or ExternalIP will be used,
// default is endpoints.
ResolveGranularity string json:"resolveGranularity,omitempty" yaml:"resolveGranularity,omitempty"
// Weight of this backend.
Weight *int json:"weight" yaml:"weight"
// Subset specifies a subset for the target Service. The subset should be pre-defined
// in ApisixUpstream about this service.
Subset string json:"subset,omitempty" yaml:"subset,omitempty"
}

@Tanc010 Tanc010 closed this as completed Aug 27, 2024
@Tanc010
Copy link
Author

Tanc010 commented Aug 27, 2024

Repeated problem

@Tanc010 Tanc010 reopened this Aug 27, 2024
@Tanc010 Tanc010 closed this as completed Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant