apply prettier

caas-team · Nov 13, 2024 · e49266a · e49266a
1 parent 90b750c
commit e49266a
Show file tree

Hide file tree

Showing 3 changed files with 19 additions and 17 deletions.
diff --git a/.github/ISSUE_TEMPLATE/issue-template.md b/.github/ISSUE_TEMPLATE/issue-template.md
@@ -1,21 +1,21 @@
 ---
 name: Issue Template
 about: The general template for issues
-title: ''
-labels: ''
-assignees: ''
-
+title: ""
+labels: ""
+assignees: ""
 ---
 
 <!--
 Use this issue template for pointing out a general issue.
 -->
+
 ## Issue
+
 <!--
 Briefly describe the issue.
 -->
 
-
 ### Problem to solve
 
 <!-- Include the following detail as necessary:

diff --git a/README.md b/README.md
@@ -284,7 +284,7 @@ Each time specification can be in one of two formats:
   `<YYYY>-<MM>-<DD>T<HH>:<MM>:<SS>[+-]<TZHH>:<TZMM>`.
 
 If you are using the first format (recurring specifications) it is important
-to note that the  downscaler can only interpret configurations within
+to note that the downscaler can only interpret configurations within
 a single day and cannot process intervals that stretch across two different days.
 As a result, overlapping time intervals are not supported.
 
@@ -399,14 +399,14 @@ annotation `downscaler/downtime` on each deployment
 
 `--upscale-target-only`
 
-:   When this optional argument is used, only the namespaces currently
-    targeted by the downscaler will be upscaled during wake-up times.
-    For instance, if your downscaler initially manages namespaces
-    A, B, and C, but is later reconfigured to target only namespaces
-    B and C, namespace A will remain downscaled if it was downscaled
-    at the time of reconfiguration. If the parameter is not used,
-    all previously downscaled namespaces may be upscaled, even if
-    they are no longer targeted by the downscaler.
+: When this optional argument is used, only the namespaces currently
+targeted by the downscaler will be upscaled during wake-up times.
+For instance, if your downscaler initially manages namespaces
+A, B, and C, but is later reconfigured to target only namespaces
+B and C, namespace A will remain downscaled if it was downscaled
+at the time of reconfiguration. If the parameter is not used,
+all previously downscaled namespaces may be upscaled, even if
+they are no longer targeted by the downscaler.
 
 `--exclude-namespaces`
 

diff --git a/chart/README.md b/chart/README.md
@@ -5,11 +5,11 @@ This repository offers a Helm chart for the `py-kube-downscaler`.
 ## Important values
 
 | Key                | Type   | Example                                                                                               | Description                                     |
-|--------------------|--------|-------------------------------------------------------------------------------------------------------|-------------------------------------------------|
+| ------------------ | ------ | ----------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
 | image.tag          | string | `"23.2.0@sha256:4129e7e7551eb451ee2b43680ef818f3057304ad50888f79ec9722afab6c29ff"`                    | Tag of the image to use                         |
 | arguments          | list   | `[--interval=60,--include-resources=deployments,statefulsets,horizontalpodautoscalers,scaledobjects]` | Arguments to pass to the kube-downscaler binary |
 | excludedNamespaces | list   | `["namespace-a", "namespace-b"]`                                                                      | Namespaces to exclude from downscaling          |
-| extraConfig        | string | `"DOWNSCALE_PERIOD: 'Mon-Sun 19:00-20:00 Europe/Berlin'"`                                              | Additional configuration in ConfigMap format    |
+| extraConfig        | string | `"DOWNSCALE_PERIOD: 'Mon-Sun 19:00-20:00 Europe/Berlin'"`                                             | Additional configuration in ConfigMap format    |
 
 # Deploy py-kube-downscaler using Helm chart
 
@@ -57,7 +57,8 @@ Note: In case RBAC is enabled, a new service account will be created for py-kube
 otherwise the 'default' one will be used.
 
 3. Deploy py-kube-downscaler:
-You can add our chart repository and deploy it by running:
+   You can add our chart repository and deploy it by running:
+
 ```bash
 helm repo add caas-team https://caas-team.github.io/helm-charts/
 
@@ -67,6 +68,7 @@ helm install py-kube-downscaler caas-team/py-kube-downscaler -n py-kube-downscal
 **OR**
 
 You can alternatively clone this repository, change the current directory to the py-kube-downscaler repository and run:
+
 ```bash
 helm install py-kube-downscaler ./chart -n py-kube-downscaler
 ```