Closed dcfranca closed 3 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
/reopen
@vedant15188: You can't reopen an issue/PR unless you authored it or you are a collaborator.
Hello all,
I'm not sure if this is the right place, maybe there is a simple solution, but I have been struggling with this use case, so I'll post it here and I hope someone point me to the right direction
I have an operator (based on KNative eventing) that needs to run in 2 different versions of Kubernetes (1.19 and 1.27) Those operators create HPA resources
These are the apiversions of
autoscaling
on each cluster:1.19
1.27
Until now, we only had 1.19, and it was working fine creating HPA
v2beta2
, but as you can see the new cluster doesn't have autoscaling v2beta2, so we need to migrate it to eitherv1
orv2
v1
is not an option as it doesn't support scaling with Memoryv2
is not available on the1.19
cluster, so first I tried using a code similar to this:EDIT: I also have added the conditional when adding the event handler
It doesn't work as expected and even tho I have a conditional it tries to watch the resource not available on the cluster, throwing the errors:
If we look at the line mentioned there
controller.go:732
it is the line that calls theRun
method of the InformersI have tried using an interface, and also using generics, but didn't go far, always ended up on some sort of limitation I have commented out the version not available in the cluster and then I was able to run it successful, but of course, this is not ideal
Any idea how to achieve this?