Skip to content

Commit 5e452b9

Browse files
dylanratcliffeactions-user
authored andcommittedMar 6, 2025·
Merge pull request #787 from overmindtech/k8s-source-docs
Fix K8s source docs & helm GitOrigin-RevId: f259deaa85d175fdead0ab37376fb041c6386da7
1 parent f79e75d commit 5e452b9

File tree

5 files changed

+8
-9
lines changed

5 files changed

+8
-9
lines changed
 

‎k8s-source/deployments/overmind-kube-source/Chart.yaml

+6-2
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,14 @@ type: application
1515
# This is the chart version. This version number should be incremented each time you make changes
1616
# to the chart and its templates, including the app version.
1717
# Versions are expected to follow Semantic Versioning (https://semver.org/)
18-
version: 0.9.1
18+
#
19+
# This is set during CI
20+
version: 0.0.0
1921

2022
# This is the version number of the application being deployed. This version number should be
2123
# incremented each time you make changes to the application. Versions are not expected to
2224
# follow Semantic Versioning. They should reflect the version the application is using.
2325
# It is recommended to use it with quotes.
24-
appVersion: "0.9.1"
26+
#
27+
# This is set during CI
28+
appVersion: "0.0.0"

‎k8s-source/deployments/overmind-kube-source/README.md

+1-6
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,4 @@ helm uninstall k8s-source
1616

1717
## Releasing
1818

19-
These charts are released automatically using [helm-chart-releaser](https://github.com/marketplace/actions/helm-chart-releaser). Chart version has to match the tags in the repo. Since the action only checks for changes since the last tag, these are the right hoops to jump through:
20-
21-
* Edit `Chart.yaml`, updating `version` to the new version
22-
* Commit and push to `main`
23-
* wait for the release to happen (`overmind-kube-source-$version` tag shows up, discord notification)
24-
* tag the same commit with `v$version` and push to github to have the corresponding docker image built
19+
These charts are automatically released and pushed to Cloudsmith when the monorepo is tagged with a version in the following format `k8s-source/v1.2.3`. This will cause the docker container to be built, tagged with `1.2.3`, pushed, and a new corresponding helm chart released. See `.github/workflows/k8s-source-release.yml` for more details

‎k8s-source/deployments/overmind-kube-source/values.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
replicaCount: 1
66

77
image:
8-
repository: ghcr.io/overmindtech/k8s-source
8+
repository: ghcr.io/overmindtech/workspace/k8s-source
99
pullPolicy: Always
1010
# Overrides the image tag whose default is the chart appVersion.
1111
tag: ""

‎k8s-source/doc/account_settings.png

-48.8 KB
Binary file not shown.

‎k8s-source/doc/api_key.png

-72.7 KB
Binary file not shown.

0 commit comments

Comments
 (0)
Please sign in to comment.