-
Notifications
You must be signed in to change notification settings - Fork 29
Azure opentelemetry changes #94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from 8 commits
43df22b
f436633
b012663
1e4ae68
42cd57c
7362be3
cc2069f
4b7f630
2255b6b
7884879
0d7d2bc
72c748d
96a4ffc
de2d9eb
e5f87cc
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| == HTTP application routing in Azure: | ||
| The HTTP application routing add-on is designed to let you quickly create an ingress controller and access your applications. | ||
| This add-on is not currently designed for use in a production environment and is not recommended for production use. | ||
|
|
||
| Following steps to enable HTTP application routing. | ||
|
|
||
| . Enable HTTP routing on existing AKS cluster using the `az aks enable-addons` with the Azure CLI | ||
|
|
||
| az aks enable-addons --resource-group myResourceGroup --name myAKSCluster --addons http_application_routing | ||
|
|
||
|
|
||
| . use the `az aks show` command to retrieve the DNS zone name. | ||
|
|
||
| az aks show --resource-group myResourceGroup --name myAKSCluster --query addonProfiles.httpApplicationRouting.config.HTTPApplicationRoutingZoneName -o table | ||
|
|
||
| . Adding annotations | ||
|
|
||
| annotations: | ||
| kubernetes.io/ingress.class: addon-http-application-routing | ||
|
|
||
| . Change your ingress host with http application DNS Zone name. | ||
|
|
||
| host: xxxxx.xxxxxx.xxxx.region.aksapp.io | ||
|
|
||
| == Nginx-ingress-controller-setup: | ||
|
|
||
| Install Nginx ingress controller in kubernetes cluster by using helm chart. | ||
|
|
||
| * Adding the Helm repository, if you’re installing the chart via the helm repository. | ||
|
|
||
| helm repo add bitnami https://charts.bitnami.com/bitnami | ||
|
|
||
| * Upgrading the Chart | ||
|
|
||
| helm repo update | ||
|
|
||
| * Installing the Chart | ||
| If you have Helm, you can deploy the ingress controller with the following command: | ||
|
|
||
| AWS - EKS: | ||
|
|
||
| helm upgrade --install nginx-ingress nginx-ingress-controller --set ingressClassResource.default=true --set containerSecurityContext.allowPrivilegeEscalation=false --repo https://charts.bitnami.com/bitnami --namespace nginx-ingress --create-namespace | ||
|
|
||
| AZURE - AKS: | ||
|
|
||
| helm install nginx-stable nginx-stable/nginx-ingress --set controller.setAsDefaultIngress=true --namespace nginx-ingress --create-namespace | ||
|
|
||
| == Examples | ||
| === Providing Dynamic Values to Helm chart | ||
| When installing Helm charts with the helm install command, the `--set` argument allows you to define value in a values.yaml file, `application.cloud` is deployment environment, aws or azure, `ingress.application.host` is to set host value. | ||
|
|
||
| helm install otlp ./helm --set application.cloud="AWS" --set ingress.application.host="xxx.com" | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| {{/* | ||
| Prepare ingress host, pass it as parameter. | ||
| */}} | ||
| {{- define "ingress.application.host" -}} | ||
| {{- printf "application.%s" .Values.ingress.host -}} | ||
| {{- end -}} | ||
|
|
||
| {{- define "ingress.jaeger.host" -}} | ||
| {{- printf "jaeger.%s" .Values.ingress.host -}} | ||
| {{- end -}} | ||
|
|
||
| {{- define "ingress.grafana.host" -}} | ||
| {{- printf "grafana.%s" .Values.ingress.host -}} | ||
| {{- end -}} |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,9 +2,17 @@ apiVersion: networking.k8s.io/v1 | |
| kind: Ingress | ||
| metadata: | ||
| name: ingress | ||
| #adding azure addon annotation for http application routing | ||
| annotations: | ||
| {{- if contains $.Values.application.cloud "AWS" }} | ||
| {{ toYaml .Values.ingress.aws.annotations | indent 2 }} | ||
| {{- end }} | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same here. The comment irritates me.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done |
||
| {{- if contains $.Values.application.cloud "AZURE" }} | ||
| {{ toYaml .Values.ingress.azure.annotations | indent 2 }} | ||
| {{- end }} | ||
| spec: | ||
| rules: | ||
| - host: {{ .Values.ingress.application.host }} | ||
| - host: {{ template "ingress.application.host" . }} | ||
| http: | ||
| paths: | ||
| - path: "/" | ||
|
|
@@ -14,7 +22,7 @@ spec: | |
| name: {{ .Values.application.service.name }} | ||
| port: | ||
| number: {{ .Values.ingress.application.port }} | ||
| - host: {{ .Values.ingress.jaeger.host }} | ||
| - host: {{ template "ingress.jaeger.host" . }} | ||
| http: | ||
| paths: | ||
| - path: "/" | ||
|
|
@@ -24,7 +32,7 @@ spec: | |
| name: jaeger-all-in-one | ||
| port: | ||
| number: {{ .Values.ingress.jaeger.port }} | ||
| - host: {{ .Values.ingress.grafana.host }} | ||
| - host: {{ template "ingress.grafana.host" . }} | ||
| http: | ||
| paths: | ||
| - path: "/" | ||
|
|
@@ -33,4 +41,4 @@ spec: | |
| service: | ||
| name: grafana | ||
| port: | ||
| number: {{ .Values.ingress.grafana.port }} | ||
| number: {{ .Values.ingress.grafana.port }} | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,6 @@ | ||
| # Application configuration | ||
| application: | ||
| cloud: "" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would define the possible values for cloud in a comment
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. done |
||
| # Configuration to get the metrics information | ||
| metrics: | ||
| jobname: "metrics-jobname" | ||
|
|
@@ -12,12 +13,17 @@ application: | |
|
|
||
| # Ingress configuration | ||
| ingress: | ||
| aws: | ||
| annotations: {} | ||
| azure: | ||
| annotations: { | ||
| kubernetes.io/ingress.class: addon-http-application-routing | ||
| } | ||
| #hostname should be passed on helm install | ||
| host: "" | ||
| application: | ||
| host: "application.localhost" | ||
| port: 8080 | ||
| jaeger: | ||
| host: "jaeger.localhost" | ||
| port: 16686 | ||
| grafana: | ||
| host: "grafana.localhost" | ||
| port: 3000 | ||
| port: 3000 | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I expected only AKS in this document and not AWS EKS
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Modified document only for AKS