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

Alternative to Operator console #2360

Closed
manju-rn opened this issue Nov 28, 2024 · 1 comment
Closed

Alternative to Operator console #2360

manju-rn opened this issue Nov 28, 2024 · 1 comment

Comments

@manju-rn
Copy link

Now that from 6.0 operator is deprecated, is there a way to see all the tenants in the single pane?
The operator console used to help summary all the tenants and easy way of navigating to each of the tenants. Dunno why it is discontinued

@ramondeklein
Copy link
Contributor

You can run the following command to show all tenants:

kubectl get tenant --all-namespaces

The most important reason why the console was removed from operator was that it wasn't used that much. Keeping the console up-to-date with the operator features was getting low priority, so the console was lagging behind with features. Even worse... Some operator changes caused bugs in the console that weren't fixed.

Removing the HTTP server from the operator also reduces the memory footprint and attack-surface of the operator. The operator typically runs with elevated privileges in the cluster, so not having an HTTP server is more secure. Although we are not aware of any security issues and this wasn't a reason to remove the console, it was a nice "bonus".

Maintaining the operator console requires significant development resources. Not only because of our changes to the operator, but the world of web frameworks is also changing rapidly. Newer versions of React/Redux also require significant amount of work to keep the console up-to-date. The same with Go and Go packages (although this is often a bit less intrusive). Not updating packages may introduce security issues, so that wasn't an option.

It was either invest in operator console or remove it. Because there is low demand for operator console (although we know some people use it), we decided the drop the operator console. That freed up resources to work on other things that we considered to be more valuable.

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

No branches or pull requests

2 participants