You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--platform string Optionally specify a target platform, for example "linux/amd64" when using the s2i build strategy
67
67
-u, --push Attempt to push the function image to the configured registry after being successfully built
68
68
-r, --registry string Container registry + registry namespace. (ex 'ghcr.io/myuser'). The full image name is automatically determined using this along with function name. ($FUNC_REGISTRY)
69
+
--registry-insecure Disable HTTPS when communicating to the registry ($FUNC_REGISTRY_INSECURE)
-u, --push Push the function image to registry before deploying. ($FUNC_PUSH) (default true)
131
132
--pvc-size string When triggering a remote deployment, set a custom volume size to allocate for the build operation ($FUNC_PVC_SIZE)
132
133
-r, --registry string Container registry + registry namespace. (ex 'ghcr.io/myuser'). The full image name is automatically determined using this along with function name. ($FUNC_REGISTRY)
134
+
--registry-insecure Disable HTTPS when communicating to the registry ($FUNC_REGISTRY_INSECURE)
133
135
-R, --remote Trigger a remote deployment. Default is to deploy and build from the local system ($FUNC_REMOTE)
134
136
--service-account string Service account to be used in the deployed function ($FUNC_SERVICE_ACCOUNT)
0 commit comments