Drop note on budget schedules sometimes being in utc

aws · Apr 19, 2024 · 62e9840 · 62e9840
1 parent 30baa2a
commit 62e9840
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 20 deletions.
diff --git a/website/content/en/docs/concepts/disruption.md b/website/content/en/docs/concepts/disruption.md
@@ -227,7 +227,7 @@ spec:
 
 #### Schedule
 Schedule is a cronjob schedule. Generally, the cron syntax is five space-delimited values with options below, with additional special macros like `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`.
-Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#writing-a-cronjob-spec) for more information on how to follow the cron syntax.
+Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#writing-a-cronjob-spec) for more information on how to follow the cron syntax. Timezones are not currently supported. Schedules are always in UTC.
 
 ```bash
 # ┌───────────── minute (0 - 59)
@@ -241,10 +241,6 @@ Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/worklo
 # * * * * *
 ```
 
-{{% alert title="Note" color="primary" %}}
-Timezones are not supported. Most images default to UTC, but it is best practice to ensure this is the case when considering how to define your budgets.
-{{% /alert %}}
-
 #### Duration
 Duration allows compound durations with minutes and hours values such as `10h5m` or `30m` or `160h`. Since cron syntax does not accept denominations smaller than minutes, users can only define minutes or hours.
 

diff --git a/website/content/en/preview/concepts/disruption.md b/website/content/en/preview/concepts/disruption.md
@@ -227,7 +227,7 @@ spec:
 
 #### Schedule
 Schedule is a cronjob schedule. Generally, the cron syntax is five space-delimited values with options below, with additional special macros like `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`.
-Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#writing-a-cronjob-spec) for more information on how to follow the cron syntax.
+Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#writing-a-cronjob-spec) for more information on how to follow the cron syntax. Timezones are not currently supported. Schedules are always in UTC.
 
 ```bash
 # ┌───────────── minute (0 - 59)
@@ -241,10 +241,6 @@ Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/worklo
 # * * * * *
 ```
 
-{{% alert title="Note" color="primary" %}}
-Timezones are not supported. Most images default to UTC, but it is best practice to ensure this is the case when considering how to define your budgets.
-{{% /alert %}}
-
 #### Duration
 Duration allows compound durations with minutes and hours values such as `10h5m` or `30m` or `160h`. Since cron syntax does not accept denominations smaller than minutes, users can only define minutes or hours.
 

diff --git a/website/content/en/v0.35/concepts/disruption.md b/website/content/en/v0.35/concepts/disruption.md
@@ -223,7 +223,7 @@ spec:
 
 #### Schedule
 Schedule is a cronjob schedule. Generally, the cron syntax is five space-delimited values with options below, with additional special macros like `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`.
-Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#writing-a-cronjob-spec) for more information on how to follow the cron syntax.
+Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#writing-a-cronjob-spec) for more information on how to follow the cron syntax. Timezones are not currently supported. Schedules are always in UTC.
 
 ```bash
 # ┌───────────── minute (0 - 59)
@@ -237,10 +237,6 @@ Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/worklo
 # * * * * *
 ```
 
-{{% alert title="Note" color="primary" %}}
-Timezones are not supported. Most images default to UTC, but it is best practice to ensure this is the case when considering how to define your budgets.
-{{% /alert %}}
-
 #### Duration
 Duration allows compound durations with minutes and hours values such as `10h5m` or `30m` or `160h`. Since cron syntax does not accept denominations smaller than minutes, users can only define minutes or hours.
 

diff --git a/website/content/en/v0.36/concepts/disruption.md b/website/content/en/v0.36/concepts/disruption.md
@@ -227,7 +227,7 @@ spec:
 
 #### Schedule
 Schedule is a cronjob schedule. Generally, the cron syntax is five space-delimited values with options below, with additional special macros like `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`.
-Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#writing-a-cronjob-spec) for more information on how to follow the cron syntax.
+Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#writing-a-cronjob-spec) for more information on how to follow the cron syntax. Timezones are not currently supported. Schedules are always in UTC.
 
 ```bash
 # ┌───────────── minute (0 - 59)
@@ -241,10 +241,6 @@ Follow the [Kubernetes documentation](https://kubernetes.io/docs/concepts/worklo
 # * * * * *
 ```
 
-{{% alert title="Note" color="primary" %}}
-Timezones are not supported. Most images default to UTC, but it is best practice to ensure this is the case when considering how to define your budgets.
-{{% /alert %}}
-
 #### Duration
 Duration allows compound durations with minutes and hours values such as `10h5m` or `30m` or `160h`. Since cron syntax does not accept denominations smaller than minutes, users can only define minutes or hours.