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
{{ message }}
This repository has been archived by the owner on Aug 9, 2024. It is now read-only.
Right now, we have a kubebench-specific config format that lets user specify the template reference (i.e. ksonnet pkg) and corresponding parameters to use in an experiment. The configurator will automatically generate the job manifests with kubebench-specific mixins. While this is useful, some user might not want to manage their configs in this particular way. We should provide the possibility for users to manage their configs in custom way, which means we can accept raw kubernetes manifest files that specify the kubeflow jobs or post jobs etc. to be run. In this case, the configurator will skip the ksonnet -> manifest generation part, and directly perform the mixins with the raw manifests provided by user.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now, we have a kubebench-specific config format that lets user specify the template reference (i.e. ksonnet pkg) and corresponding parameters to use in an experiment. The configurator will automatically generate the job manifests with kubebench-specific mixins. While this is useful, some user might not want to manage their configs in this particular way. We should provide the possibility for users to manage their configs in custom way, which means we can accept raw kubernetes manifest files that specify the kubeflow jobs or post jobs etc. to be run. In this case, the configurator will skip the ksonnet -> manifest generation part, and directly perform the mixins with the raw manifests provided by user.
The text was updated successfully, but these errors were encountered: