redpanda-data / redpanda-data/redpanda-operator

Support disabling mTLS after mTLS is enabled.

Open
#104 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
84
Forks
32
Avg merge
1d 19h
Merged PRs (30d)
104

Description

After mTLS is enabled at Schema Registry, HTTP Proxy or Kafka, disabling mTLS via unsetting clientCACertRef does not work. Disabling mTLS should be supported.

Steps on reproducing the issue:

  1. Enable mTLS in cluster CR,
      tls:
        clientCACertRef:
          kind: Secret
          name: proxy-trusted-ca-certs
        enabled: true
        requireClientAuth: true
  1. Disable mTLS by not setting clientCACertRef
      tls:
        enabled: true
        requireClientAuth: false

JIRA Link: K8S-206

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by locating the cluster CR TLS handling for Schema Registry, HTTP Proxy, and Kafka, then reproduce the enable-then-unset sequence; done means unsetting clientCACertRef with requireClientAuth false disables mTLS for each affected component.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.