Update NodePort and Helm Chart configuration in get-started.md

[pedroignacio13]

Added the nodePort 30478 and the containerPort 8443. This is needed because the tutorial fails on the part of HTTPS Termination since the Kind Cluster does not have the needed ports exposed.

Proposed changes

Checklist

Before sharing this pull request, I completed the following checklist:

• I read the Contributing guidelines
• My branch adheres to the Git conventions
• My content changes adhere to the F5 NGINX Documentation style guide
• If my changes involve potentially sensitive information¹, I have assessed the possible impact
• I have waited to ensure my changes pass tests, and addressed any discovered issues

Footnotes

1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

[github-actions]

✅ All required contributors have signed the F5 CLA for this PR. Thank you!
_{Posted by the CLA Assistant Lite bot.}

[pedroignacio13]

I have hereby read the F5 CLA and agree to its terms

[bjee19]

Suggested change

	- containerPort:30478
	- containerPort: 30478

[sjberman]

There is no HTTPS as part of this tutorial guide. @pedroignacio13 Are you using this guide as the setup for the other guides we have?

@ADubhlaoich not sure we considered that scenario, since our other traffic guides don't use the "Get Started" guide as a prerequisite. How should we approach that?

[pedroignacio13]

@sjberman in this file (get-started.md) it really does not have any HTTPS reference, but if you go to the HTTPS Termination page of the tutorial (https://docs.nginx.com/nginx-gateway-fabric/traffic-management/https-termination/) that's when it starts having some trouble.
As I moved forward with my study, I noticed the Kind cluster is set up only in this file, since it's the beginning of the whole tutorial. That's why I suggested the Kind cluster to already be created with the correct port mapping to support HTTPS.

[ADubhlaoich]

@ADubhlaoich not sure we considered that scenario, since our other traffic guides don't use the "Get Started" guide as a prerequisite. How should we approach that?

I guess if the get started guide is being used an example, it's good to show how to enable HTTPS, but the actual design intent for the document is just to show a test cluster deployment quickly, on the basis that someone would follow a dedicated "full" deployment guide for a production environment.

If it doesn't "break" this guide I see no harm in adding the scope of the PR's changes.

@pedroignacio13 Are you following through documentation starting from Get started for a production environment, or just testing?

There's a big notice box at the very top of "Get started" directing users to other deployment guides: I' m trying to understand if that was effective or not.