Intermittent error when doing kubectl apply -f for a HorizontalPodAutoscaler: 'unable to find api field in struct HorizontalPodAutoscalerSpec for the json field "scaleTargetRef"' #34413

bes · 2016-10-09T12:42:31Z

What keywords did you search in Kubernetes issues before filing this one?

unable to find api field in struct HorizontalPodAutoscalerSpec for the json field "scaleTargetRef"
HorizontalPodAutoscaler
scaleTargetRef

Also searched google/stackoverflow

Is this a BUG REPORT or FEATURE REQUEST?
Bug report

Kubernetes version (use kubectl version):
v1.4.0

Environment:

GKE with kubernetes v1.4.0

What happened:
Do kubectl apply -f my-service.yaml

Intermittently, since upgrading to 1.4.0 I have been getting

error: error when applying patch:

to:
&{0xc8203546c0 0xc8202e3340 default my-service-horizpodautoscaler /my-service/build/k8s/my-service.yaml &HorizontalPodAutoscaler{ObjectMeta:k8s_io_kubernetes_pkg_api_v1.ObjectMeta{Name:my-service-horizpodautoscaler,GenerateName:,Namespace:,SelfLink:,UID:,ResourceVersion:,Generation:0,CreationTimestamp:0001-01-01 00:00:00 +0000 UTC,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{},Annotations:map[string]string{kubectl.kubernetes.io/last-applied-configuration: ,},OwnerReferences:[],Finalizers:[],ClusterName:,},Spec:HorizontalPodAutoscalerSpec{ScaleTargetRef:CrossVersionObjectReference{Kind:Deployment,Name:my-service-frontend,APIVersion:extensions/v1beta1,},MinReplicas:*1,MaxReplicas:3,TargetCPUUtilizationPercentage:nil,},Status:HorizontalPodAutoscalerStatus{ObservedGeneration:nil,LastScaleTime:<nil>,CurrentReplicas:0,DesiredReplicas:0,CurrentCPUUtilizationPercentage:nil,},} &TypeMeta{Kind:,APIVersion:,} 1537793 false}
for: "/my-service/build/k8s/my-service.yaml": error when creating patch with:
original:
{"kind":"HorizontalPodAutoscaler","apiVersion":"autoscaling/v1","metadata":{"name":"my-service-horizpodautoscaler","creationTimestamp":null},"spec":{"scaleTargetRef":{"kind":"Deployment","name":"my-service-frontend","apiVersion":"extensions/v1beta1"},"minReplicas":1,"maxReplicas":3},"status":{"currentReplicas":0,"desiredReplicas":0}}
modified:
{"kind":"HorizontalPodAutoscaler","apiVersion":"autoscaling/v1","metadata":{"name":"my-service-horizpodautoscaler","creationTimestamp":null,"annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{\"kind\":\"HorizontalPodAutoscaler\",\"apiVersion\":\"autoscaling/v1\",\"metadata\":{\"name\":\"my-service-horizpodautoscaler\",\"creationTimestamp\":null},\"spec\":{\"scaleTargetRef\":{\"kind\":\"Deployment\",\"name\":\"my-service-frontend\",\"apiVersion\":\"extensions/v1beta1\"},\"minReplicas\":1,\"maxReplicas\":3},\"status\":{\"currentReplicas\":0,\"desiredReplicas\":0}}"}},"spec":{"scaleTargetRef":{"kind":"Deployment","name":"my-service-frontend","apiVersion":"extensions/v1beta1"},"minReplicas":1,"maxReplicas":3},"status":{"currentReplicas":0,"desiredReplicas":0}}
current:
{"kind":"HorizontalPodAutoscaler","apiVersion":"extensions/v1beta1","metadata":{"name":"my-service-horizpodautoscaler","namespace":"default","selfLink":"/apis/autoscaling/v1/namespaces/default/horizontalpodautoscalers/my-service-horizpodautoscaler","uid":"REDACTED-REDA-REDA-REDA-REDACTED","resourceVersion":"1537793","creationTimestamp":"2016-09-28T15:51:27Z","annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{\"kind\":\"HorizontalPodAutoscaler\",\"apiVersion\":\"autoscaling/v1\",\"metadata\":{\"name\":\"my-service-horizpodautoscaler\",\"creationTimestamp\":null},\"spec\":{\"scaleTargetRef\":{\"kind\":\"Deployment\",\"name\":\"my-service-frontend\",\"apiVersion\":\"extensions/v1beta1\"},\"minReplicas\":1,\"maxReplicas\":3},\"status\":{\"currentReplicas\":0,\"desiredReplicas\":0}}"}},"spec":{"scaleRef":{"kind":"Deployment","name":"my-service-frontend","apiVersion":"extensions/v1beta1","subresource":"scale"},"minReplicas":1,"maxReplicas":3,"cpuUtilization":{"targetPercentage":80}},"status":{"lastScaleTime":"2016-10-08T23:19:12Z","currentReplicas":1,"desiredReplicas":1,"currentCPUUtilizationPercentage":0}}

