Closed gigi206 closed 2 years ago
Hi @gigi206 Please check ingress kubectl get ing -A and see if ADDRESS now shows anything other than the IP you expect for DNS. I noticed this just broke on minikube with new nginx-ingress-controller from being passed this argument: --publish-status-address=localhost I was able to temp fix it by editing the controller and removing that line/arg, then scale down and up replicas: kubectl edit deploy -n ingress-nginx ingress-nginx-controller kubectl scale deploy -n ingress-nginx ingress-nginx-controller --replicas=0 kubectl scale deploy -n ingress-nginx ingress-nginx-controller --replicas=1
I try with the ingress-nginx provided by default with rancher rke2 (with daemonset by default). In this case ingress IP corresponding to local IPs of the daemonset servers. And I try with custom ingress-nginx (not the ingress-nginx provided by rke2) + metallb
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: ingress-nginx
namespace: argo-cd
spec:
destination:
namespace: ingress-nginx
server: 'https://kubernetes.default.svc'
source:
chart: ingress-nginx
repoURL: 'https://kubernetes.github.io/ingress-nginx'
targetRevision: '4.0.13'
helm:
parameters:
# - name: controller.kind
# value: daemonset
- name: controller.ingressClassResource.default
value: "true"
- name: defaultBackend.replicaCount
value: "1"
# - name: controller.metrics.enabled # Cf https://artifacthub.io/packages/helm/ingress-nginx/ingress-nginx#prometheus-metrics
# value: "true"
project: default
syncPolicy:
syncOptions:
- CreateNamespace=true
- PruneLast=true
I have the same result in the 2 cases, it's not working
Below is the result of my second test with custom installation of ingress-nginx + metallb 192.168.122.200 is the IP provided by metallb
$ kubectl get ing -A
NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE
argo-cd argo-cd-argocd-server nginx argocd.gigix 192.168.122.200 80, 443 44m
rancher-demo rancher-demo-rancher-demo-helm nginx rancher-demo.gigix 192.168.122.200 80 6m43s
For me no issue there, but I don't understand why rancher-demo.gigix or argocd.gigix not shown in logs and it's not working :(
Adding the annotation ̀external-dns.alpha.kubernetes.io/hostname` on ingress or service seems to do nothing
What happened: I have tested a few weeks ago pdns provider with success :) But now I try to test again and it seems not working :(
What you expected to happen: I install pdns with this helm chart (ArgoCD with helm):
And external-dns whith this:
And powerdns log:
Then I create a service as explained like that:
But example.gigix is never created, anything in log :(
Environment: