## kn source ping create Create a ping source ``` kn source ping create NAME --sink SINK ``` ### Examples ``` # Create a Ping source 'my-ping' which fires every two minutes and sends '{ value: "hello" }' to service 'mysvc' as a cloudevent kn source ping create my-ping --schedule "*/2 * * * *" --data '{ value: "hello" }' --sink ksvc:mysvc ``` ### Options ``` --ce-override stringArray Cloud Event overrides to apply before sending event to sink. Example: '--ce-override key=value' You may be provide this flag multiple times. To unset, append "-" to the key (e.g. --ce-override key-). -d, --data string Data to send in JSON format. This flag can implicitly determine the encoding of the supplied data (text | base64). -e, --encoding string Data encoding format. One of: text | base64 -h, --help help for create -n, --namespace string Specify the namespace to operate in. --schedule string Optional schedule specification in crontab format (e.g. '*/2 * * * *' for every two minutes. By default fire every minute. -s, --sink string Addressable sink for events. You can specify a broker, channel, Knative service, Kubernetes service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an HTTP URI, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace, '--sink svc:receiver:mynamespace' for a Kubernetes service 'receiver' in the 'mynamespace' namespace, '--sink special.eventing.dev/v1alpha1/channels:pipe' for GroupVersionResource of v1alpha1 'pipe'. If a prefix is not provided, it is considered as a Knative service in the current namespace. ``` ### Options inherited from parent commands ``` --as string username to impersonate for the operation --as-group stringArray group to impersonate for the operation, this flag can be repeated to specify multiple groups --as-uid string uid to impersonate for the operation --cluster string name of the kubeconfig cluster to use --config string kn configuration file (default: ~/.config/kn/config.yaml) --context string name of the kubeconfig context to use --kubeconfig string kubectl configuration file (default: ~/.kube/config) --log-http log http traffic ``` ### SEE ALSO * [kn source ping](kn_source_ping.md) - Manage ping sources