instruction: Create a Kubernetes configuration with Ingress, Secret resources
output: ```dockerfile
  From Message
   ---- ------ ---- ---- -------
   Normal ADD 22s loadbalancer-controller default/test
  The Ingress controller provisions an implementation-specific load balancer
  that satisfies the Ingress, as long as the Services (service1, service2) exist.
  When it has done so, you can see the address of the load balancer at the
  Address field.
  
  Note: Depending on the Ingress controller
  you are using, you may need to create a default-http-backend
  Service.
  
  Name based virtual hosting
  Name-based virtual hosts support routing HTTP traffic to multiple host names at the same IP address.
  
  Figure. Ingress Name Based Virtual hosting
  
  The following Ingress tells the backing load balancer to route requests based on
  the Host header.
  
  service/networking/name-virtual-host-ingress.yaml
  
  apiVersion: networking.k8s.io/v1
  kind: Ingress
  metadata:
   name: name-virtual-host-ingress
  spec:
   rules:
   - host: foo.bar.com
   http:
   paths:
   - pathType: Prefix
   path: "/"
   backend:
   service:
   name: service1
   port:
   number: 80
   - host: bar.foo.com
   http:
   paths:
   - pathType: Prefix
   path: "/"
   backend:
   service:
   name: service2
   port:
   number: 80
  
  If you create an Ingress resource without any hosts defined in the rules, then any
  web traffic to the IP address of your Ingress controller can be matched without a name based
  virtual host being required.
  For example, the following Ingress routes traffic
  requested for first.bar.com to service1, second.bar.com to service2,
  and any traffic whose request host header doesn't match first.bar.com
  and second.bar.com to service3.
  
  service/networking/name-virtual-host-ingress-no-third-host.yaml
  
  apiVersion: networking.k8s.io/v1
  kind: Ingress
  metadata:
   name: name-virtual-host-ingress-no-third-host
  spec:
   rules:
   - host: first.bar.com
   http:
   paths:
   - pathType: Prefix
   path: "/"
   backend:
   service:
   name: service1
   port:
   number: 80
   - host: second.bar.com
   http:
   paths:
   - pathType: Prefix
   path: "/"
   backend:
   service:
   name: service2
   port:
   number: 80
   - http:
   paths:
   - pathType: Prefix
   path: "/"
   backend:
   service:
   name: service3
   port:
   number: 80
  
  TLS
  You can secure an Ingress by specifying a Secret
  that contains a TLS private key and certificate. The Ingress resource only
  supports a single TLS port, 443, and assumes TLS termination at the ingress point
  (traffic to the Service and its Pods is in plaintext).
  If the TLS configuration section in an Ingress specifies different hosts, they are
  multiplexed on the same port according to the hostname specified through the
  SNI TLS extension (provided the Ingress controller supports SNI). The TLS secret
  must contain keys named tls.crt and tls.key that contain the certificate
  and private key to use for TLS. For example:
  apiVersion: v1
  kind: Secret
  metadata:
   name: testsecret-tls
   namespace: default
  data:
   tls.crt: base64 encoded cert
   tls.key: base64 encoded key
  type: kubernetes.io/tls
  Referencing this secret in an Ingress tells the Ingress controller to
  secure the channel
  ```