shaneutt
commented
2 years ago Hi Vikram :wave:
No worries or anything, but in the future you can use the discussions board right here in Github for these kinds of questions.
MicroK8s was just the flavor of choice used for testing at the time of writing, not a specific hard requirement.
In a broad general sort of sense this should work in any Kubernetes cluster which is CNCF Compliant, but that's not because we specifically test with any of them it's more an assertion based on compliance with the specification.
If you are building your own cluster with Kubeadm and run into issues with the Kong operator (and you've done investigation which strongly points that the problem is an issue with the operator and not due to something missing or out-of-spec in the environment) it would be reasonable to put in a bug report here for that. Ideally any such report would be something you can provide full reproduction steps for, and even better if you can reproduce it in another Kubernetes distribution like KIND or Microk8s and provide the steps for that.
vbansal22
Will Kong Operator work with other Kubernetes options like Gardner and Kubeadm, or is microk8s a hard requirement? I apologize if I posted this question in the wrong forum. I could not find a mailing list or other dev forums in the readme.
Thanks Vikram