[GitHub] [flink-kubernetes-operator] GezimSejdiu commented on pull request #170: [FLINK-27235] Publish Flink k8s Operator Helm Charts via Github Actions

GezimSejdiu commented on PR #170: URL: https://github.com/apache/flink-kubernetes-operator/pull/170#issuecomment-1114057825 Hi @wangyang0918 , I tried a solution on how to simulate the re-deployment of the SNAPSHOT (but I didn't like it myself as it is a bit tricky and as such I will

[GitHub] [flink-kubernetes-operator] GezimSejdiu commented on pull request #170: [FLINK-27235] Publish Flink k8s Operator Helm Charts via Github Actions

GezimSejdiu commented on PR #170: URL: https://github.com/apache/flink-kubernetes-operator/pull/170#issuecomment-1105752453 > If the helm chart-releaser could support snapshot override, then this PR makes sense to me. Because users could test the new version easily. Indeed. That woul

[GitHub] [flink-kubernetes-operator] GezimSejdiu commented on pull request #170: [FLINK-27235] Publish Flink k8s Operator Helm Charts via Github Actions

GezimSejdiu commented on PR #170: URL: https://github.com/apache/flink-kubernetes-operator/pull/170#issuecomment-1104478327 > > @GezimSejdiu Thanks for your explanation. I still have some questions before we could merge this PR. > > * IIUC, we need to create a `gh-pag

[GitHub] [flink-kubernetes-operator] GezimSejdiu commented on pull request #170: [FLINK-27235] Publish Flink k8s Operator Helm Charts via Github Actions

GezimSejdiu commented on PR #170: URL: https://github.com/apache/flink-kubernetes-operator/pull/170#issuecomment-1103135999 Hey @wangyang0918, thanks a lot for your review on this. Reg.: > * `https://downloads.apache.org/flink/` is not a right place to host the snapshot he