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
Can Fleet deployment of Rancher Apps such as Monitoring, Logging or Istio default to the System project or allow the Project to be specified.
I have worked around Istio by precreating the Namespace but doing that with monitoring will cause the Helm chart to fail, but in general precreating namespaces ( Rancher API + TF ) is unsatisfactory as it mixes deployemnt methods
I realise this could be classed as a duplicate of #304 , so by all means close it if you agree, but wanted to higlight the default Rancher 'system' apps deployments that are done as part of a cluster creation.
The text was updated successfully, but these errors were encountered:
Can Fleet deployment of Rancher Apps such as Monitoring, Logging or Istio default to the System project or allow the Project to be specified.
I have worked around Istio by precreating the Namespace but doing that with monitoring will cause the Helm chart to fail, but in general precreating namespaces ( Rancher API + TF ) is unsatisfactory as it mixes deployemnt methods
I realise this could be classed as a duplicate of #304 , so by all means close it if you agree, but wanted to higlight the default Rancher 'system' apps deployments that are done as part of a cluster creation.
The text was updated successfully, but these errors were encountered: