Yao Xiao
I think google has already migrated to kpt instead, so this issue should be closed
I'm not sure if I understand, if we're not using go 1.15, there should be some issues when we upgrade go version in kfctl. Let's take a step back, what's...
I think kfctl/upgrade is not supported at this moment, but will be an action item on roadmap /assign
``` managedRelationDatabase: host: REPLACE_WITH_METADATA_RDS_ENDPOINT database: REPLACE_WITH_METADATA_RDS_DATABASE username: REPLACE_WITH_METADATA_DB_USERNAME password: REPLACE_WITH_METADATA_DB_PASSWORD port: REPLACE_WITH_METADATA_DB_PORT ``` I don't really think this will work, because those are interfaces we pre-defined, but not yet implement
All the other parts of implementation are finished, except how to pass `password` to replace K8s secret, it's fairly easy in the k8s onfigmap, however not in k8s secret. It's...
I believe there's no one take care of windows deployment for kubeflow as of now.
I think GCP now is using gcp-blueprint to deploy kubeflow, they might don't want to check backward, @chethanmahadevaiah do you want to try gcp-blueprint instead of kfctl
I believe the issue is solved in favor of https://github.com/kubeflow/manifests/pull/1600