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
I have read and agree to the project's Code of Conduct.
Provider Version
latest
Motivation
When creating a tanzu-mission-control_git_repository and tanzu-mission-control_kustomization, they did not appear in the TMC console until they were deployed to the tanzu-continuousdelivery-resources namespace. They were created in the cluster, but did not appear in the console until they were explicitly deployed to the tanzu-continuousdelivery-resources namespace. Initially I thought this was a bug and created a support ticket. Which caused extra work all around.
Suggestion
One thought is to have the documentation call this out. Or possibly update the example code to default the namespace_name to tanzu-continuousdelivery-resources.
The text was updated successfully, but these errors were encountered:
Code of Conduct
Provider Version
latest
Motivation
When creating a
tanzu-mission-control_git_repository
andtanzu-mission-control_kustomization
, they did not appear in the TMC console until they were deployed to thetanzu-continuousdelivery-resources
namespace. They were created in the cluster, but did not appear in the console until they were explicitly deployed to thetanzu-continuousdelivery-resources
namespace. Initially I thought this was a bug and created a support ticket. Which caused extra work all around.Suggestion
One thought is to have the documentation call this out. Or possibly update the example code to default the
namespace_name
totanzu-continuousdelivery-resources
.The text was updated successfully, but these errors were encountered: