Azure Setup Guide / Example

[J12934]

The Azure Setup Example has been started but is still WIP.
Some help, especially from some Azure Experts would be highly appreciated!

https://github.com/J12934/juicy-ctf/blob/master/guides/azure/azure.md

[c0pp3r]

Hey there. So I'm new to Azure but I took the time to try and solve this and here is what I did for anyone that comes along after me.
Here is the yaml for the LB:
kind: Service
apiVersion: v1
metadata:
name: multi-juicer-loadbalancer
spec:
type: LoadBalancer
selector:
app.kubernetes.io/instance: multi-juicer
app.kubernetes.io/name: multi-juicer
ports:
- name: http
protocol: TCP
port: 80
targetPort: 3000

save that to do-lb.yam

kubectl create -f do-lb.yam

You can check on this with:
kubectl describe services multi-juicer-loadbalancer

This should create an external IP for accessing your multi-juicer in Azure after you have followed the rest of the instructions.

When done do:
kubectl delete -f do-lb.yaml

helm delete multi-juicer

[J12934]

Nice 👍, thanks @c0pp3r
Do you know if there is a easy way to set up https & custom domains for the azure loadbalancers?

[c0pp3r]

Nice 👍, thanks @c0pp3r
Do you know if there is a easy way to set up https & custom domains for the azure loadbalancers?

Apologies for the late response. I honestly haven't tried at this point. I would imagine you could handle that somewhere in azure but would have to do some digging.

[J12934]

Azure guide was update to include external connection, but the guide doesn't show how to set it up using https.
Any help / changes on that front would be extremely welcome 🙏

[sydseter]

I added how to setup ssl for the ingress. see: #118

[J12934]

I've removed the WIP warning from the Azure Guide now 👍
I'll keep the issue open so that we can keep discussing further problems and improvements here if they come up.

[dean-mcb]

A crucial step that seemed to be overlooked, was authenticating (logging into) to the helm registry. This should be done before the helm install step, and looks like this: helm registry login ghcr.io --username johndoe --password ghp_YourPersonalAccessTokenHere. These credentials are your github username and a PAT that has the correct scope.

[J12934]

@dean-mcb no thats not the case.
It doesn't require auth, but it will fail if you have at some point added credentials for ghcr.io have expired. (either for helm or for docker)

[dean-mcb]

Your walk-through will be more complete and more useful if you added it in as a possible step, 'note' or checkpoint, or something.