lyft / lyft/flinkk8soperator

HPA failed status - unknow FlinkApplication / not found

Open
#247 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
581
Forks
153
PR merge metrics
No merged PRs in 30d

Description

I've created FlinkApplication cluster. After I've create a HPA with scaleTargetRef.. but hpa describe never find the new object FlinkApplication cluster "flinkoperator":

Cluster Green ok:

NAME                       PHASE     CLUSTER HEALTH   JOB HEALTH   JOB RESTARTS   AGE
flinkoperator   Running   Green            Green                       34m
Conditions:
  Type         Status  Reason          Message
  ----         ------  ------          -------
  AbleToScale  False   FailedGetScale  the HPA controller was unable to get the target's current scale: flinkapplications.flink.k8s.io "flinkoperator" not found
Events:
  Type     Reason          Age   From                       Message
  ----     ------          ----  ----                       -------
  Warning  FailedGetScale  8s    horizontal-pod-autoscaler  flinkapplications.flink.k8s.io "flinkoperator" not found
NAME                           REFERENCE                                   TARGETS                            MINPODS   MAXPODS   REPLICAS   AGE
flinkoperator-hpa   FlinkApplication/flinkoperator   <unknown>/14100Mi, <unknown>/95%   9         12        0          11m

Flink version: 1.9.2
AKS version:

% kubectl version             
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-17T15:48:33Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"10428892c761e8ca8908e71146eea4751feb545b", GitTreeState:"clean", BuildDate:"2021-11-15T08:35:11Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the HPA failure with the reported FlinkApplication and Kubernetes versions, using the HPA description and object status as the initial evidence. Trace how the operator exposes the FlinkApplication as an HPA scale target; done means the HPA finds the target and reports current replicas and metrics instead of “not found”.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.