-
Notifications
You must be signed in to change notification settings - Fork 455
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
6.0 helm tenant console service not created #2231
Comments
this should be fixed here: #2230 |
So just to be clear, will these instructions continue to work after the fix? This is for the Operator console, before a Tenant is even created where it assumes a service account + secret has been created for the Operator console... or is the Operator console what was intended to be removed so these instructions are no longer valid? |
I don't think those instructions are any good. There is no long a console in the operator. So step 5 on is no longer usable. |
@bkinzle @JamesAtIntegratnIO Documentation for operator will be updated (our docs team is working on it). There is no operator console in v6 anymore, so all instructions that will describe the operator console will be removed as well. Creating tenants should now be done directly by creating |
When creating a new Tenant with Helm Release 6.0.0. The console service is never created in the Tenant.
Expected Behavior
When creating a new tenant I expect a service for
{{ .Values.tenant.name }}-console
to be created.Current Behavior
Service is not created.
Listing of created resources
values.yaml
Argo Application Manifest
Startup Logs
Possible Solution
Steps to Reproduce (for bugs)
My operator deployment
My tenant deployment
Context
Regression
Your Environment
minio-operator
): Helm 6.0uname -a
): Talos 1.7.5The text was updated successfully, but these errors were encountered: