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

[RELEASE] Operator 5.0.11 #1076

Closed
7 of 8 tasks
ravindk89 opened this issue Nov 27, 2023 · 1 comment · Fixed by #1117
Closed
7 of 8 tasks

[RELEASE] Operator 5.0.11 #1076

ravindk89 opened this issue Nov 27, 2023 · 1 comment · Fixed by #1117
Assignees

Comments

@ravindk89
Copy link
Collaborator

ravindk89 commented Nov 27, 2023

Summary

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Goals

  • Document MINIO_OPERATOR_IMAGE envvar override PR 1854
  • Operator STS enabled by default PR 1848
  • Additional improvements to TLS behavior in Operator PR 1847
  • Support for MINIO_KMS_SECRET_KEY_FILE, possible spillover to server docs PR 1789
  • --kes-image flag for kubectl minio tenant create PR 1808
  • --retain-namespace flag for kubectl minio delete PR 1807

** For Consideration **

  • Operator CRD supports PVC deletion on tenant delete - may require some warnings in docs PR 1828
  • Add guidance for health checks outside of pods post change to UBI 9 PR 1831
  • [ ]
@ravindk89 ravindk89 self-assigned this Nov 27, 2023
@ravindk89
Copy link
Collaborator Author

Notes:

  • For PR1789 I don't see any doc references to operator-tls. Maybe we removed them already at some point? I think this is a noop
  • For PR1789 this is related to the non-KMS encryption key setup. We do not document this at all, and I believe this is intentional as we do not recommend using it even for the most basic of testing (it leads to bad habits). I cannot find any references to MINIO_KMS_SECRET_KEY in the docs as-is, and I'm almost certain that is intentional. I'm calling this a no-op.
  • For 1831 I think it's better to address the liveness probe on its own in a separate issue, but I have to do some digging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant