Deploying to GKE self managed has invalid YAML

[KatrinaHoffert]

This is for issue #755. Straightforward fix for the invalid syntax. I tested the script with this change.

Given that the invalid syntax should have prevented anyone from using the script, it is rather concerning. Implies no tests for this. But creating a meaningful test for it is quite non-trivial, so not doing that here.

[k8s-ci-robot]

Welcome @KatrinaHoffert!

It looks like this is your first PR to kubernetes/ingress-gce 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/ingress-gce has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @KatrinaHoffert. 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.

[KatrinaHoffert]

Gah, I have dirty commits on that branch, lemme clean it up.

[KatrinaHoffert]

Ready for review.

[MrHohn]

/ok-to-test

[MrHohn]

Thanks for the fix!
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: KatrinaHoffert, MrHohn

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

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

[rramkumar1]

@KatrinaHoffert Thanks for the fix. For posterity, looks like the typo was introduced in #746. You are right that we need some unit testing around those files that lints the yaml at the very least. Thanks for filing the issue for that!

[KatrinaHoffert]

I actually had already made a ticket for that. #760. It's a bit broader than just unit tests, but does mention similar, with points 2 and 3 of simplifying that.