fix: Update ingress.yaml

[sourirv]

Updates to ingress.yaml that allow the pod selector to match the scheduler pod in KubeCF.
This is to address #1509 , where ccf ssh to apps does not work in cases where the ssh-proxy-public service uses a LoadBalancer instead of an nginx ingress-controller.

Description

The scheduler pod has a label called app.kubernetes.io/component=scheduler
Whereas the service resource described in ingress.yaml, specifies a pod selector with a value app.kubernetes.io/component=ssh-proxy
The pull request modifies the label and the pod selector to app.kubernetes.io/component=scheduler, such that the service can match the ssh-proxy container in the pod

Motivation and Context

This change allows the ssh-proxy-public service to select the appropriate kubecf pod, and enables the cf ssh capability to work when the services are deployed as LoadBalanced as opposed to being exposed via an ingress-controller.
Fixes #1509

How Has This Been Tested?

Deployed the charts from the pull request on AWS EKS as a backbone. (Diego deployment)
Deployed a simple cloud foundry app (python buildpack) to the deployment.
Verified that the cf ssh feature works by being able to ssh into the app container.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code has security implications.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ sourirv (90a6cd7)

[sourirv]

@mook-as @jandubois This is the same as #1510 .

[mook-as]

I'm still fine with the change :)

Ah, the things we do to work around machines…