images: upgrade to Alpine 3.18

[tao12345666333]

What this PR does / why we need it:

Alpine Linux 3.18 was released
https://alpinelinux.org/posts/Alpine-3.18.0-released.html

tao@moelove:~$ grype alpine:3.17
 ✔ Vulnerability DB        [no update available]
New version of grype is available: 0.62.2
 ✔ Loaded image            
 ✔ Parsed image            
 ✔ Cataloged packages      [15 packages]
 ✔ Scanned image           [2 vulnerabilities]
NAME        INSTALLED  FIXED-IN  TYPE  VULNERABILITY  SEVERITY 
libcrypto3  3.0.8-r3   3.0.8-r4  apk   CVE-2023-1255  Medium    
libssl3     3.0.8-r3   3.0.8-r4  apk   CVE-2023-1255  Medium    
tao@moelove:~$ grype alpine:3.18.0
 ✔ Vulnerability DB        [no update available]
New version of grype is available: 0.62.2
 ✔ Loaded image            
 ✔ Parsed image            
 ✔ Cataloged packages      [15 packages]
 ✔ Scanned image           [0 vulnerabilities]
No vulnerabilities found
tao@moelove:~$ grype alpine:3.17.2
 ✔ Vulnerability DB        [no update available]
New version of grype is available: 0.62.2
 ✔ Loaded image            
 ✔ Parsed image            
 ✔ Cataloged packages      [15 packages]
 ✔ Scanned image           [8 vulnerabilities]
NAME        INSTALLED  FIXED-IN  TYPE  VULNERABILITY  SEVERITY 
libcrypto3  3.0.8-r0   3.0.8-r4  apk   CVE-2023-1255  Medium    
libcrypto3  3.0.8-r0   3.0.8-r1  apk   CVE-2023-0464  High      
libcrypto3  3.0.8-r0   3.0.8-r2  apk   CVE-2023-0465  Medium    
libcrypto3  3.0.8-r0   3.0.8-r3  apk   CVE-2023-0466  Medium    
libssl3     3.0.8-r0   3.0.8-r3  apk   CVE-2023-0466  Medium    
libssl3     3.0.8-r0   3.0.8-r4  apk   CVE-2023-1255  Medium    
libssl3     3.0.8-r0   3.0.8-r1  apk   CVE-2023-0464  High      
libssl3     3.0.8-r0   3.0.8-r2  apk   CVE-2023-0465  Medium    

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

How Has This Been Tested?

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added unit and/or e2e tests to cover my changes.
• All new and existing tests passed.

[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.

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.

[strongjz]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: strongjz, tao12345666333

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [strongjz,tao12345666333]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[longwuyuan]

Awesome, images are getting built so need to promote and update project