Update code reference links in docs

[bharath-123]

Update out of date code reference links in the how it works doc. These out of date links had me confused a bit while reading the docs.

[k8s-ci-robot]

Hi @bharath-123. 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.

[olemarkus]

/ok-to-test

[hakman]

I don't think it's sustainable to change these line numbers all the time. I thin wither using the current master tag or keeping master and removing line would be better (once you get to the right file, a quick search is not that hard).
What do you think?

[bharath-123]

Yeah that was in my mind while raising this PR. I think we should point to the right file and be more explicit in the docs about the struct name and method name so that the reader knows what to search for at least.

[olemarkus]

It may be better to replace e.g https://github.com/kubernetes/kops/blob/master/upup/pkg/fi/cloudup/apply_cluster.go#L89 with a link to https://pkg.go.dev/k8s.io/kops/upup/pkg/fi/cloudup#ApplyClusterCmd

These docs has up-to-date line references.

[bharath-123]

Thats a good idea @olemarkus! Thanks! Will fix up the links to point to the pkg.go.dev references!

[olemarkus]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bharath-123, olemarkus

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 [olemarkus]

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