Releases: CluedIn-io/Charts
Releases · CluedIn-io/Charts
Release cluedin-3.2.5
Features
- Added port configuration for CluedIn statistics on 9013
- Added service monitor to listen to port 9013 and send data to Prometheus
- Added engine room environment vars for grafana dashboards (#11359)
- Added stream monitoring
- Expose
submitter.clueSubmissionApiPath
invalues.yaml
to allow configuration of endpoint to post clues. Defaults to/api/v2/clue?save=true
- Expose web_api environment variable to datasource to communicate with cluedin server
- Expose web_api environment variable to clean to communicate with cluedin server
- Expose liveness check for submitter service
- Added
duplication-project
as enabled by default in UI features. - RabbitMQ now has a default policy applied to set all queues as
queue-mode: lazy
for better performance. - Added external-auth service (unused) for future feature
- Added new async submitter
- Added datasource monitoring
- Added datasource submission cancel features
- Increased default Memory for DataSource from 1Gi requested and 2Gi max to 2Gi and 4Gi respectively
- Increased minimum PVC size for Elastic Search from 2Gi to 4Gi
Fixes
- Added
global.uploadFileSizeLimit
to set the maximum filesize for uploaded files. Default:1gb
(Sets on UI + GQL) - Added
datasource.ingestionRequestLimit
to set maximum packet size for data uploaded via api endpoint. Default:1mb
- Security: Update OAUTH2_PROXY to latest (secure) version =>
7.1.3
- Bump Bitnami RabbitMQ Helm chart version =>
8.22.4
- Add additional charts/gauges to monitoring
- Ensure
controller
default image version is based on theglobal.image.tag
property
Release cluedin-3.2.4
Features
Fixes
- Disable
wait
init-containers if a service is running externally (e.g Azure SQL)- SqlServer
sqlserver: isExternal: true
- Redis
redis: isExternal: true
- SqlServer
- Added
Feature
CRD toController
. Currently, only supportsEnableSso
function to enable SSO provider. - See
docs/examples/6_foobar-enablesso.yaml
for an example resource. - Users can now specify
datasource.ingestionEndpointRequestLimit
to set the request limit size for the ingestion endpoint. The value must be specified as a file size (e.g. 1024kb)
Fixes
- Normalize environment variables to support ubuntu based images
Release cluedin-3.2.4-beta.17
Features
Fixes
- Disable
wait
init-containers if a service is running externally (e.g Azure SQL)- SqlServer
sqlserver: isExternal: true
- Redis
redis: isExternal: true
- SqlServer
- Added
Feature
CRD toController
. Currently, only supportsEnableSso
function to enable SSO provider. - See
docs/examples/6_foobar-enablesso.yaml
for an example resource.
Fixes
- Normalize environment variables to support ubuntu based images
Release cluedin-3.2.3
Breaking Changes
- Minimum supported Kubernetes version is now
v1.18
(fromv1.16
)
Fixes
- Fix NGINX Ingress configuration - When
nginxConfiguration.enabled
is set totrue
, it will now create two ingresses. One for the services that proxy through GQL and another for the mapped services that need a customized rewrite rule. - Added
nodeSelector
,tolerations
andaffinity
to all cluedin services. - RabbitMQ
username
+password
passed to all connection strings correctly. Wait
+Bootstrap
container locations are now configurable throughvalues.yaml
- All ingress API versions moved to
networking.k8s.io/v1beta1
asextensions/v1beta1
is deprecated.
Release cluedin-3.2.2
Features
- Enabled CluedIn.Controller support for cluster administration
- Added secret for AuditLog db
- Roles feature is now enabled by default
- RabbitMQ upgraded to v3.8 (prev 3.7)
- RabbitMQ now uses Bitnami sub-chart
- NOTES.txt has been re-worked
- OpenRefine has been moved to its own sub-chart. (Remember to run
helm dep up
to see changes reflected) - FUTURE USE:
Global
section added to values, this is so some common values can be shared between sub-charts.
Breaking Changes
-
Moved to Helm3 (so install behaviour will have changed slightly)
-
dns.prefix
- No longer uses ReleaseName + optionnone
has been removed. If you need a prefix then specify it in the values. -
RabbitMQ support for Azure has changed (using official Bitnami chart).
Options are :- You can create an Azure PVC + then use the
persistence.existingClaim
field to link thedata
directory to it. - You can also use
extraVolumeMounts
+extraVolumes
to configure specific mounts.
You have to setpersistence.enabled
tofalse
so that it doesn't generate a PVC for data.
extraVolumes: - name: data azureDisk: kind: Managed diskName: RABBITMQ_DISK_NAME diskURI: RABBITMQ_DISK_URI
- You can create an Azure PVC + then use the
-
Move
ingress.forceHttps
=>global.ingress.forceHttps
-
Reworked DNS / Prefix / Subdomains section
dns:
hostname: "127.0.0.1.xip.io" # Base host to use for all URLs. Will be combined with the organization name e.g https://<org-name>.<hostname>
prefix: "" # Adds a subdomain prefix to all ingress urls e.g. adding a prefix of 'staging' will create: https://app.staging.<hostname>
subdomains: # Allows overriding of top-level sub-domains (if needed) e.g https://appstaging.<hostname>
application: "app"
openrefine: "clean"
grafanaAdmin: "grafana"
prometheusAdmin: "prometheus"
alertManagerAdmin: "alertmanager"
seq: "seq"
-
Move
dns.hostname
=>global.dns.hostname
-
Move
dns.prefix
=>global.dns.prefix
-
ElasticSearch - Replicas default to
1
not3
-
ElasticSearch - Healthcheck set to
Yellow
if replicas is set to1
Release cluedin-3.2.2-beta.37
Features
- Enabled CluedIn.Controller support for cluster administration
- Added secret for AuditLog db
- Roles feature is now enabled by default
- RabbitMQ upgraded to v3.8 (prev 3.7)
- RabbitMQ now uses Bitnami sub-chart
- NOTES.txt has been re-worked
- OpenRefine has been moved to its own sub-chart. (Remember to run
helm dep up
to see changes reflected) - FUTURE USE:
Global
section added to values, this is so some common values can be shared between sub-charts.
Breaking Changes
- Moved to Helm3 (so install behaviour will have changed slightly)
dns.prefix
- No longer uses ReleaseName + optionnone
has been removed. If you need a prefix then specify it in the values.- RabbitMQ support for Azure has changed (using official Bitnami chart).
Options are :- You can create an Azure PVC + then use the
persistence.existingClaim
field to link thedata
directory to it. - You can also use
extraVolumeMounts
+extraVolumes
to configure specific mounts.
You have to setpersistence.enabled
tofalse
so that it doesn't generate a PVC for data.
extraVolumes: - name: data azureDisk: kind: Managed diskName: RABBITMQ_DISK_NAME diskURI: RABBITMQ_DISK_URI
- Move
dns.hostname
=>global.dns.hostname
- Move
dns.prefix
=>global.dns.prefix
- Move
ingress.forceHttps
=>global.ingress.forceHttps
- You can create an Azure PVC + then use the
Release cluedin-3.2.2-beta.36
Features
- Enabled CluedIn.Controller support for cluster administration
- Added secret for AuditLog db
- Roles feature is now enabled by default
- RabbitMQ upgraded to v3.8 (prev 3.7)
- RabbitMQ now uses Bitnami sub-chart
- NOTES.txt has been re-worked
- OpenRefine has been moved to its own sub-chart. (Remember to run
helm dep up
to see changes reflected) - FUTURE USE:
Global
section added to values, this is so some common values can be shared between sub-charts.
Breaking Changes
- Moved to Helm3 (so install behaviour will have changed slightly)
dns.prefix
- No longer uses ReleaseName + optionnone
has been removed. If you need a prefix then specify it in the values.- RabbitMQ support for Azure has changed (using official Bitnami chart).
Options are :- You can create an Azure PVC + then use the
persistence.existingClaim
field to link thedata
directory to it. - You can also use
extraVolumeMounts
+extraVolumes
to configure specific mounts.
You have to setpersistence.enabled
tofalse
so that it doesn't generate a PVC for data.
extraVolumes: - name: data azureDisk: kind: Managed diskName: RABBITMQ_DISK_NAME diskURI: RABBITMQ_DISK_URI
- Move
dns.hostname
=>global.dns.hostname
- Move
dns.prefix
=>global.dns.prefix
- Move
ingress.forceHttps
=>global.ingress.forceHttps
- You can create an Azure PVC + then use the
Release cluedin-3.2.2-beta.31
Features
- Enabled CluedIn.Controller support for cluster administration
- Added secret for AuditLog db
- Roles feature is now enabled by default
- RabbitMQ upgraded to v3.8 (prev 3.7)
- RabbitMQ now uses Bitnami sub-chart
- NOTES.txt has been re-worked
- OpenRefine has been moved to its own sub-chart. (Remember to run
helm dep up
to see changes reflected) - FUTURE USE:
Global
section added to values, this is so some common values can be shared between sub-charts.
Breaking Changes
- Moved to Helm3 (so install behaviour will have changed slightly)
dns.prefix
- No longer uses ReleaseName + optionnone
has been removed. If you need a prefix then specify it in the values.- RabbitMQ support for Azure has changed (using official Bitnami chart).
Options are :- You can create an Azure PVC + then use the
persistence.existingClaim
field to link thedata
directory to it. - You can also use
extraVolumeMounts
+extraVolumes
to configure specific mounts.
You have to setpersistence.enabled
tofalse
so that it doesn't generate a PVC for data.
extraVolumes: - name: data azureDisk: kind: Managed diskName: RABBITMQ_DISK_NAME diskURI: RABBITMQ_DISK_URI
- Move
dns.hostname
=>global.dns.hostname
- Move
dns.prefix
=>global.dns.prefix
- Move
ingress.forceHttps
=>global.ingress.forceHttps
- You can create an Azure PVC + then use the
Release cluedin-3.2.1
Fixes
- SQL Server - Override VolumeClaims for transact/backup/master
- Add ability to add toleration to deployments
Release cluedin-3.2.2-beta.29
Features
- Enabled CluedIn.Controller support for cluster administration
- Added secret for AuditLog db
- Roles feature is now enabled by default
- RabbitMQ upgraded to v3.8 (prev 3.7)
- RabbitMQ now uses Bitnami sub-chart
- NOTES.txt has been re-worked
- OpenRefine has been moved to its own sub-chart. (Remember to run
helm dep up
to see changes reflected) - FUTURE USE:
Global
section added to values, this is so some common values can be shared between sub-charts.
Breaking Changes
- Moved to Helm3 (so install behaviour will have changed slightly)
dns.prefix
- No longer uses ReleaseName + optionnone
has been removed. If you need a prefix then specify it in the values.- RabbitMQ support for Azure has changed (using official Bitnami chart).
Options are :- You can create an Azure PVC + then use the
persistence.existingClaim
field to link thedata
directory to it. - You can also use
extraVolumeMounts
+extraVolumes
to configure specific mounts.
You have to setpersistence.enabled
tofalse
so that it doesn't generate a PVC for data.
extraVolumes: - name: data azureDisk: kind: Managed diskName: RABBITMQ_DISK_NAME diskURI: RABBITMQ_DISK_URI
- Move
dns.hostname
=>global.dns.hostname
- Move
dns.prefix
=>global.dns.prefix
- Move
ingress.forceHttps
=>global.ingress.forceHttps
- You can create an Azure PVC + then use the