Rebuild echo server

[SaumyaBhushan]

What this PR does / why we need it:

• Alpine and golang needed to be bumped for CVE and performance to go-1.20 and alpine-3.17.2
• images of the project were rebuilt and promoted from staging to prod in https://github.com/kubernetes/k8s.io/pull/4929/files
• echo server image was not rebuilt because rebuilt was not triggered because no file was edited under /images/echo
• So this PR makes a dummy cosmetic edit (adding a space) to makefile of the echo server.
• This is expected to fire a build for echo server with new go-1.20 and alpine-3.17.2 .

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.
• Added Release Notes.

Does my pull request need a release note?

Any user-visible or operator-visible change qualifies for a release note. This could be a:

• CLI change
• API change
• UI change
• configuration schema change
• behavioral change
• change in non-functional attributes such as efficiency or availability, availability of a new platform
• a warning about a deprecation
• fix of a previous Known Issue
• fix of a vulnerability (CVE)

No release notes are required for changes to the following:

• Tests
• Build infrastructure
• Fixes for unreleased bugs

For more tips on writing good release notes, check out the Release Notes Handbook

Build echo server with go1.20 and alpine 3.17.2

[k8s-ci-robot]

Hi @SaumyaBhushan. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[longwuyuan]

Thanks.
/ok-to-test
/triage accepted
/area stabilization
/remove-area helm

[longwuyuan]

/lgtm

[strongjz]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: longwuyuan, SaumyaBhushan, strongjz

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:

• images/OWNERS [strongjz]

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

[longwuyuan]

@SaumyaBhushan echo-server new build details below. Follow up PRs needed to promote this image from staging to prod and then to change project code to use this new tag+sha
Image type
Docker Manifest, Schema 2
Media type
application/vnd.docker.distribution.manifest.v2+json
Project
k8s-staging-ingress-nginx
Repository
e2e-test-echo
Digest
sha256:4938d1d91a2b7d19454460a8c1b010b89f6ff92d2987fd889ac3e8fc3b70d91a
Virtual size
93.9 MB
Created
Mar 19, 2023, 3:45:11 AM
Uploaded
Mar 19, 2023, 3:45:17 AM
Tags
v20230318-helm-chart-4.5.2-44-gfec1dbe3a

[SaumyaBhushan]

@SaumyaBhushan echo-server new build details below. Follow up PRs needed to promote this image from staging to prod and then to change project code to use this new tag+sha Image type Docker Manifest, Schema 2 Media type application/vnd.docker.distribution.manifest.v2+json Project k8s-staging-ingress-nginx Repository e2e-test-echo Digest sha256:4938d1d91a2b7d19454460a8c1b010b89f6ff92d2987fd889ac3e8fc3b70d91a Virtual size 93.9 MB Created Mar 19, 2023, 3:45:11 AM Uploaded Mar 19, 2023, 3:45:17 AM Tags v20230318-helm-chart-4.5.2-44-gfec1dbe3a

Sure @longwuyuan .