microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
AKS samples don't work in AKS 1.2.2+ and don't deploy
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Describe the issue
AKS samples don't work in AKS 1.2.2, specifically APIs which are deprecated:
cert-manager.io/v1alpha2
networking.k8s.io/v1beta1
Source: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-22
After updating the template to use supported APIs with the following template changes means it'll deploy:
ingress.yaml:
{{- $fullName := include "fullName" . -}}
{{- $namespace := include "namespace" . -}}
apiVersion: networking.k8s.io/v1
[snip]
rules:
- host: {{ include "hostName" . }}
http:
paths:
- backend:
service:
name: {{ $fullName }}-routing
port:
number: 443
path: /
pathType: Prefix
cluster-issuer.yaml:
apiVersion: cert-manager.io/v1
...but it fails to get a certificate from letsencrypt, and therefore never gets the SSL certificate.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ingress.yaml and cluster-issuer.yaml, then compare their API versions with the Kubernetes v1.22 deprecation guide. Deploy the updated templates on AKS 1.2.2+ and investigate the certificate flow; done means the samples deploy and Let's Encrypt issues the SSL certificate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes, yaml
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100