IssueTracker

This will create a public issue which anybody can view and comment on.

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered:

Cx is using extended resources: kubernetes.io/batch-memory in their pod yaml using the steps here [1][2] However when they try to deploy pod which requesting for more than 'batch-memory' advertised to the node, the cluster autoscaler is not triggering a scale-up eventhough the pods are pending and CA is enabled. I replicated the use-case on my test lab and I was able to see the CA is not triggering the scale up in this case.

What you expected to happen:

Extended resources are supported in GKE cluster autoscaling and can be used just like CPU and Memory for triggering scaling up.

Steps to reproduce:

[1] run command

kubectl proxy

[2]run command to advertise extended resources to all existing nodes (reference https://kubernetes.io/docs/tasks/administer-cluster/extended-resource-node/)

curl --header "Content-Type: application/json-patch+json" \
--request PATCH \
--data '[{"op": "add", "path": "/status/capacity/batch~1memory", "value": "1"}]' \
http://localhost:8001/api/v1/nodes/<your-node-name>/status

[3] deploy the test pod of yaml file below

kind: Pod
apiVersion: v1
metadata:
 name: ubuntu-test-extended-resources
spec:
 containers:
  - name: ubuntu
   image: ubuntu:18.04
   resources:
    requests:
     batch/memory: 1
    limits:
     batch/memory: 1
   command: ["/bin/bash", "-ec", "while :; do echo '.'; sleep 5 ; done"]
 restartPolicy: Never

Other information (workarounds you have tried, documentation consulted, etc):

[1] https://kubernetes.io/docs/tasks/administer-cluster/extended-resource-node/

[2] https://kubernetes.io/docs/tasks/configure-pod-container/extended-resource/