Hey guys, has anyone else faced this issue with th...
# ory-selfhosting
c
Hey guys, has anyone else faced this issue with the Secret provided by the Hydra chart? https://github.com/ory/k8s/issues/813 What do you think?
re: https://ory-community.slack.com/archives/C02PSRUGUAV/p1757415553004489 @enough-yak-81379 hey 😊 What is the best way to get attention / feedback to these kinds of issues? I'm onboarding self-hosted Ory Hydra (and maybe more in the future). Where there are gaps, I'd like to upstream patches and work with the upstream instead of maintaining a soft-fork.
e
hi there! for now i am the core maintainer of the maester repos, i try to keep the codebase alive, updated and working, as there are people who actively use it, and contribute features
c
I understand that it's more of a skeleton-level and best-effort operation. πŸ™‚ Totally fine, especially since we're very unlikely to become paid self-hosted – contributing back, especially in the Ops area, is how we can repay. What would be the best way to interact, contribute issues (bug reports / feature requests) and solutions (PRs) in a community-oriented way? Is tagging you something that would be frowned upon? Mainly seeking ways to keep the feedback loop tight. πŸ₯Ί
e
no, i don’t mind, and try to be responsive here :d I think the best approach is to create issues/pr/discussions in the repos and ping me on gh if i dont respond within few days. I try to check the notifications a few times per week, but i sometimes can simply overlook something πŸ™‚
c
Noted! πŸ™Œ
I closed the issue in the OP. Your suggestion makes all the sense. I'm not sure how I overlooked the secret nameOverride – likely because it was encapsulated within the secret name template 🀦
e
no worries, i think we have this described in the values.yaml as this is the place people most often look for guidelines, outside of dedicated docs