Update Hugo to v0.145.0 and fix Resource.Err deprecation

[ntheanh201]

Description

This PR updates the website to use Hugo v0.145.0 (from v0.133.0) and fixes compatibility issues with the deprecated Resource.Err field.
See: https://gohugo.io/functions/go-template/try

Issue

When running with Hugo v0.141.0+, the build fails with the error:
"can't evaluate field Err in type resource.Resource: Resource.Err was removed in Hugo v0.141.0 and replaced with a new try keyword"

Closes: #49836

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign salaxander for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	958ed25
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/67d4bc8e20975900083fa7c3
😎 Deploy Preview	https://deploy-preview-50100--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	2277060
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/67d4bcf1683b180008ab175a
😎 Deploy Preview	https://deploy-preview-50100--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ntheanh201]

Hi @natalisucks, @divya-mohan0209 can you check my PR?

[SayakMukhopadhyay]

The latest release of Docsy (0.11.0) has official support upto 0.136.1 (see). Although the HEAD has been updated to a pretty recent version of Hugo, it should be noted that we are multiple versions of Docsy behind.

As such, I don't have a lot of confidence about whether a newer version of Hugo will remain compatible as we upgrade towards the latest Docsy.

[sftim]

/hold

given the valid-looking concern in #50100 (comment)

[sftim]

/area web-development

[ntheanh201]

The latest release of Docsy (0.11.0) has official support upto 0.136.1 (see). Although the HEAD has been updated to a pretty recent version of Hugo, it should be noted that we are multiple versions of Docsy behind.

As such, I don't have a lot of confidence about whether a newer version of Hugo will remain compatible as we upgrade towards the latest Docsy.

Hi @SayakMukhopadhyay, do you have any idea?

[SayakMukhopadhyay]

Hi @SayakMukhopadhyay, do you have any idea?

I'm sorry, idea of what exactly? Our suggestion would be to downgrade your Hugo version if you are using a local build or alternatively, use a container build, which comes with its own Hugo.

[ntheanh201]

Hi @SayakMukhopadhyay, do you have any idea?

I'm sorry, idea of what exactly? Our suggestion would be to downgrade your Hugo version if you are using a local build or alternatively, use a container build, which comes with its own Hugo.

Docsy's 0.11.1 (unreleased) has support Hugo 0.145.0 (https://github.com/google/docsy/blob/3b8482557b530533e627292638a18b42da783540/package.json#L44C5-L44C33), I think we can wait until it's released and then update this K8s website docsy to 0.11.1?

[SayakMukhopadhyay]

I think we can wait until it's released and then update this K8s website docsy to 0.11.1?

Updating the website to the latest Docsy is non trivial process since it has a lot of customisations. We are in the process of upgrading one minor version at a time. See #49430 for some background on our attempt to migrate to 0.7.0 which also has links to some other issues and PRs that might be helpful.

Anyway, if you would like to assist in this upgrade, help is welcome.

[ntheanh201]

I think we can wait until it's released and then update this K8s website docsy to 0.11.1?

Updating the website to the latest Docsy is non trivial process since it has a lot of customisations. We are in the process of upgrading one minor version at a time. See #49430 for some background on our attempt to migrate to 0.7.0 which also has links to some other issues and PRs that might be helpful.

Anyway, if you would like to assist in this upgrade, help is welcome.

Thank you for the context on the Docsy upgrade challenges. I understand that the customizations make this a complex process requiring an incremental approach. I've reviewed #49430 and would happily assist with the upgrade efforts.

[SayakMukhopadhyay]

I've reviewed #49430 and would happily assist with the upgrade efforts.

If you are in the kubernetes slack, give me a mention in the #sig-docs channel (same name as here) and we can discuss in detail there.

[ntheanh201]

I've reviewed #49430 and would happily assist with the upgrade efforts.

If you are in the kubernetes slack, give me a mention in the #sig-docs channel (same name as here) and we can discuss in detail there.

I did

[iamNoah1]

@SayakMukhopadhyay @ntheanh201 do we have any update on this after you discussed detail on slack?!

[SayakMukhopadhyay]

@SayakMukhopadhyay @ntheanh201 do we have any update on this after you discussed detail on slack?!

@iamNoah1 We will still need to work towards upgrading the Docsy version of the website first before we can get this PR merged.