A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
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