I don't know off the top of my head, but it looks like this may be something that's popped up recently with cert-manager dealing with ports. There seems to be a fix mentioned here, but I haven't had a chance to test anything with it.
I am using AKS and cant find a solution to the above :/
I'm kind of winging it, but if you want to go on a trip with me...
az aks browse --resource-group <resourcegroup> --name <clustername>
Discovery and Load Balancing > Services
Kubernetes
I believe this should give you the option to edit the YAML. I THINK you should just need to add the port there. Something similar to:
"ports": [ { "name": "https", "protocol": "TCP", "port": 443, "targetPort": 443 }, { "name": "webhook", "protocol": "TCP", "port": 6443, "targetPort": 6443 } ]
Maybe? This is just a hunch.
You may also be able to accomplish this through kubectl, but I'm not sure.
I'm working on updating my post to specify which version of Cert-Manager to use, since apparently this is an issue after version 0.6.0
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't know off the top of my head, but it looks like this may be something that's popped up recently with cert-manager dealing with ports. There seems to be a fix mentioned here, but I haven't had a chance to test anything with it.
I am using AKS and cant find a solution to the above :/
I'm kind of winging it, but if you want to go on a trip with me...
az aks browse --resource-group <resourcegroup> --name <clustername>Discovery and Load Balancing > ServicesKubernetesI believe this should give you the option to edit the YAML. I THINK you should just need to add the port there. Something similar to:
Maybe? This is just a hunch.
You may also be able to accomplish this through kubectl, but I'm not sure.
I'm working on updating my post to specify which version of Cert-Manager to use, since apparently this is an issue after version 0.6.0