-
Notifications
You must be signed in to change notification settings - Fork 13
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
[Bug]: Using secrets results in "map[...]" values #23
Comments
Thanks for this report. I think it's due to the changes regarding secret management we are introducing at the moment. I will revalidate this and get back to you. A fix will be in v0.2.0 (which is coming soon), along with proper documentation on how secret management works within this chart. |
Okay, thanks for letting me know. One thing I forgot to report back on: After using secrets didn't work, I did change my values file to temporarily use hard-coded strings. I did notice that using for example icinga2:
config:
ticket_salt:
value: changeme like it's documented resulted in a similar icinga2:
config:
ticket_salt: changeme This could be part of the changes you mentioned, as it also happens in the same area. |
As @mocdaniel mentioned this is due to changes in secret management. Secrets are not used in version v0.1.0 (and result in output |
Affected Chart
icinga-stack
Which version of the app contains the bug?
0.1.0
Please describe your problem
Using kubernetes secrets in several places results in output similar to
value: "map[secretKey:username]"
in the generated manifest.Places I have noticed this happening in include:
TicketSalt
const valueApiUser
object's passwordICINGADB_DATABASE_USER
andICINGADB_DATABASE_PASSWORD
MARIADB_USER
andMARIADB_PASSWORD
Here is the output from running
helm install --dry-run --debug
: debug.logOne thing I'd like to mention, though this does not seem to have affected much: I noticed the problem by the
icingadb
pod not coming up due to invalid credentials. Since I wasn't entirely sure of the format for using secrets, as the chart sometimes requires thesecretName
to be at the same level as thesecretKey
and sometimes one level above, I tried using two different configs for theglobal.databases.icingadb
section.At first I had the config looking like this:
and changed it to
Both forms resulted in
map[...]
values, but slightly different. From what I can tell, the latter format is the correct one for the database configuration, though I've only changed theicingadb
section so far. The other sections still used the former format when I ranhelm install --dry-run --debug
, hence the slight discrepancy with the databaseStatefulSet
s.The text was updated successfully, but these errors were encountered: