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
As discussed in the review of #2689, for Mesos it is not feasible to use environment variables to communicate the unique invoker names. For Mesos, we need to also support command-line flags style of specifying arguments. For example:
--name <some_name> --id <proposed_id>
For Kubernetes, we really would prefer environment variables.
So, the plan is to support both options. Add flags-style command line argument processing to the invoker and read the environment if explicit command lines are not provided.
The text was updated successfully, but these errors were encountered:
As discussed in the review of #2689, for Mesos it is not feasible to use environment variables to communicate the unique invoker names. For Mesos, we need to also support command-line flags style of specifying arguments. For example:
--name <some_name> --id <proposed_id>
For Kubernetes, we really would prefer environment variables.
So, the plan is to support both options. Add flags-style command line argument processing to the invoker and read the environment if explicit command lines are not provided.
The text was updated successfully, but these errors were encountered: