Skip to content
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

Koperator does not clean up SSL resources when switching to PLAINTEXT for all listeners #989

Open
2 tasks done
panyuenlau opened this issue Jun 2, 2023 · 0 comments
Open
2 tasks done
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed triaged root-cause of the bug is known

Comments

@panyuenlau
Copy link
Member

Description

When users configure the Kafka cluster with some SSL listeners (e.g. kafkacluster_with_external_ssl.yaml) to all PLAINTEXT listeners (e.g. https://github.com/banzaicloud/koperator/blob/master/config/samples/kafkacluster_without_ssl.yaml#L52-L66), the Koperator currently does not remove the resources created for SSL listeners.

Expected Behavior

Koperator successfully cleans up all of the resources created for SSL listeners

Actual Behavior

Koperator doesn't clean up any of the resources created for SSL listeners even though they are no longer needed.

Affected Version

<= Koperator v0.24.1

Steps to Reproduce

  1. Create a Kafka cluster with kafkacluster_with_external_ssl.yaml
  2. Configure all listeners to be PLAINTEXT, e.g. https://github.com/banzaicloud/koperator/blob/master/config/samples/kafkacluster_without_ssl.yaml#L52-L66
  3. Check resources created for SSL listeners,KafkaUser, secrets that contain the corresponding certs, etc.

Checklist

@panyuenlau panyuenlau added bug Something isn't working triaged root-cause of the bug is known help wanted Extra attention is needed good first issue Good for newcomers labels Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed triaged root-cause of the bug is known
Projects
None yet
Development

No branches or pull requests

1 participant