Open khiemng99 opened 8 months ago
/tmp//tmp/deployment.yaml
educated guess:
to me this looks like there is supposed to be something between the two //, that tends to happen when some variable is empty that is expected to be in there, not sure which one it could be though
This issue is idle because it has been open for 14 days with no activity.
Just to note.. This seems to be an issue with the private-cluster
setting. When working with a non-private cluster it works.
Perhaps is not necessarily a bug, but at least missing documentation on how to deploy to a private cluster.
Just to note.. This seems to be an issue with the
private-cluster
setting. When working with a non-private cluster it works. Perhaps is not necessarily a bug, but at least missing documentation on how to deploy to a private cluster.
Thank you for your response. Yes, with non-private cluster, I can deploy multiple yaml files in the same step, but not with private cluster. Currently I solve this problem by separating each yaml file into one step (maybe it's not optimal but it's the only way I found.
V5 e v5.0.0 tbm está dando esse problema, passando os arquilos listados, ou apenas a pasta dos arquivos.
What happened?
What happened?
I get an error "Error: undefined" when running the following pipeline:
Then, I get the error:
I am not sure what else could be an issue. Many thanks in advance!
Version
Runner
Standard GitHub-hosted runners
Relevant log output