Releases: epam/ai-dial-helm
dial-core-3.0.2
Helm chart for dial core
What's Changed
- feat: support ingress.tls.hosts templating in dial-core helm chart by @nepalevov in #88
- chore: bump epam/ai-dial-ci from 1.9.2 to 1.9.3 by @dependabot in #87
Full Changelog: dial-core-3.0.1...dial-core-3.0.2
dial-core-3.0.1
Helm chart for dial core
What's Changed
- fix: default resources path for redis by @nepalevov in #85
Full Changelog: dial-extension-1.0.6...dial-core-3.0.1
dial-3.3.0
Umbrella chart for DIAL solution
What's Changed
- feat: DIAL release 1.17 by @nepalevov in #89
Full Changelog: dial-core-3.0.2...dial-3.3.0
dial-extension-1.0.6
Helm chart for dial extensions
What's Changed
- feat: support ingress.tls.hosts templating in dial-extension helm chart by @nepalevov in #86
Full Changelog: dial-extension-1.0.5...dial-extension-1.0.6
dial-extension-1.0.5
Helm chart for dial extensions
What's Changed
- feat: added json values schema to dial-extension helm chart by @taa-epam in #76
- chore: remove unused existingConfigmap value
- chore: fix install command in dial-extension README
- chore: bump epam/ai-dial-ci from 1.9.0 to 1.9.2 by @dependabot in #84
Full Changelog: dial-3.2.0...dial-extension-1.0.5
dial-3.2.0
Umbrella chart for DIAL solution
What's Changed
- feat: DIAL release 1.16 by @nepalevov in #83
Full Changelog: dial-3.1.0...dial-3.2.0
dial-3.1.0
Umbrella chart for DIAL solution
What's Changed
- chore: bump actions/setup-python from 5.1.1 to 5.2.0 by @dependabot in #75
- feat: DIAL release 1.15.0 by @nepalevov in #79
Full Changelog: dial-3.0.0...dial-3.1.0
dial-core-3.0.0
Helm chart for dial core
IMPORTANT: Manual Action Required
What's Changed
- feat!: rename encryption values in dial-core chart by @nepalevov in #72
Upgrading
In this version we have to reflect ai-dial-core
application configuration parameters renaming in version 0.15.1+
by renaming several values in this chart.
configuration.encryption.password
parameter is renamed toconfiguration.encryption.secret
configuration.encryption.salt
parameter is changed toconfiguration.encryption.key
How to upgrade to version 3.0.0
a) If using encryption Kubernetes secret created by the chart:
-
Update the parameters you have in your current deployment values (e.g.
values.yaml
file or set via--set
) according to the changes below:configuration.encryption.password
-->configuration.encryption.secret
configuration.encryption.salt
-->configuration.encryption.key
-
Delete the
*-encryption
secret, e.g. (replacemy-release
with the actual release name):kubectl delete secret my-release-dial-core-encryption
-
Proceed with the helm upgrade as usual, e.g.:
helm upgrade my-release dial/dial-core -f values.yaml
b) If using your own managed Kubernetes secret (configuration.encryption.existingSecret
is set):
-
Rename keys in your existing secret:
aidial.encryption.password
-->aidial.encryption.secret
aidial.encryption.salt
-->aidial.encryption.key
You can update your existing secret to rename or move the keys using the following one-liner command (replace
<your-existing-secret-name>
and<namespace>
with the actual values):kubectl get secret <your-existing-secret-name> -o yaml -n <namespace> | jq '.data["aidial.encryption.secret"] = .data["aidial.encryption.password"] | .data["aidial.encryption.key"] = .data["aidial.encryption.salt"] | del(.data["aidial.encryption.password"], .data["aidial.encryption.salt"])' | kubectl replace -f -
-
Proceed with the helm upgrade as usual, e.g.:
helm upgrade my-release dial/dial-core -f values.yaml
Full Changelog: dial-2.9.0...dial-core-3.0.0
dial-3.0.0
Umbrella chart for DIAL solution
IMPORTANT: Manual Action Required
What's Changed
- feat!: core encryption configuration changes in dial chart by @nepalevov in #74
Upgrading
To 3.0.0
In this version we have to reflect ai-dial-core
application configuration parameters renaming in version 0.15.1+
by renaming several values in this chart.
core.configuration.encryption.password
parameter is renamed tocore.configuration.encryption.secret
core.configuration.encryption.salt
parameter is changed tocore.configuration.encryption.key
How to upgrade to version 3.0.0
a) If using encryption Kubernetes secret created by the chart:
-
Update the parameters you have in your current deployment values (e.g.
values.yaml
file or set via--set
) according to the changes below:core.configuration.encryption.password
-->core.configuration.encryption.secret
core.configuration.encryption.salt
-->core.configuration.encryption.key
-
Delete the
*-encryption
secret, e.g. (replacemy-release
with the actual release name):kubectl delete secret my-release-dial-core-encryption
-
Proceed with the helm upgrade as usual, e.g.:
helm upgrade my-release dial/dial -f values.yaml
b) If using your own managed Kubernetes secret (core.configuration.encryption.existingSecret
is set):
-
Rename keys in your existing secret:
aidial.encryption.password
-->aidial.encryption.secret
aidial.encryption.salt
-->aidial.encryption.key
You can update your existing secret to rename or move the keys using the following one-liner command (replace
<your-existing-secret-name>
and<namespace>
with the actual values):kubectl get secret <your-existing-secret-name> -o yaml -n <namespace> | jq '.data["aidial.encryption.secret"] = .data["aidial.encryption.password"] | .data["aidial.encryption.key"] = .data["aidial.encryption.salt"] | del(.data["aidial.encryption.password"], .data["aidial.encryption.salt"])' | kubectl replace -f -
-
Proceed with the helm upgrade as usual, e.g.:
helm upgrade my-release dial/dial -f values.yaml
Full Changelog: dial-core-3.0.0...dial-3.0.0
dial-extension-1.0.4
Helm chart for dial extensions
What's Changed
- chore: bump epam/ai-dial-ci from 1.8.3 to 1.9.0 by @dependabot in #57
- chore: bump actions/setup-python from 5.1.0 to 5.1.1 by @dependabot in #53
- feat: add custom probes to dial-extension chart by @dspashynskyi in #69
Full Changelog: dial-2.8.3...dial-extension-1.0.4