-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/add helm docs #67
base: feat/add-docusaurus
Are you sure you want to change the base?
Conversation
@jonathan-mayer feel free to look over the rest if you have the time |
we should consider updating these packages:
|
We dont need this right? the crds permission is unnessessary since we dont need to do anything with the definitions themselves. We also currently dont need the admission controller ones and taking the recent comments in the issues topic into account it seems as though we won't need them. {{- if not .Values.constrainedDownscaler }}
- apiGroups:
- constraints.gatekeeper.sh
resources:
- kubedownscalerjobsconstraint
verbs:
- get
- create
- watch
- list
- update
- patch
- delete
- apiGroups:
- kyverno.io
resources:
- policies
resourceNames:
- kube-downscaler-jobs-policy
verbs:
- get
- create
- watch
- list
- update
- patch
- delete
- apiGroups:
- kyverno.io
resources:
- policies
verbs:
- get
- create
- watch
- list
- apiGroups:
- templates.gatekeeper.sh
resources:
- constrainttemplate
verbs:
- create
- get
- list
- watch
- apiGroups:
- apiextensions.k8s.io
resources:
- customresourcedefinitions
verbs:
- create
- get
- list
- watch
{{- end }} also we only ever do |
please change every admonition to have empty lines around its contents. see https://docusaurus.io/docs/markdown-features/admonitions#usage-with-prettier for why we (at least sometimes) need it and we should be consistent across the whole docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LLYHSWCOTM
In order to get started installing the GoKubeDownscaler using our Helm Chart you need: | ||
|
||
- [Helm installed][helm-intro] on a system | ||
- have access to a Kubernetes cluster in some kind of way. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this makes the sentence strucutre better: "... to use our Helm Chart you need access to a Kubernetes ...".
- have access to a Kubernetes cluster in some kind of way. | |
- access to a Kubernetes cluster |
If left empty like it is by default the GoKubeDownscaler will use the | ||
[appVersion](repo:deployments/chart/Chart.yaml#L10) of the currently used Helm Chart. | ||
|
||
You can find all versions of the GoKubeDownscaler [on the github releases page](repo/releases). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"/home/installadm/dev/gokubedownscaler2/website/content/docs/1 - helm-chart/2 - values/1 - image.mdx:32:51": No repository path specified
You can find all versions of the GoKubeDownscaler [on the github releases page](repo/releases). | |
You can find all versions of the GoKubeDownscaler [on the github releases page](https://github.com/caas-team/GoKubeDownscaler/releases). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the order right now is not only wierd, since its "Downcsaler", "Workflows", "Helm Chart", "Docker Image" but also has duplicate indexes. I would put the Workflow docs after the Helm Chart. Update the index of the Docker Image docs along with this change.
## Serviceaccount | ||
|
||
The [serviceaccount.yaml](repo:deployments/chart/templates/serviceaccount.yaml) file creates a ServiceAccount | ||
that will be used by the go-kube-downscaler to interact with Kubernetes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should only use one way to write GoKubeDownscaler in the docs.
that will be used by the go-kube-downscaler to interact with Kubernetes. | |
that will be used by the GoKubeDownscaler to interact with Kubernetes. |
|
||
## Workload Permissions | ||
|
||
The Helm Chart assigns get, watch, list, update and patch permissions for the workloads defined in [`includedResources`](ref:docs-helm-included-resources). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Helm Chart assigns get, watch, list, update and patch permissions for the workloads defined in [`includedResources`](ref:docs-helm-included-resources). | |
The Helm Chart assigns `get`, `watch`, `list`, `update` and `patch` permissions for the workloads defined in [`includedResources`](ref:docs-helm-included-resources). |
The `configMap` value contains the two fields `name` and `extraConfig`: | ||
|
||
- `name` defines the name of the configmap for the GoKubeDownscaler. | ||
- `extraConfig` adds additional specified environment variables to the ConfigMap. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- `extraConfig` adds additional specified environment variables to the ConfigMap. | |
- `extraConfig` adds additional specified [environment variables](ref:docs-environment-variables) to the ConfigMap. |
::: | ||
|
||
By default the `extraConfig` field is empty. | ||
Appending a line will add the corresponding environment variable to the configMap. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Appending a line will add the corresponding environment variable to the configMap. | |
Appending a line will add the corresponding [environment variable](ref:docs-environment-variables) to the configMap. |
|
||
This then changes how the GoKubeDownscaler behaves. | ||
|
||
:::tip For example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:::tip For example: | |
:::tip Example |
|
||
If you want the GoKubeDownscaler to be scheduled on a specific type of node you can specify the determining labels of the node here. | ||
|
||
:::tip For example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:::tip For example: | |
:::tip Example |
|
||
This will add the `EXCLUDE_DEPLOYMENTS` environment variable to the configMap. | ||
|
||
The given configuration will exclude the deployments with the name deployment1 and deployment2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The given configuration will exclude the deployments with the name deployment1 and deployment2 | |
The given configuration will exclude the deployments with the name `deployment1` and `deployment2` |
* fix: correction for leader election flag assignment (#123) * refactor: added release namespace to k8s resources in the chart * Update configmap fields * chore: automatically push pre-commit changes --------- Co-authored-by: Jan <[email protected]> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Motivation
Adding documentation for the Helm Chart
Part of #38
Blocked by #80 and #69
Changes
Tests done
Ran the site locally
TODO
Make links to arguments and environment variable pages.