Remove Operator UI #2205
Merged
Remove Operator UI #2205
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dvaldivia
requested review from
harshavardhana,
pjuarezd,
ramondeklein,
cniackz,
cesnietor,
ravindk89,
allanrogerr and
bexsoft
bexsoft
previously approved these changes
Jul 6, 2024
pjuarezd
previously approved these changes
Jul 6, 2024
Fix conflixt on kubernetes-tests.yml
Signed-off-by: pjuarezd <pjuarezd@users.noreply.github.com>
Signed-off-by: pjuarezd <pjuarezd@users.noreply.github.com>
Signed-off-by: pjuarezd <pjuarezd@users.noreply.github.com>
Signed-off-by: pjuarezd <pjuarezd@users.noreply.github.com>
pjuarezd
approved these changes
Jul 8, 2024
ramondeklein
approved these changes
Jul 8, 2024
bexsoft
approved these changes
Jul 8, 2024
bayasdev
approved these changes
Jul 8, 2024
This was referenced Jul 9, 2024
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are phasing out the UI from the MinIO Operator because it has not been maintained actively for a few years. Initially, the UI was introduced to help users become acquainted with the MinIO Operator. However, it's worth noting that no other operators provide a UI for managing their resources. This is an uncommon practice, and maintaining an unused UI diverts resources from more critical aspects of development. Therefore, we are removing the UI to concentrate solely on a declarative approach to managing MinIO deployments through Kubernetes-native primitives, specifically using Tenant YAMLs. This shift allows us to focus on the most efficient and widely-accepted methods of operation within the Kubernetes ecosystem.