salaboy
@lony2003 can you take this back, I can work with you to get this reviewed and merged by the maintainers
@pdebruin do you want to work with me on these changes ? I am happy to do a simple configuration first but I might need help for more advanced use...
@joebowbeer yeah I've seen that and that can totally complement what is proposed here. But it defeats the purpose of being super clear about what Dapr needs to run it...
@joebowbeer yeah.. I do agree with that... I want to make sure that people can get started without obfuscating the Kubernetes experience that they are already used to. For example,...
> @salaboy I fully agree that there's a need for a transparent "Getting started with Dapr on Kubernetes", with easy to follow installation steps, similar to what most CNCF projects...
Hey @paulyuk my opinion is still the same `dapr init -k --dev` is not familiar to Kubernetes users. We are pushing Kubernetes users to download a new CLI and then...
@joebowbeer most of CNCF CLIs are helpers to solve some sort of limitations with `kubectl` or to keep open connections. A krew plugin might help, but that is usually just...
@joebowbeer my issue with `dapr -k` is that you get other things installed.. not the installation of Dapr itself. And yes.. +1 to have the helm chart highlighted in the...
@cicoyle that looks like a clash on random ports, which should be very strange, was that issue consistent for multiple runs?
I am closing this PR due inactivity @cicoyle