You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
@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 Tenant custom resources or using the tenant helm chart.
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: