Documentation: Would like to see example yaml snippet for GCP certificate resource for SSL/TLS

[jdyer09]

I'm assuming it would look like such, but it is somewhat unclear:

kind: Ingress
metadata:
  name: no-rules-map
  annotations:
    ingress.gcp.kubernetes.io/pre-shared-cert: "example.com-cert"
spec:
  backend:
    serviceName: s1
    servicePort: 443

[jdyer09]

Also, noting that crt and key input cannot have newlines in the encoding would be useful.
Suggestion:

kind: Secret
metadata:
  name: testsecret
  namespace: default
type: Opaque
data:
  tls.crt: base64 encoded cert # note that newlines are not allowed in the encoding.  Try $ cat example.com.crt | tr -d "\n" | base64
  tls.key: base64 encoded key # The same is true as the cert about not allowing newline characters

[TheWolfNL]

It's already visible in the README.md here:
https://github.com/kubernetes/ingress-gce/blob/master/README.md#frontend-https

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[rramkumar1]

/close

[k8s-ci-robot]

@rramkumar1: Closing this issue.

In response to this:

/close

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.