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

Fleet Deployed Rancher Charts deployed to System Project by default. #435

Closed
serverbaboon opened this issue Jun 25, 2021 · 4 comments
Closed

Comments

@serverbaboon
Copy link

serverbaboon commented Jun 25, 2021

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.

@serverbaboon
Copy link
Author

..or certainly cluster creation in our case.

@kkaempf kkaempf closed this as not planned Won't fix, can't repro, duplicate, stale Dec 13, 2022
@zube zube bot closed this as completed Dec 13, 2022
@zube zube bot removed the [zube]: Done label Mar 14, 2023
@chfrank-cgn
Copy link

This is still a valid issue - Fleet should be able to deploy Rancher cluster tools easily into the System project

@chfrank-cgn
Copy link

Can you please reopen the issue @kkaempf ? Thank you!

@kkaempf
Copy link
Collaborator

kkaempf commented Sep 12, 2023

Fleet engineering does not intend to work on this in a forseeable future.
However, we are accepting respective pull requests 😉

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

4 participants