Promote custom-errors to newer version

[rikatz]

custom errors image needs to be promoted.

Steps:

• Open a PR for https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-ingress-nginx/images.yaml#L129, add a new line below this one with the following:

 "sha256:1d69f28d6412b0f2a6302f9df9a6bc49e83703336a35f95ab109cad10e039120": ["1.0.0"]

• Once this PR gets merged, open a new PR in ingress-nginx repo to update pointing to newer version -

  ingress-nginx/docs/examples/customization/custom-errors/custom-default-backend.yaml

  Line 39 in ff2b743

  image: k8s.gcr.io/ingress-nginx/nginx-errors:0.48.1

image: k8s.gcr.io/ingress-nginx/nginx-errors:1.0.0

This is a followup of #7728

/good-first-issue
/help
/kind feature

[k8s-ci-robot]

@rikatz:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

custom errors image needs to be promoted.

Steps:

• Open a PR for https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-ingress-nginx/images.yaml#L129, add a new line below this one with the following:

"sha256:1d69f28d6412b0f2a6302f9df9a6bc49e83703336a35f95ab109cad10e039120": ["1.0.0"]

• Once this PR gets merged, open a new PR in ingress-nginx repo to update pointing to newer version -

  ingress-nginx/docs/examples/customization/custom-errors/custom-default-backend.yaml

  Line 39 in ff2b743

  image: k8s.gcr.io/ingress-nginx/nginx-errors:0.48.1

image: k8s.gcr.io/ingress-nginx/nginx-errors:1.0.0

This is a followup of #7728

/good-first-issue
/help
/kind feature

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.

[rikatz]

/priority backlog
/triage accepted

[justaugustus]

Check out kpromo pr: https://sigs.k8s.io/promo-tools/docs/promotion-pull-requests.md

[rikatz]

Oooh thanks @justaugustus this is a cool tool! Didn't knew about that!

Will dig a bit into it because as for this issue the promotion is for a secondary image, for the main ingress images that we cut tags and do stuff using the tool can help us avoid errors!!

@strongjz automation ftw!!

[justaugustus]

for the main ingress images that we cut tags and do stuff using the tool can help us avoid errors!!

Here's an example of usage in capz from @CecileRobertMichon: kubernetes-sigs/cluster-api-provider-azure#1877

[anand-abgis]

/assign

[anand-abgis]

@rikatz raised a PR for the first step. kubernetes/k8s.io#3222
will open a new PR here once this one is merged.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[strongjz]

/remove-lifecycle stale

we need to add this to the release updates issue tracker that I have yet to make.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[DanielViniciusAlves]

Hey @strongjz, this issue still need to be worked?

[Dhairya-Arora01]

@rikatz @strongjz , do this still need to be worked ? If yes, i am happy to work on this

[rikatz]

nope, thanks! and sorry for the long delay!
/close

[k8s-ci-robot]

@rikatz: Closing this issue.

In response to this:

nope, thanks! and sorry for the long delay!
/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.