Expose Knative domain in a build environment variable
Description
Whenever we interact with Kubernetes, KUBECONFIG and KUBE_PEM variables are available for us. This is a great experience because this way one can use kubectl from within a build, or integrate their tools and communicate with a cluster.
When we deploy to Knative however, neither Knative domain, or Knative ingress IP are not available as environment variables. KUBE_INGRESS_BASE_DOMAIN is empty in that case too.
We could read everything that is necessary from the cluster itself, but having this exposed automatically when operating on a Knative cluster would make sense too.
Proposal
Introduce KNATIVE_BASE_DOMAIN and KNATIVE_INGRESS_IP / KNATIVE_ENDPOINT_IP variables to make it easier to interact with a Knative cluster from the CI environment.