Skip to content

[#563] Use bitnamilegacy repository in Hono values.yaml. #566

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.

Sign up for GitHub

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

Merged
calohmn merged 1 commit into from
Oct 27, 2025
+21 −1
Merged

[#563] Use bitnamilegacy repository in Hono values.yaml. #566

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion charts/hono/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ name: hono
description: |
Eclipse Hono™ provides remote service interfaces for connecting large numbers of IoT devices to a back end and
interacting with them in a uniform way regardless of the device communication protocol.
version: 2.6.4
version: 2.6.5
# Version of Hono being deployed by the chart
appVersion: 2.6.0
keywords:
Expand Down
5 changes: 5 additions & 0 deletions charts/hono/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,6 +101,11 @@ The command removes all the Kubernetes components associated with the chart and

## Release Notes

### 2.6.5

* Use the bitnamilegacy image repository in the mongodb and kafka chart configurations as used images aren't
available anymore in the bitnami repository.

### 2.6.4

* Recreate expired demo certificates.
Expand Down
15 changes: 15 additions & 0 deletions charts/hono/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1426,6 +1426,8 @@ mongodb:
# do not use the default name ("mongodb") because it will lead to a config
# property name clash in the device registry pod when using "hono" as the release name
nameOverride: "monogodb-server"
image:
repository: bitnamilegacy/mongodb
# run single node instance
architecture: "standalone"
# Use StatefulSet instead of Deployment when deploying standalone
Expand Down Expand Up @@ -1730,6 +1732,9 @@ kafka:
# the name of the template (maintains the release name)
nameOverride: "kafka"

image:
repository: bitnamilegacy/kafka

broker:
automountServiceAccountToken: true

Expand All @@ -1750,6 +1755,11 @@ kafka:
external:
protocol: "SASL_SSL"

metrics:
jmx:
image:
repository: bitnamilegacy/jmx-exporter

sasl:
client:
users:
Expand All @@ -1770,6 +1780,8 @@ kafka:
enabled: true
autoDiscovery:
enabled: true
image:
repository: bitnamilegacy/kubectl
broker:
service:
type: "LoadBalancer"
Expand All @@ -1786,6 +1798,9 @@ kafka:
# Note that this could require creating RBAC rules, for more information refer to
# https://github.com/bitnami/charts/tree/master/bitnami/kafka#accessing-kafka-brokers-from-outside-the-cluster
create: true
volumePermissions:
image:
repository: bitnamilegacy/os-shell

# amqpMessagingNetworkExample contains properties for configuring an example AMQP network
# to be used for messaging if "messagingNetworkTypes" contains "amqp"
Expand Down