Dimitris Karakasilis

Now that I think again, what I suggest doesn't make sense, does it? What would the policy block the creation on? The end goal is to prevent the user from...

Currently installing on DO doesn't work. We've sent an email to their support and we opened a thread here: https://forum.digitalocean.com/t/how-can-i-debug-the-deploy-sh-script/695

PR: https://github.com/digitalocean/marketplace-kubernetes/pull/381/files

This PR is not moving. Let's replace it with one that removes Epinio from the markeplace.

Our PR has been merged. I tried the 1-click installation and it worked file. I also updated the instructions (through vendor's portal) to match v1.0.0 and the fact that we...

I sent an email to [email protected] and CCed [email protected]

And it's now updated.

Relevant #434 and #544 . Maybe `epinio target` command should be the one labeling the namespace if not already labeled. Or is this very unexpected?

To make things more complicated, if you annotate a namespace for linkerd, none of the already existing pods become meshed, unless they are restarted. And we can't restart pods we...

Yes, with a move to minio/S3/other, that constraint is gone. I see we also copy a secret and we create a service account in the new namespace: https://github.com/epinio/epinio/blob/main/internal/organizations/organizations.go#L78-L109 So simply...