Add service and ingress resources

[cmoulliard]

• Issue: Backstage component is not deployed as service and no ingress route is available #22
• Adding the definition about the Service and Ingress kubernetes resource to expose backstage using the host: https://backstage.idpbuilder.cnoe.io.local:8443

Remarks:

• The UI reports as error Fail to load entity kinds when we navigate to https://backstage.idpbuilder.cnoe.io.local:8443/catalog. This problem is most probably due to cors badly defined as described here: 🐛 Bug Report: Failed to load entity kinds backstage/backstage#15403
• If later, we also deploy cert manager, then we could add an annotation to the ingress resource to get the TLS secret populated by the cert manager

[nabuskey]

These needs to be either local.me or local.cnoe.io, depending on which one we use in #29

[cmoulliard]

I suggest to change all the URLs (including what we have here + documentation when a PR will be created to fix issue 29

[greghaynes]

Yep - we're going to hopefully merge #29 asap which does this, we should change it here assuming we merge that one first.

[cmoulliard]

I updated the DNS name to use cnoe.io.localtest.me @greghaynes

[cmoulliard]

As you merged my commits in another PR, I will then close this PR @jessesanford Next time, we should keep my PR and not creating another one ;-)

[jessesanford]

As you merged my commits in another PR, I will then close this PR @jessesanford Next time, we should keep my PR and not creating another one ;-)

Hey sorry for merging your work without you online. I was creating the same code changes to fix backstage. Unfortunately I could not rebase your fork. Sorry for pulling the branch here in order to do so, all of your commits and the credit was attributed to you. In fact the full PR was taken in its complete state in order to retain your intent. If the PR was not ready for merge just mark it as WIP or draft or "don't merge". However I tested it and it was nearly exactly the code that I had prepared to commit.