Skip to content

Deprecate spec.scaleTargetRef.deployment #1061

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

Closed
zroubalik opened this issue Jun 7, 2024 · 3 comments · Fixed by #1060
Closed

Deprecate spec.scaleTargetRef.deployment #1061

zroubalik opened this issue Jun 7, 2024 · 3 comments · Fixed by #1060

Comments

@zroubalik
Copy link
Member

Proposal

Let's deprecate this field to be able to support more types, not just Deployments. The same way it is done for KEDA.

kind: HTTPScaledObject
...
spec:
...
    scaleTargetRef:
        deployment: xkcd
        service: xkcd
        port: 8080

->

kind: HTTPScaledObject
...
spec:
...
    scaleTargetRef:
        name: xkcd
        kind: Deployment
        apiVersion: apps/v1
        service: xkcd
        port: 8080

Use-Case

No response

Is this a feature you are interested in implementing yourself?

Yes

Anything else?

No response

@Leonardo-Ferreira
Copy link

Leonardo-Ferreira commented Mar 26, 2025

Does version 0.8 of the http interceptor accepts this contract? Im currently at v8 intending to go to v10

@zroubalik
Copy link
Member Author

zroubalik commented Mar 26, 2025

v10 doesn't have this field, let's use the new one:

type ScaleTargetRef struct {
// +optional
Name string `json:"name"`
// +optional
APIVersion string `json:"apiVersion,omitempty"`
// +optional
Kind string `json:"kind,omitempty"`
// The name of the service to route to
Service string `json:"service"`
// The port to route to
Port int32 `json:"port,omitempty"`
// The port to route to referenced by name
PortName string `json:"portName,omitempty"`
}

wrt migration, v8 supports the new field, so you should be good.

@Leonardo-Ferreira
Copy link

wrt migration, v8 supports the new field, so you should be good.

thanks a lot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants