helm-chart v4.13.5 & v4.14.1 missing from oci://registry.k8s.io

[blahspam]

What happened:

$ helm show chart oci://registry.k8s.io/ingress-nginx/charts/ingress-nginx --version v4.14.1
Error: failed to perform "FetchReference" on source: registry.k8s.io/ingress-nginx/charts/ingress-nginx:v4.14.1: not found

$ helm show chart oci://registry.k8s.io/ingress-nginx/charts/ingress-nginx --version v4.13.5
Error: failed to perform "FetchReference" on source: registry.k8s.io/ingress-nginx/charts/ingress-nginx:v4.13.5: not found

Both v4.14.0 and v4.13.4 are available, however

$ helm show chart oci://registry.k8s.io/ingress-nginx/charts/ingress-nginx --version v4.14.0
Pulled: registry.k8s.io/ingress-nginx/charts/ingress-nginx:v4.14.0
Digest: sha256:95ea5f0784add47611abd33a96639e3cd9021fae61df773ff60c7edd5a20ec5b
annotations:
  artifacthub.io/changes: |
    - Update Ingress-Nginx version controller-v1.14.0
  artifacthub.io/prerelease: "false"
apiVersion: v2
appVersion: 1.14.0
description: Ingress controller for Kubernetes using NGINX as a reverse proxy and
  load balancer
home: https://github.com/kubernetes/ingress-nginx
icon: https://upload.wikimedia.org/wikipedia/commons/thumb/c/c5/Nginx_logo.svg/500px-Nginx_logo.svg.png
keywords:
- ingress
- nginx
kubeVersion: '>=1.21.0-0'
maintainers:
- name: cpanato
- name: Gacko
- name: strongjz
- name: tao12345666333
name: ingress-nginx
sources:
- https://github.com/kubernetes/ingress-nginx
version: 4.14.0

$ helm show chart oci://registry.k8s.io/ingress-nginx/charts/ingress-nginx --version v4.13.4
Pulled: registry.k8s.io/ingress-nginx/charts/ingress-nginx:v4.13.4
Digest: sha256:ae3da4be7f7d5fe1c52fe00d66ef4ddc492c63ebbb0a985f9ea3b77cdf5d22cb
annotations:
  artifacthub.io/changes: |
    - Update Ingress-Nginx version controller-v1.13.4
  artifacthub.io/prerelease: "false"
apiVersion: v2
appVersion: 1.13.4
description: Ingress controller for Kubernetes using NGINX as a reverse proxy and
  load balancer
home: https://github.com/kubernetes/ingress-nginx
icon: https://upload.wikimedia.org/wikipedia/commons/thumb/c/c5/Nginx_logo.svg/500px-Nginx_logo.svg.png
keywords:
- ingress
- nginx
kubeVersion: '>=1.21.0-0'
maintainers:
- name: cpanato
- name: Gacko
- name: strongjz
- name: tao12345666333
name: ingress-nginx
sources:
- https://github.com/kubernetes/ingress-nginx
version: 4.13.4

What you expected to happen:

Latest helm charts to be available in OCI repo.

NGINX Ingress controller version (exec into the pod and run /nginx-ingress-controller --version):

Kubernetes version (use kubectl version):

Environment:

• Cloud provider or hardware configuration:

• OS (e.g. from /etc/os-release):

• Kernel (e.g. uname -a):

• Install tools:

  • Please mention how/where was the cluster created like kubeadm/kops/minikube/kind etc.

• Basic cluster related info:

  • kubectl version
  • kubectl get nodes -o wide

• How was the ingress-nginx-controller installed:

  • If helm was used then please show output of helm ls -A | grep -i ingress
  • If helm was used then please show output of helm -n <ingresscontrollernamespace> get values <helmreleasename>
  • If helm was not used, then copy/paste the complete precise command used to install the controller, along with the flags and options used
  • if you have more than one instance of the ingress-nginx-controller installed in the same cluster, please provide details for all the instances

• Current State of the controller:

  • kubectl describe ingressclasses
  • kubectl -n <ingresscontrollernamespace> get all -A -o wide
  • kubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>
  • kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>

• Current state of ingress object, if applicable:

  • kubectl -n <appnamespace> get all,ing -o wide
  • kubectl -n <appnamespace> describe ing <ingressname>
  • If applicable, then, your complete and exact curl/grpcurl command (redacted if required) and the reponse to the curl/grpcurl command with the -v flag

• Others:

  • Any other related information like ;
    • copy/paste of the snippet (if applicable)
    • kubectl describe ... of any custom configmap(s) created and in use
    • Any other related information that may help

How to reproduce this issue:

Anything else we need to know:

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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-sigs/prow repository.

[Gacko]

Uh, ah, yes, you are right about that. Might have forgotten to promote them, gonna do so in a second. I just hope the digest is still around.

[Gacko]

kubernetes/k8s.io#8909

You sadly cannot LGTM this, but I cc'ed the other maintainers. Gonna close this for now as the PR getting merged is all that's missing.