Quantcast
Channel: Active questions tagged 22.04 - Ask Ubuntu
Viewing all articles
Browse latest Browse all 4477

Argocd Ingress not working on a Ubuntu Microk8s cluster

$
0
0

I have a working Microk8s cluster. After enabling the argocd community addon, the recommended ingress for argocd sever doesn't seem to be working.

Here's a note I got after enabling the addon:

Infer repository community for addon argocdInfer repository core for addon helm3Addon core/helm3 is already enabledInstalling ArgoCD (Helm v4.6.3)"argo" already exists with the same configuration, skippingRelease "argo-cd" does not exist. Installing it now.NAME: argo-cdLAST DEPLOYED: Thu Oct 20 17:34:33 2022NAMESPACE: argocdSTATUS: deployedREVISION: 1TEST SUITE: NoneNOTES:In order to access the server UI you have the following options:1. kubectl port-forward service/argo-cd-argocd-server -n argocd 8080:443    and then open the browser on http://localhost:8080 and accept the certificate2. enable ingress in the values file `server.ingress.enabled` and either      - Add the annotation for ssl passthrough: https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/ingress.md#option-1-ssl-passthrough      - Add the `--insecure` flag to `server.extraArgs` in the values file and terminate SSL at your ingress: https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/ingress.md#option-2-multiple-ingress-objects-and-hostsAfter reaching the UI the first time you can login with username: admin and the random password generated during the installation. You can find the password by running:kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d(You should delete the initial secret afterwards as suggested by the Getting Started Guide: https://github.com/argoproj/argo-cd/blob/master/docs/getting_started.md#4-login-using-the-cli)ArgoCD is installed

Additionally, here's the Ingress that I defined:

apiVersion: networking.k8s.io/v1kind: Ingressmetadata:  name: argocd-server-ingress  namespace: argocd  annotations:    cert-manager.io/cluster-issuer: lets-encrypt    kubernetes.io/ingress.class: nginx    kubernetes.io/tls-acme: "true"    nginx.ingress.kubernetes.io/ssl-passthrough: "true"    # If you encounter a redirect loop or are getting a 307 response code    # then you need to force the nginx ingress to connect to the backend using HTTPS.    #    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"spec:  rules:  - host: argocd.DOMAIN.com    http:      paths:      - path: /        pathType: Prefix        backend:          service:            name: argo-cd-argocd-server            port:              name: https  tls:  - hosts:    - argocd.DOMAIN.com    secretName: argocd-secret # do not change, this is provided by Argo CD

When I visit the host address, I get this:

enter image description here

From firefox, here's the certificate being issued.

enter image description here

enter image description here

From the notes I got after enabling this addon, how do I do this part enable ingress in the values file server.ingress.enabled this or get my ingress to correctly work?

UPDATE:

Here's what the ingress description looks like:enter image description here


Viewing all articles
Browse latest Browse all 4477

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>