Set 'enable_private_endpoint' to false

[pawloch00]

Submission Checklist

NOTE: Community submissions can take up to 2 weeks to be reviewed.
Set enable_private_endpoint to false, so cluster do not fail during creation.
Right now, buidling gke a3 mega blueprint fails with error:
Error: Error waiting for creating GKE cluster: Invalid master authorized networks: network "x.y.z.w/l" is not a reserved network, which is required for private endpoints.

With enable_private_endpoint set to false user can access cluster either with private or public endpoint.
It looks like this was introduced here c901563
Please take the following actions before submitting this pull request.

• Fork your PR branch from the Toolkit "develop" branch (not main)
• Test all changes with pre-commit in a local branch #
• Confirm that "make tests" passes all tests
• Add or modify unit tests to cover code changes
• Ensure that unit test coverage remains above 80%
• Update all applicable documentation
• Follow Cluster Toolkit Contribution guidelines #

[ankitkinra]

Can you please add to the description of the CLs two things:

• Why is enable_private_endpoint is important ?
• That currently this blueprint is broken