Closed c4milo closed 2 months ago
I also opened https://github.com/redpanda-data/redpanda/issues/17540
@c4milo i think i understand this problem now, do you have a simple sample to test this out? otherwise ill assume just enabling config watcher and tls should be enough right?
I am not sure what I am missing here, the config-watcher does a good job of getting cluster-health given the setup of rpk when tls is enabled, done some time ago. Now what I am surprised about is this:
redpanda redpanda 6 2024-04-02 01:17:31.253662 -0400 EDT deployed redpanda-0.1.1 0.1.0
we are currently at, looking at the repo:
redpanda/redpanda 5.7.37 v23.3.10 Redpanda is the real-time engine for modern apps.
and my local installation:
redpanda redpanda 1 2024-04-05 07:33:28.463959 -0400 EDT deployed redpanda-5.7.37 v23.3.10
Clearly something is off, can we verify this using the latest charts please? And if we cannot achieve that, is the expectation that we back-port something?
Does the config map for rpk look like this in your setup?
why is it trying to use the external domain instead of the internal?
@alejandroEsc, please let me know if you want to pair on this one.
@alejandroEsc, please let me know if you want to pair on this one.
yeah, let me know. With the latest changes I am hoping this is resolved?
This issue is probably a symptom of internal certs using the public dns domain, if we fix that it should also fix this.
Camilo Aguilar
Software Engineer
redpanda.com | The streaming data platform for developers
Follow us on Twitter https://twitter.com/redpandadata | Join our community https://join.slack.com/t/redpandacommunity/shared_invite/zt-ng2ze1uv-l5VMWSGQHB9gp47~kNnYGA/
On Fri, Apr 12, 2024 at 1:59 PM Alejandro Escobar @.***> wrote:
@alejandroEsc https://github.com/alejandroEsc, please let me know if you want to pair on this one.
yeah, let me know. With the latest changes I am hoping this is resolved?
— Reply to this email directly, view it on GitHub https://github.com/redpanda-data/helm-charts/issues/1127#issuecomment-2052222632, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAKFUIO4GDQN77EHHZU6FDY5AOHTAVCNFSM6AAAAABFSW7EN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJSGIZDENRTGI . You are receiving this because you were mentioned.Message ID: @.***>
I haven't tested again but I think this issue may have been fixed by https://github.com/redpanda-data/helm-charts/issues/1155 as well.
We have fixed this issue by configuring RPK correctly. It's done in config map where Redpanda.yaml is located.
What happened?
In config-watcher container:
What did you expect to happen?
If I can pass
admin.tls.insecure_skip_verify
also through the CR, it will be fabulous.How can we reproduce it (as minimally and precisely as possible)?. Please include values file.
Anything else we need to know?
Which are the affected charts?
Redpanda, Operator
Chart Version(s)
Cloud provider
JIRA Link: K8S-131