Clearly state what types you can expose using Skupper

[pwright]

Rather than relying on https://skupper.io/docs/cli-reference/skupper_expose.html to show users what objects you can expose on the service network, it would be better to express the limits up front to users.

[pwright]

Also, "exposing services" can be ambiguous, normally it refers to services created on the van, but sometimes refers to the object you're exposing, maybe best handled by something like:

When you expose services on the service network, Skupper provides a default name for that service as follows:

Kubernetes object	Default service name	Notes
deployment	Deployment name	Use --address <name> for custom service names
service	None	Specify the resulting service name using --address <name>
statefulset	StatefulSet name	Use --address <name> for custom service names
deploymentconfig	DeploymentConfig name	Supported for OpenShift 3 only
pods	None	Not currently supported.
daemonset	DaemonSet name	Only supported with YAML

wdyt @ssorj