castai.GetRebalancingScheduleDataSource
Using GetRebalancingScheduleDataSource
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getRebalancingScheduleDataSource(args: GetRebalancingScheduleDataSourceArgs, opts?: InvokeOptions): Promise<GetRebalancingScheduleDataSourceResult>
function getRebalancingScheduleDataSourceOutput(args: GetRebalancingScheduleDataSourceOutputArgs, opts?: InvokeOptions): Output<GetRebalancingScheduleDataSourceResult>def get_rebalancing_schedule_data_source(name: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetRebalancingScheduleDataSourceResult
def get_rebalancing_schedule_data_source_output(name: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetRebalancingScheduleDataSourceResult]func GetRebalancingScheduleDataSource(ctx *Context, args *GetRebalancingScheduleDataSourceArgs, opts ...InvokeOption) (*GetRebalancingScheduleDataSourceResult, error)
func GetRebalancingScheduleDataSourceOutput(ctx *Context, args *GetRebalancingScheduleDataSourceOutputArgs, opts ...InvokeOption) GetRebalancingScheduleDataSourceResultOutputpublic static class GetRebalancingScheduleDataSource
{
public static Task<GetRebalancingScheduleDataSourceResult> InvokeAsync(GetRebalancingScheduleDataSourceArgs args, InvokeOptions? opts = null)
public static Output<GetRebalancingScheduleDataSourceResult> Invoke(GetRebalancingScheduleDataSourceInvokeArgs args, InvokeOptions? opts = null)
}public static CompletableFuture<GetRebalancingScheduleDataSourceResult> getRebalancingScheduleDataSource(GetRebalancingScheduleDataSourceArgs args, InvokeOptions options)
public static Output<GetRebalancingScheduleDataSourceResult> getRebalancingScheduleDataSource(GetRebalancingScheduleDataSourceArgs args, InvokeOptions options)
fn::invoke:
function: castai:rebalancing:GetRebalancingScheduleDataSource
arguments:
# arguments dictionaryThe following arguments are supported:
- Name string
- Name string
- name String
- name string
- name str
- name String
GetRebalancingScheduleDataSource Result
The following output properties are available:
- Id string
- The provider-assigned unique ID for this managed resource.
- Launch
Configurations List<Pulumi.Cast AI. Rebalancing. Outputs. Get Rebalancing Schedule Data Source Launch Configuration> - Name string
- Schedules
List<Pulumi.
Cast AI. Rebalancing. Outputs. Get Rebalancing Schedule Data Source Schedule> - Trigger
Conditions List<Pulumi.Cast AI. Rebalancing. Outputs. Get Rebalancing Schedule Data Source Trigger Condition>
- Id string
- The provider-assigned unique ID for this managed resource.
- Launch
Configurations GetRebalancing Schedule Data Source Launch Configuration - Name string
- Schedules
Get
Rebalancing Schedule Data Source Schedule - Trigger
Conditions GetRebalancing Schedule Data Source Trigger Condition
- id String
- The provider-assigned unique ID for this managed resource.
- launch
Configurations List<GetRebalancing Schedule Data Source Launch Configuration> - name String
- schedules
List<Get
Rebalancing Schedule Data Source Schedule> - trigger
Conditions List<GetRebalancing Schedule Data Source Trigger Condition>
- id string
- The provider-assigned unique ID for this managed resource.
- launch
Configurations rebalancingGet Rebalancing Schedule Data Source Launch Configuration[] - name string
- schedules
rebalancing
Get Rebalancing Schedule Data Source Schedule[] - trigger
Conditions rebalancingGet Rebalancing Schedule Data Source Trigger Condition[]
- id str
- The provider-assigned unique ID for this managed resource.
- launch_
configurations Sequence[rebalancing.Get Rebalancing Schedule Data Source Launch Configuration] - name str
- schedules
Sequence[rebalancing.
Get Rebalancing Schedule Data Source Schedule] - trigger_
conditions Sequence[rebalancing.Get Rebalancing Schedule Data Source Trigger Condition]
- id String
- The provider-assigned unique ID for this managed resource.
- launch
Configurations List<Property Map> - name String
- schedules List<Property Map>
- trigger
Conditions List<Property Map>
Supporting Types
GetRebalancingScheduleDataSourceLaunchConfiguration
- Aggressive
Mode bool - When enabled rebalancing will also consider problematic pods (pods without controller, job pods, pods with removal-disabled annotation) as not-problematic.
- Aggressive
Mode Pulumi.Config Cast AI. Rebalancing. Inputs. Get Rebalancing Schedule Data Source Launch Configuration Aggressive Mode Config - Advanced configuration for aggressive rebalancing mode.
- Execution
Conditions Pulumi.Cast AI. Rebalancing. Inputs. Get Rebalancing Schedule Data Source Launch Configuration Execution Conditions - Keep
Drain boolTimeout Nodes - Defines whether the nodes that failed to get drained until a predefined timeout, will be kept with a rebalancing.cast.ai/status=drain-failed annotation instead of forcefully drained.
- Node
Ttl intSeconds - Specifies amount of time since node creation before the node is allowed to be considered for automated rebalancing.
- Num
Targeted intNodes - Maximum number of nodes that will be selected for rebalancing.
- Rebalancing
Min intNodes - Minimum number of nodes that should be kept in the cluster after rebalancing.
- Selector string
- Node selector in JSON format.
- Target
Node stringSelection Algorithm - Defines the algorithm used to select the target nodes for rebalancing.
- Aggressive
Mode bool - When enabled rebalancing will also consider problematic pods (pods without controller, job pods, pods with removal-disabled annotation) as not-problematic.
- Aggressive
Mode GetConfig Rebalancing Schedule Data Source Launch Configuration Aggressive Mode Config - Advanced configuration for aggressive rebalancing mode.
- Execution
Conditions GetRebalancing Schedule Data Source Launch Configuration Execution Conditions - Keep
Drain boolTimeout Nodes - Defines whether the nodes that failed to get drained until a predefined timeout, will be kept with a rebalancing.cast.ai/status=drain-failed annotation instead of forcefully drained.
- Node
Ttl intSeconds - Specifies amount of time since node creation before the node is allowed to be considered for automated rebalancing.
- Num
Targeted intNodes - Maximum number of nodes that will be selected for rebalancing.
- Rebalancing
Min intNodes - Minimum number of nodes that should be kept in the cluster after rebalancing.
- Selector string
- Node selector in JSON format.
- Target
Node stringSelection Algorithm - Defines the algorithm used to select the target nodes for rebalancing.
- aggressive
Mode Boolean - When enabled rebalancing will also consider problematic pods (pods without controller, job pods, pods with removal-disabled annotation) as not-problematic.
- aggressive
Mode GetConfig Rebalancing Schedule Data Source Launch Configuration Aggressive Mode Config - Advanced configuration for aggressive rebalancing mode.
- execution
Conditions GetRebalancing Schedule Data Source Launch Configuration Execution Conditions - keep
Drain BooleanTimeout Nodes - Defines whether the nodes that failed to get drained until a predefined timeout, will be kept with a rebalancing.cast.ai/status=drain-failed annotation instead of forcefully drained.
- node
Ttl IntegerSeconds - Specifies amount of time since node creation before the node is allowed to be considered for automated rebalancing.
- num
Targeted IntegerNodes - Maximum number of nodes that will be selected for rebalancing.
- rebalancing
Min IntegerNodes - Minimum number of nodes that should be kept in the cluster after rebalancing.
- selector String
- Node selector in JSON format.
- target
Node StringSelection Algorithm - Defines the algorithm used to select the target nodes for rebalancing.
- aggressive
Mode boolean - When enabled rebalancing will also consider problematic pods (pods without controller, job pods, pods with removal-disabled annotation) as not-problematic.
- aggressive
Mode rebalancingConfig Get Rebalancing Schedule Data Source Launch Configuration Aggressive Mode Config - Advanced configuration for aggressive rebalancing mode.
- execution
Conditions rebalancingGet Rebalancing Schedule Data Source Launch Configuration Execution Conditions - keep
Drain booleanTimeout Nodes - Defines whether the nodes that failed to get drained until a predefined timeout, will be kept with a rebalancing.cast.ai/status=drain-failed annotation instead of forcefully drained.
- node
Ttl numberSeconds - Specifies amount of time since node creation before the node is allowed to be considered for automated rebalancing.
- num
Targeted numberNodes - Maximum number of nodes that will be selected for rebalancing.
- rebalancing
Min numberNodes - Minimum number of nodes that should be kept in the cluster after rebalancing.
- selector string
- Node selector in JSON format.
- target
Node stringSelection Algorithm - Defines the algorithm used to select the target nodes for rebalancing.
- aggressive_
mode bool - When enabled rebalancing will also consider problematic pods (pods without controller, job pods, pods with removal-disabled annotation) as not-problematic.
- aggressive_
mode_ rebalancing.config Get Rebalancing Schedule Data Source Launch Configuration Aggressive Mode Config - Advanced configuration for aggressive rebalancing mode.
- execution_
conditions rebalancing.Get Rebalancing Schedule Data Source Launch Configuration Execution Conditions - keep_
drain_ booltimeout_ nodes - Defines whether the nodes that failed to get drained until a predefined timeout, will be kept with a rebalancing.cast.ai/status=drain-failed annotation instead of forcefully drained.
- node_
ttl_ intseconds - Specifies amount of time since node creation before the node is allowed to be considered for automated rebalancing.
- num_
targeted_ intnodes - Maximum number of nodes that will be selected for rebalancing.
- rebalancing_
min_ intnodes - Minimum number of nodes that should be kept in the cluster after rebalancing.
- selector str
- Node selector in JSON format.
- target_
node_ strselection_ algorithm - Defines the algorithm used to select the target nodes for rebalancing.
- aggressive
Mode Boolean - When enabled rebalancing will also consider problematic pods (pods without controller, job pods, pods with removal-disabled annotation) as not-problematic.
- aggressive
Mode Property MapConfig - Advanced configuration for aggressive rebalancing mode.
- execution
Conditions Property Map - keep
Drain BooleanTimeout Nodes - Defines whether the nodes that failed to get drained until a predefined timeout, will be kept with a rebalancing.cast.ai/status=drain-failed annotation instead of forcefully drained.
- node
Ttl NumberSeconds - Specifies amount of time since node creation before the node is allowed to be considered for automated rebalancing.
- num
Targeted NumberNodes - Maximum number of nodes that will be selected for rebalancing.
- rebalancing
Min NumberNodes - Minimum number of nodes that should be kept in the cluster after rebalancing.
- selector String
- Node selector in JSON format.
- target
Node StringSelection Algorithm - Defines the algorithm used to select the target nodes for rebalancing.
GetRebalancingScheduleDataSourceLaunchConfigurationAggressiveModeConfig
- Ignore
Local boolPersistent Volumes - Rebalance workloads that use local-path Persistent Volumes. THIS WILL RESULT IN DATA LOSS.
- Ignore
Problem boolJob Pods - Pods spawned by Jobs or CronJobs will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, pods spawned by Jobs or CronJobs will be terminated if the Rebalancer picks a node that runs them. As such, they are likely to lose their progress.
- Ignore
Problem boolPods Without Controller - Pods that don't have a controller (bare pods) will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods might not restart, since they have no controller to do it.
- Ignore
Problem boolRemoval Disabled Pods - Pods that are marked with "removal disabled" will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods will be evicted and disrupted.
- Ignore
Local boolPersistent Volumes - Rebalance workloads that use local-path Persistent Volumes. THIS WILL RESULT IN DATA LOSS.
- Ignore
Problem boolJob Pods - Pods spawned by Jobs or CronJobs will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, pods spawned by Jobs or CronJobs will be terminated if the Rebalancer picks a node that runs them. As such, they are likely to lose their progress.
- Ignore
Problem boolPods Without Controller - Pods that don't have a controller (bare pods) will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods might not restart, since they have no controller to do it.
- Ignore
Problem boolRemoval Disabled Pods - Pods that are marked with "removal disabled" will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods will be evicted and disrupted.
- ignore
Local BooleanPersistent Volumes - Rebalance workloads that use local-path Persistent Volumes. THIS WILL RESULT IN DATA LOSS.
- ignore
Problem BooleanJob Pods - Pods spawned by Jobs or CronJobs will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, pods spawned by Jobs or CronJobs will be terminated if the Rebalancer picks a node that runs them. As such, they are likely to lose their progress.
- ignore
Problem BooleanPods Without Controller - Pods that don't have a controller (bare pods) will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods might not restart, since they have no controller to do it.
- ignore
Problem BooleanRemoval Disabled Pods - Pods that are marked with "removal disabled" will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods will be evicted and disrupted.
- ignore
Local booleanPersistent Volumes - Rebalance workloads that use local-path Persistent Volumes. THIS WILL RESULT IN DATA LOSS.
- ignore
Problem booleanJob Pods - Pods spawned by Jobs or CronJobs will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, pods spawned by Jobs or CronJobs will be terminated if the Rebalancer picks a node that runs them. As such, they are likely to lose their progress.
- ignore
Problem booleanPods Without Controller - Pods that don't have a controller (bare pods) will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods might not restart, since they have no controller to do it.
- ignore
Problem booleanRemoval Disabled Pods - Pods that are marked with "removal disabled" will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods will be evicted and disrupted.
- ignore_
local_ boolpersistent_ volumes - Rebalance workloads that use local-path Persistent Volumes. THIS WILL RESULT IN DATA LOSS.
- ignore_
problem_ booljob_ pods - Pods spawned by Jobs or CronJobs will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, pods spawned by Jobs or CronJobs will be terminated if the Rebalancer picks a node that runs them. As such, they are likely to lose their progress.
- ignore_
problem_ boolpods_ without_ controller - Pods that don't have a controller (bare pods) will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods might not restart, since they have no controller to do it.
- ignore_
problem_ boolremoval_ disabled_ pods - Pods that are marked with "removal disabled" will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods will be evicted and disrupted.
- ignore
Local BooleanPersistent Volumes - Rebalance workloads that use local-path Persistent Volumes. THIS WILL RESULT IN DATA LOSS.
- ignore
Problem BooleanJob Pods - Pods spawned by Jobs or CronJobs will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, pods spawned by Jobs or CronJobs will be terminated if the Rebalancer picks a node that runs them. As such, they are likely to lose their progress.
- ignore
Problem BooleanPods Without Controller - Pods that don't have a controller (bare pods) will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods might not restart, since they have no controller to do it.
- ignore
Problem BooleanRemoval Disabled Pods - Pods that are marked with "removal disabled" will not prevent the Rebalancer from deleting a node on which they run. WARNING: When true, such pods will be evicted and disrupted.
GetRebalancingScheduleDataSourceLaunchConfigurationExecutionConditions
- Enabled bool
- Enables or disables the execution conditions.
- Achieved
Savings intPercentage - The percentage of the predicted savings that must be achieved in order to fully execute the plan.If the savings are not achieved after creating the new nodes, the plan will fail and delete the created nodes.
- Enabled bool
- Enables or disables the execution conditions.
- Achieved
Savings intPercentage - The percentage of the predicted savings that must be achieved in order to fully execute the plan.If the savings are not achieved after creating the new nodes, the plan will fail and delete the created nodes.
- enabled Boolean
- Enables or disables the execution conditions.
- achieved
Savings IntegerPercentage - The percentage of the predicted savings that must be achieved in order to fully execute the plan.If the savings are not achieved after creating the new nodes, the plan will fail and delete the created nodes.
- enabled boolean
- Enables or disables the execution conditions.
- achieved
Savings numberPercentage - The percentage of the predicted savings that must be achieved in order to fully execute the plan.If the savings are not achieved after creating the new nodes, the plan will fail and delete the created nodes.
- enabled bool
- Enables or disables the execution conditions.
- achieved_
savings_ intpercentage - The percentage of the predicted savings that must be achieved in order to fully execute the plan.If the savings are not achieved after creating the new nodes, the plan will fail and delete the created nodes.
- enabled Boolean
- Enables or disables the execution conditions.
- achieved
Savings NumberPercentage - The percentage of the predicted savings that must be achieved in order to fully execute the plan.If the savings are not achieved after creating the new nodes, the plan will fail and delete the created nodes.
GetRebalancingScheduleDataSourceSchedule
- Cron string
Cron expression defining when the schedule should trigger.
The
cronexpression can optionally include theCRON_TZvariable at the beginning to specify the timezone in which the schedule should be interpreted.Example:
CRON_TZ=America/New_York 0 12 * * ?In the example above, the
CRON_TZvariable is set to "America/New_York" indicating that the cron expression should be interpreted in the Eastern Time (ET) timezone.To retrieve a list of available timezone values, you can use the following API endpoint:
GET https://api.cast.ai/v1/time-zones
When using the
CRON_TZvariable, ensure that the specified timezone is valid and supported by checking the list of available timezones from the API endpoint. If theCRON_TZvariable is not specified, the cron expression will be interpreted in the UTC timezone.
- Cron string
Cron expression defining when the schedule should trigger.
The
cronexpression can optionally include theCRON_TZvariable at the beginning to specify the timezone in which the schedule should be interpreted.Example:
CRON_TZ=America/New_York 0 12 * * ?In the example above, the
CRON_TZvariable is set to "America/New_York" indicating that the cron expression should be interpreted in the Eastern Time (ET) timezone.To retrieve a list of available timezone values, you can use the following API endpoint:
GET https://api.cast.ai/v1/time-zones
When using the
CRON_TZvariable, ensure that the specified timezone is valid and supported by checking the list of available timezones from the API endpoint. If theCRON_TZvariable is not specified, the cron expression will be interpreted in the UTC timezone.
- cron String
Cron expression defining when the schedule should trigger.
The
cronexpression can optionally include theCRON_TZvariable at the beginning to specify the timezone in which the schedule should be interpreted.Example:
CRON_TZ=America/New_York 0 12 * * ?In the example above, the
CRON_TZvariable is set to "America/New_York" indicating that the cron expression should be interpreted in the Eastern Time (ET) timezone.To retrieve a list of available timezone values, you can use the following API endpoint:
GET https://api.cast.ai/v1/time-zones
When using the
CRON_TZvariable, ensure that the specified timezone is valid and supported by checking the list of available timezones from the API endpoint. If theCRON_TZvariable is not specified, the cron expression will be interpreted in the UTC timezone.
- cron string
Cron expression defining when the schedule should trigger.
The
cronexpression can optionally include theCRON_TZvariable at the beginning to specify the timezone in which the schedule should be interpreted.Example:
CRON_TZ=America/New_York 0 12 * * ?In the example above, the
CRON_TZvariable is set to "America/New_York" indicating that the cron expression should be interpreted in the Eastern Time (ET) timezone.To retrieve a list of available timezone values, you can use the following API endpoint:
GET https://api.cast.ai/v1/time-zones
When using the
CRON_TZvariable, ensure that the specified timezone is valid and supported by checking the list of available timezones from the API endpoint. If theCRON_TZvariable is not specified, the cron expression will be interpreted in the UTC timezone.
- cron str
Cron expression defining when the schedule should trigger.
The
cronexpression can optionally include theCRON_TZvariable at the beginning to specify the timezone in which the schedule should be interpreted.Example:
CRON_TZ=America/New_York 0 12 * * ?In the example above, the
CRON_TZvariable is set to "America/New_York" indicating that the cron expression should be interpreted in the Eastern Time (ET) timezone.To retrieve a list of available timezone values, you can use the following API endpoint:
GET https://api.cast.ai/v1/time-zones
When using the
CRON_TZvariable, ensure that the specified timezone is valid and supported by checking the list of available timezones from the API endpoint. If theCRON_TZvariable is not specified, the cron expression will be interpreted in the UTC timezone.
- cron String
Cron expression defining when the schedule should trigger.
The
cronexpression can optionally include theCRON_TZvariable at the beginning to specify the timezone in which the schedule should be interpreted.Example:
CRON_TZ=America/New_York 0 12 * * ?In the example above, the
CRON_TZvariable is set to "America/New_York" indicating that the cron expression should be interpreted in the Eastern Time (ET) timezone.To retrieve a list of available timezone values, you can use the following API endpoint:
GET https://api.cast.ai/v1/time-zones
When using the
CRON_TZvariable, ensure that the specified timezone is valid and supported by checking the list of available timezones from the API endpoint. If theCRON_TZvariable is not specified, the cron expression will be interpreted in the UTC timezone.
GetRebalancingScheduleDataSourceTriggerCondition
- Savings
Percentage double - Defines the minimum percentage of savings expected.
- Ignore
Savings bool - If true, the savings percentage will be ignored and the rebalancing will be triggered regardless of the savings percentage.
- Savings
Percentage float64 - Defines the minimum percentage of savings expected.
- Ignore
Savings bool - If true, the savings percentage will be ignored and the rebalancing will be triggered regardless of the savings percentage.
- savings
Percentage Double - Defines the minimum percentage of savings expected.
- ignore
Savings Boolean - If true, the savings percentage will be ignored and the rebalancing will be triggered regardless of the savings percentage.
- savings
Percentage number - Defines the minimum percentage of savings expected.
- ignore
Savings boolean - If true, the savings percentage will be ignored and the rebalancing will be triggered regardless of the savings percentage.
- savings_
percentage float - Defines the minimum percentage of savings expected.
- ignore_
savings bool - If true, the savings percentage will be ignored and the rebalancing will be triggered regardless of the savings percentage.
- savings
Percentage Number - Defines the minimum percentage of savings expected.
- ignore
Savings Boolean - If true, the savings percentage will be ignored and the rebalancing will be triggered regardless of the savings percentage.
Package Details
- Repository
- castai castai/pulumi-castai
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
castaiTerraform Provider.