for: "/my-service/build/k8s/my-service.yaml": unable to find api field in struct HorizontalPodAutoscalerSpec for the json field "scaleTargetRef"

As you can see, it seems that the "current" metadata specifies "apiVersion" as extensions/v1beta1, that might be correct, but it seems suspicious to me...

I have the feeling it works every second time I do apply, but hard to say from my small sample size.

What you expected to happen:
The apply to work every time.

How to reproduce it

I used this yaml file (cleaned)

apiVersion: v1
kind: Service
metadata:
  name: my-service
  labels:
    app: my-service
    tier: frontend
spec:
  type: NodePort
  ports:
  - name: http8080
    protocol: TCP
    port: 8080
    targetPort: 8080
  selector:
    app: my-service
    tier: frontend

---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: my-service-frontend
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: my-service
        tier: frontend
    spec:
      containers:
      - name: my-service
        image: eu.gcr.io/my-project/my-service:v0.0.0
        env:
        - name: MY_ENVIRONMENT
          value: dev
        ports:
        - containerPort: 8080
        resources:
          requests:
            cpu: 100m
            memory: 800Mi

---
apiVersion: autoscaling/v1 #I've tried with extensions/v1beta1 and "scaleRef" below, but that doesn't work properly either (similar error message)
kind: HorizontalPodAutoscaler
metadata:
  name: my-service-horizpodautoscaler
spec:
  scaleTargetRef:
    kind: Deployment
    name: my-service-frontend
    apiVersion: extensions/v1beta1 #I've tried with and without this, makes no difference
  minReplicas: 1
  maxReplicas: 3

Anything else do we need to know:

GET on clusters using https://cloud.google.com/container-engine/reference/rest/v1/projects.zones.clusters/get reveals:

[...]
 "addonsConfig": {
  "httpLoadBalancing": {
  },
  "horizontalPodAutoscaling": {
  }
 },
[...]
   "initialNodeCount": 1,
   "autoscaling": {
    "enabled": true,
    "minNodeCount": 1,
    "maxNodeCount": 3
   },
[...]

 "initialClusterVersion": "1.3.6",
 "currentMasterVersion": "1.4.0",
 "currentNodeVersion": "1.4.0",

To solve this I have temporarily moved the HPA section out of the file into a separate file, but I prefer having the complete configuration in one place.

Am I doing something wrong?

Thanks!

The text was updated successfully, but these errors were encountered:

bes · 2016-10-09T15:00:50Z

Tried deleting the hpa using kubectl delete hpa my-service-horizpodautoscaler and then reapplying. Worked first time (no errors) and the hpa was created. Waited a few minutes then applied again, and got the same error.

pwittrock · 2016-10-13T22:11:47Z

Does this work consistently if the the hpa is in a different file?

bes · 2016-10-14T06:12:35Z

@pwittrock No, it's the same thing. Every other time it seems to work.

pwittrock · 2016-10-16T18:10:27Z

@ymqytw Would you look into this one as well?

mengqiy · 2016-10-18T16:06:54Z

@pwittrock Yeah, I will look into this issue.

ajohnstone · 2016-10-19T11:22:49Z

Getting this issue too on 1.4.3

Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.3", GitCommit:"4957b090e9a4f6a68b4a40375408fdc74a212260", GitTreeState:"clean", BuildDate:"2016-10-16T06:36:33Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.3", GitCommit:"4957b090e9a4f6a68b4a40375408fdc74a212260", GitTreeState:"clean", BuildDate:"2016-10-16T06:20:04Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

11:03:39 INFO:k8s.kubernetes:kubectl --context=test-xxx-xxx.xx-xxx.photobox.com --namespace=development apply -f deploy/kubernetes;
11:03:39 error: error when applying patch:
11:03:39 
11:03:39 to:
11:03:39 &{0xc8200b4e40 0xc82034c460 development smash-website deploy/kubernetes/hpa.yaml &HorizontalPodAutoscaler{ObjectMeta:k8s_io_kubernetes_pkg_api_v1.ObjectMeta{Name:smash-website,GenerateName:,Namespace:,SelfLink:,UID:,ResourceVersion:,Generation:0,CreationTimestamp:0001-01-01 00:00:00 +0000 UTC,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{},Annotations:map[string]string{kubectl.kubernetes.io/last-applied-configuration: ,},OwnerReferences:[],Finalizers:[],ClusterName:,},Spec:HorizontalPodAutoscalerSpec{ScaleTargetRef:CrossVersionObjectReference{Kind:Deployment,Name:smash-website,APIVersion:extensions/v1beta1,},MinReplicas:*1,MaxReplicas:10,TargetCPUUtilizationPercentage:*45,},Status:HorizontalPodAutoscalerStatus{ObservedGeneration:nil,LastScaleTime:<nil>,CurrentReplicas:0,DesiredReplicas:0,CurrentCPUUtilizationPercentage:nil,},} &TypeMeta{Kind:,APIVersion:,} 629103 false}
11:03:39 for: "deploy/kubernetes/hpa.yaml": error when creating patch with:
11:03:39 original:
11:03:39 {"kind":"HorizontalPodAutoscaler","apiVersion":"autoscaling/v1","metadata":{"name":"smash-website","creationTimestamp":null},"spec":{"scaleTargetRef":{"kind":"Deployment","name":"smash-website","apiVersion":"extensions/v1beta1"},"minReplicas":1,"maxReplicas":10,"targetCPUUtilizationPercentage":45},"status":{"currentReplicas":0,"desiredReplicas":0}}
11:03:39 modified:
11:03:39 {"kind":"HorizontalPodAutoscaler","apiVersion":"autoscaling/v1","metadata":{"name":"smash-website","creationTimestamp":null,"annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{\"kind\":\"HorizontalPodAutoscaler\",\"apiVersion\":\"autoscaling/v1\",\"metadata\":{\"name\":\"smash-website\",\"creationTimestamp\":null},\"spec\":{\"scaleTargetRef\":{\"kind\":\"Deployment\",\"name\":\"smash-website\",\"apiVersion\":\"extensions/v1beta1\"},\"minReplicas\":1,\"maxReplicas\":10,\"targetCPUUtilizationPercentage\":45},\"status\":{\"currentReplicas\":0,\"desiredReplicas\":0}}"}},"spec":{"scaleTargetRef":{"kind":"Deployment","name":"smash-website","apiVersion":"extensions/v1beta1"},"minReplicas":1,"maxReplicas":10,"targetCPUUtilizationPercentage":45},"status":{"currentReplicas":0,"desiredReplicas":0}}
11:03:39 current:
11:03:39 {"kind":"HorizontalPodAutoscaler","apiVersion":"extensions/v1beta1","metadata":{"name":"smash-website","namespace":"development","selfLink":"/apis/autoscaling/v1/namespaces/development/horizontalpodautoscalers/smash-website","uid":"a9e65e5a-9539-11e6-bc5e-0645d95d0de3","resourceVersion":"629103","creationTimestamp":"2016-10-18T13:49:17Z","annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{\"kind\":\"HorizontalPodAutoscaler\",\"apiVersion\":\"autoscaling/v1\",\"metadata\":{\"name\":\"smash-website\",\"creationTimestamp\":null},\"spec\":{\"scaleTargetRef\":{\"kind\":\"Deployment\",\"name\":\"smash-website\",\"apiVersion\":\"extensions/v1beta1\"},\"minReplicas\":1,\"maxReplicas\":10,\"targetCPUUtilizationPercentage\":45},\"status\":{\"currentReplicas\":0,\"desiredReplicas\":0}}","kubernetes.io/change-cause":"kubectl --context=test-xxx-xxx.xx-xxx.photobox.com --namespace=development --record=true apply -f deploy/kubernetes"}},"spec":{"scaleRef":{"kind":"Deployment","name":"smash-website","apiVersion":"extensions/v1beta1","subresource":"scale"},"minReplicas":1,"maxReplicas":10,"cpuUtilization":{"targetPercentage":45}},"status":{"currentReplicas":2,"desiredReplicas":0}}
11:03:39 
11:03:39 for: "deploy/kubernetes/hpa.yaml": unable to find api field in struct HorizontalPodAutoscalerSpec for the json field "scaleTargetRef"
11:03:39 ERROR:k8s.kubernetes:stdout output:
11:03:39 deployment "smash-website" configured
11:03:39 service "smash-website-int" configured
11:03:39 service "smash-website" configured

yaml

apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
  name: smash-website
spec:
  maxReplicas: 10
  minReplicas: 1
  scaleTargetRef:
    apiVersion: extensions/v1beta1
    kind: Deployment
    name: smash-website
  targetCPUUtilizationPercentage: 45

mengqiy · 2016-10-19T18:36:55Z

It happens on 1.4.0 and HEAD.
I observed the APIVersion is wrong sometimes when using encoder to encode a internal object
Sometimes it has "apiVersion":"autoscaling/v1" which is correct, but sometimes it has "apiVersion":"extensions/v1beta1" which is wrong.

I think there is something wrong with the encoder genertaed by codec.
@smarterclayton

smarterclayton · 2016-10-19T21:19:12Z

It's possible that we are not forcing the stored version into a stable apiVersion/group, and so when the HPA controller runs it mutates the object via one name (extensions?) and when the user runs it updates via (autoscaling), and so the user action fails. There is code in the storage codec (storage_factory.go) that should force objects from either type into a single version when stored in etcd. That's probably the first place to look. If that's not stable then multiple clients can cause this problem.

bgrant0607 · 2016-10-21T23:40:38Z

See also #23378, #22866

devth · 2016-10-24T19:02:01Z

This busted our CD system for any repos that contain HPA manifests. Details:

Started happening 10/17 on our GKE cluster.
The cluster was upgraded to 1.4.0 on 10/4.
Masters were upgraded to 1.4.3 on 10/16.

mengqiy · 2016-10-24T20:35:19Z

I will prioritize this issue.
cc: @caesarxuchao

mengqiy · 2016-10-25T04:50:10Z

The root cause is bestMatch().
This function will return the first one in the slice when there is no best match.
In this case, this function's return value is not deterministic. It depends on the order of the input slice.
Ref: #34010Comment
@soltysh @smarterclayton Can you give a fix?

pwittrock · 2016-10-25T22:46:25Z

@caesarxuchao Is the codec library owned by the api-machinery sig?

caesarxuchao · 2016-10-26T00:29:47Z

Yes. This is an api-machinery issue.

soltysh · 2016-10-26T13:54:50Z

Lemme try to first reproduce this and I'll see what I can do.

soltysh · 2016-10-27T06:37:56Z

It looks like the same problem as in #35149, goes all the way down the exact same method. Working on it now...

pwittrock · 2016-10-27T20:20:12Z

Thx

pwittrock · 2016-12-16T00:50:03Z

@soltysh any updates on this?

matchstick · 2016-12-16T01:54:55Z

@pwittrock Giving this P1 priority and targeting to 1.5 for now. Should this be backported to 1.4?
Also I see #35688 has a possible fix. @soltysh Do you have an ETA? are you waiting on review?

pwittrock · 2016-12-16T21:54:36Z

cc @caesarxuchao @lavalamp

caesarxuchao · 2016-12-16T23:44:21Z

@smarterclayton @liggitt is this issue fixed by #38406?

pwittrock · 2016-12-19T19:00:45Z

It is possible this is already fixed on master/head. @ymqytw is trying to verify if this is the case now, and create a patch for 1.5 if this is the case.

@pwittrock

…d_obj Automatic merge from submit-queue make apply use the correct versioned obj Cherrypick [part of the changes](https://github.com/kubernetes/kubernetes/pull/38406/files#diff-b3aa1e4377838f45d595f8ecca3c2619) from #38406. Make `kubectl apply` in `v1.5` works for #34413. ``` release-note Give apply the versioned struct that generated from the type defined in the restmapping. ``` cc: @pwittrock @matchstick @liggitt

munnerz · 2017-01-04T18:39:55Z

If #38982 does in fact fix this issue, does anyone know if it'll make it into the 1.5.2 release? This issue is really frustrating in a CI/CD pipeline!

mengqiy · 2017-01-04T18:46:30Z

@munnerz I believe #38982 will be in 1.5.2.
@pwittrock Can you confirm?

pwittrock · 2017-01-04T18:56:45Z

Yes, this will be in 1.5.2

…

On Wed, Jan 4, 2017 at 10:47 AM, Mengqi Yu ***@***.***> wrote: @munnerz <https://github.com/munnerz> I believe #38982 <#38982> will be in 1.5.2. @pwittrock <https://github.com/pwittrock> Can you confirm? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#34413 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHhIAv2iKjM9i4CAsEoLKNrWDoOvjPxlks5rO-kqgaJpZM4KR_cS> .

yunzhu-li · 2017-01-25T18:38:22Z

I'm still hitting this on an 1.5.2 cluster, although much fewer times. Both master and node version are 1.5.2.

liggitt · 2017-01-25T18:40:06Z

do you have any pre-1.5.2 kubectl clients performing apply?

yunzhu-li · 2017-01-26T01:07:45Z

@liggitt Thanks for reminding! We were running pre-1.5.2 kubectl clients and now updated. Will continue monitoring.

Automatic merge from submit-queue (batch tested with PRs 39223, 40260, 40082, 40389) make kubectl generic commands work with unstructured objects part of making apply, edit, label, annotate, and patch work with third party resources fixes #35149 fixes #34413 prereq of: #35496 #40096 related to: #39906 #40119 kubectl is currently decoding any resource it doesn't have compiled-in to a ThirdPartyResourceData struct, which means it computes patches using that struct, and would try to send a ThirdPartyResourceData object to the API server when running `apply` This PR removes the behavior that decodes unknown objects into ThirdPartyResourceData structs internally, and fixes up the following generic commands to work with unstructured objects - [x] apply - [x] decode into runtime.Unstructured objects - [x] successfully use `--record` with unregistered objects - [x] patch - [x] decode into runtime.Unstructured objects - [x] successfully use `--record` with unregistered objects - [x] describe - [x] decode into runtime.Unstructured objects - [x] implement generic describer - [x] fix other generic kubectl commands to work with unstructured objects - [x] label - [x] annotate follow-ups for pre-existing issues: - [ ] `explain` doesn't work with unregistered resources - [ ] remove special casing of federation group in clientset lookups, etc - [ ] `patch` - [ ] doesn't honor output formats when persisting to server (`kubectl patch -f svc.json --type merge -p '{}' -o json` doesn't output json) - [ ] --local throws exception (`kubectl patch -f svc.json --type merge -p '{}' --local`) - [ ] `apply` - [ ] fall back to generic JSON patch computation if no go struct is registered for the target GVK (e.g. #40096) - [ ] ensure subkey deletion works in CreateThreeWayJSONMergePatch - [ ] ensure type stomping works in CreateThreeWayJSONMergePatch - [ ] lots of tests for generic json patch computation - [ ] prevent generic apply patch computation among different versions - [ ] reconcile treatment of nulls with #35496 - [ ] `edit` - [ ] decode into runtime.Unstructured objects - [ ] fall back to generic JSON patch computation if no go struct is registered for the target GVK

nckturner · 2017-05-26T08:10:51Z

I have this issue with a 1.5.2 cluster with a 1.5.4 client, anyone else seeing it?

adambkaplan · 2017-05-26T19:39:08Z

I'm seeing the same/similar issue with a 1.5.2 cluster and 1.6.3 client

kishorekumark · 2017-10-11T04:57:38Z

seeing the same issue with v1.8.0
macbook-pro-2:Federation kkokkiligadda$ kubectl --context=fed replace -f Adminconsole-Full.yaml --record --validate=false
service "adminconsole-app" replaced
deployment "adminconsole" replaced
error: unable to recognize "Adminconsole-Full.yaml": no matches for autoscaling/, Kind=HorizontalPodAutoscaler

How to overcome

kishorekumark · 2017-10-11T04:58:40Z

apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
name: adminconsole-app
namespace: default
spec:
scaleTargetRef:
apiVersion: apps/v1beta1
kind: Deployment
name: adminconsole-app
namespace: default
minReplicas: 1
maxReplicas: 10
cpuUtilization:
targetPercentage: 50

k8s-github-robot added area/kubectl team/ux labels Oct 9, 2016

bgrant0607 mentioned this issue Oct 13, 2016

kubectl apply umbrella issue #15894

Closed

pwittrock assigned mengqiy Oct 16, 2016

pwittrock added the kind/bug Categorizes issue or PR as related to a bug. label Oct 16, 2016

pwittrock added 0 - Triage labels Oct 18, 2016

pwittrock mentioned this issue Oct 20, 2016

kubectl apply umbrella issue tracker #35234

Open

32 tasks

pwittrock assigned caesarxuchao and soltysh and unassigned mengqiy and caesarxuchao Oct 25, 2016

soltysh mentioned this issue Oct 27, 2016

Force using versioned objects in apply's patch #35688

Closed

adam-sandor mentioned this issue Nov 17, 2016

Apply changes to HorizontalPodAutoscaler configuration fails #32768

Closed

bgrant0607 removed 0 - Triage labels Dec 8, 2016

pwittrock assigned mengqiy Dec 16, 2016

pwittrock added sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. labels Dec 16, 2016

matchstick added the priority/P1 label Dec 16, 2016

matchstick added this to the v1.5 milestone Dec 16, 2016

mengqiy mentioned this issue Dec 19, 2016

make apply use the correct versioned obj #38982

Merged

soltysh mentioned this issue Jan 24, 2017

make kubectl generic commands work with unstructured objects #40260

Merged

19 tasks

k8s-github-robot closed this as completed in #40260 Jan 27, 2017

tavogel mentioned this issue Jun 29, 2017

The oc cli fails to apply HorizontalPodAutoscalers from v3.6 -> v3.4 openshift/origin#14965

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Intermittent error when doing kubectl apply -f for a HorizontalPodAutoscaler: 'unable to find api field in struct HorizontalPodAutoscalerSpec for the json field "scaleTargetRef"' #34413

Intermittent error when doing kubectl apply -f for a HorizontalPodAutoscaler: 'unable to find api field in struct HorizontalPodAutoscalerSpec for the json field "scaleTargetRef"' #34413

bes commented Oct 9, 2016

bes commented Oct 9, 2016

pwittrock commented Oct 13, 2016

bes commented Oct 14, 2016

pwittrock commented Oct 16, 2016

mengqiy commented Oct 18, 2016

ajohnstone commented Oct 19, 2016

mengqiy commented Oct 19, 2016 •

edited

Loading

smarterclayton commented Oct 19, 2016

bgrant0607 commented Oct 21, 2016

devth commented Oct 24, 2016

mengqiy commented Oct 24, 2016

mengqiy commented Oct 25, 2016 •

edited

Loading

pwittrock commented Oct 25, 2016

caesarxuchao commented Oct 26, 2016

soltysh commented Oct 26, 2016

soltysh commented Oct 27, 2016

pwittrock commented Oct 27, 2016

pwittrock commented Dec 16, 2016

matchstick commented Dec 16, 2016

pwittrock commented Dec 16, 2016

caesarxuchao commented Dec 16, 2016 •

edited

Loading

pwittrock commented Dec 19, 2016

munnerz commented Jan 4, 2017

mengqiy commented Jan 4, 2017

pwittrock commented Jan 4, 2017 via email

yunzhu-li commented Jan 25, 2017

liggitt commented Jan 25, 2017

yunzhu-li commented Jan 26, 2017

nckturner commented May 26, 2017

adambkaplan commented May 26, 2017 •

edited

Loading

kishorekumark commented Oct 11, 2017

kishorekumark commented Oct 11, 2017

Intermittent error when doing kubectl apply -f for a HorizontalPodAutoscaler: 'unable to find api field in struct HorizontalPodAutoscalerSpec for the json field "scaleTargetRef"' #34413

Intermittent error when doing kubectl apply -f for a HorizontalPodAutoscaler: 'unable to find api field in struct HorizontalPodAutoscalerSpec for the json field "scaleTargetRef"' #34413

Comments

bes commented Oct 9, 2016

bes commented Oct 9, 2016

pwittrock commented Oct 13, 2016

bes commented Oct 14, 2016

pwittrock commented Oct 16, 2016

mengqiy commented Oct 18, 2016

ajohnstone commented Oct 19, 2016

mengqiy commented Oct 19, 2016 • edited Loading

smarterclayton commented Oct 19, 2016

bgrant0607 commented Oct 21, 2016

devth commented Oct 24, 2016

mengqiy commented Oct 24, 2016

mengqiy commented Oct 25, 2016 • edited Loading

pwittrock commented Oct 25, 2016

caesarxuchao commented Oct 26, 2016

soltysh commented Oct 26, 2016

soltysh commented Oct 27, 2016

pwittrock commented Oct 27, 2016

pwittrock commented Dec 16, 2016

matchstick commented Dec 16, 2016

pwittrock commented Dec 16, 2016

caesarxuchao commented Dec 16, 2016 • edited Loading

pwittrock commented Dec 19, 2016

munnerz commented Jan 4, 2017

mengqiy commented Jan 4, 2017

pwittrock commented Jan 4, 2017 via email

yunzhu-li commented Jan 25, 2017

liggitt commented Jan 25, 2017

yunzhu-li commented Jan 26, 2017

nckturner commented May 26, 2017

adambkaplan commented May 26, 2017 • edited Loading

kishorekumark commented Oct 11, 2017

kishorekumark commented Oct 11, 2017

apiVersion: autoscaling/v1 kind: HorizontalPodAutoscaler metadata: name: adminconsole-app namespace: default spec: scaleTargetRef: apiVersion: apps/v1beta1 kind: Deployment name: adminconsole-app namespace: default minReplicas: 1 maxReplicas: 10 cpuUtilization: targetPercentage: 50

mengqiy commented Oct 19, 2016 •

edited

Loading

mengqiy commented Oct 25, 2016 •

edited

Loading

caesarxuchao commented Dec 16, 2016 •

edited

Loading

adambkaplan commented May 26, 2017 •

edited

Loading

apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
name: adminconsole-app
namespace: default
spec:
scaleTargetRef:
apiVersion: apps/v1beta1
kind: Deployment
name: adminconsole-app
namespace: default
minReplicas: 1
maxReplicas: 10
cpuUtilization:
targetPercentage: 50