downwardAPI volumes should also have hugepages-<size> exposed to the pod through resourceFieldRef.

[DeySouvik]

What would you like to be added:
Currently the resourceFieldRef only exposes the cpu/memory and ephemeral-storage limit and requests to the POD. The hugepages information is not retrieve through the same mechanism.
POD manifest :
apiVersion: v1
kind: Pod
metadata:
name: isbc
namespace: development
labels:
name: isbc
annotations:
k8s.v1.cni.cncf.io/networks: pkt0-conf, pkt0-conf, pkt1-conf
spec:
nodeName: "node2"
hostname: "vsbc1"
containers:

• name: isbc
  image: artifact1.eng.sonusnet.com:8443/sbx-docker-prod-westford/isbc/sbc-image:latest
  imagePullPolicy: IfNotPresent
  command: ["/bin/bash","-c", "sleep 2000000000000"]
  securityContext:
  capabilities:
  add:
  - NET_ADMIN
  allowPrivilegeEscalation: false
  volumeMounts:
  • mountPath: /hugepages
    name: hugepage
    resources:
    limits:
    hugepages-2Mi: "2048Mi"
    memory: "16Gi"
    cpu: "8"
    ephemeral-storage: "100Gi"
    volumeMounts:
    • name: podinfo
      mountPath: /etc/podinfo
      readOnly: false
      volumes:
  • name: hugepage
    emptyDir:
    medium: HugePages
  • name: podinfo
    downwardAPI:
    items:
    - path: "cpu"
    resourceFieldRef:
    containerName: isbc
    resource: limits.cpu
    - path: "memory"
    resourceFieldRef:
    containerName: isbc
    resource: limits.memory
    divisor: 1Mi
    - path: "storage"
    resourceFieldRef:
    containerName: isbc
    resource: limits.ephemeral-storage
    divisor: 1Mi
    - path: "hugepages"
    resourceFieldRef:
    containerName: isbc
    resource: limits.hugepages-2Mi
    divisor: 1Mi
    - path: "uid"
    fieldRef:
    fieldPath: metadata.uid

The above manifest fails the validation as the value limits.hugepages- is not supported.
[root@node1 ~]# kubectl create -f abc_pod.yml
The Pod "isbc" is invalid:

• spec.volumes[1].downwardAPI.resourceFieldRef.resource: Unsupported value: "limits.hugepages-2Mi": supported values: "limits.cpu", "limits.ephemeral-storage", "limits.memory", "requests.cpu", "requests.ephemeral-storage", "requests.memory"
• spec.containers[0].volumeMounts[0].name: Not found: "podinfo"
  [root@node1 ~]#

Why is this needed:
As we are running dpdk and other real time apps it is required to know the number of hugepages allocated for the pod. We need to have both the limit and request for the hugepages- reported back to the pod as a part of the resourceFieldRef in the downwardAPI. This will help in allocating the proper number of hugepages to the apps in the POD.

[DeySouvik]

@kubernetes/sig-node-feature-requests
@kubernetes/sig-service-catalog-feature-requests
@kubernetes/sig-scheduling-feature-requests
@kubernetes/sig-instrumentation-feature-requests
@kubernetes/sig-network-feature-requests
@kubernetes/sig-architecture-feature-requests
/wg resource-management

[k8s-ci-robot]

@DeySouvik: Reiterating the mentions to trigger a notification:
@kubernetes/sig-node-feature-requests, @kubernetes/sig-service-catalog-feature-requests, @kubernetes/sig-scheduling-feature-requests, @kubernetes/sig-instrumentation-feature-requests, @kubernetes/sig-network-feature-requests, @kubernetes/sig-architecture-feature-requests

In response to this:

@kubernetes/sig-node-feature-requests
@kubernetes/sig-service-catalog-feature-requests
@kubernetes/sig-scheduling-feature-requests
@kubernetes/sig-instrumentation-feature-requests
@kubernetes/sig-network-feature-requests
@kubernetes/sig-architecture-feature-requests
/wg resource-management

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[athenabot]

/triage unresolved

Comment /remove-triage unresolved when the issue is assessed and confirmed.

🤖 I am a bot run by vllry. 👩‍🔬

[robscott]

It looks like this ended up with a few too many sigs assigned, removing the ones that are not related, though I think this may only actually be relevant to sig-node.

/remove-sig network service-catalog instrumentation architecture

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[odinuge]

/reopen

[odinuge]

/remove-lifecycle rotten

[k8s-ci-robot]

@odinuge: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.