We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened: annotation on Ingress object on same cluster works but on Service resource doesn't seem to create the DNS name on route53.
Ingress
Service
What you expected to happen: We expect the DNS name to be
How to reproduce it (as minimally and precisely as possible): This is the yaml config of the EKS service object for Neo4j:
➜ ~ k get service my-neo4j-lb-neo4j -n neo4j -o yaml apiVersion: v1 kind: Service metadata: annotations: external-dns.alpha.kubernetes.io/hostname: neo4j.sfysec-dev.com meta.helm.sh/release-name: my-neo4j meta.helm.sh/release-namespace: neo4j service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags: environment=dev service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:<redacted>:<redacted>:certificate/<redacted> service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "443" service.beta.kubernetes.io/aws-load-balancer-subnets: subnet-<redacted>,subnet-<redacted> service.beta.kubernetes.io/aws-load-balancer-type: external service.beta.kubernetes.io/load-balancer-source-ranges: <redacted> creationTimestamp: "2024-08-12T15:52:26Z" finalizers: - service.k8s.aws/resources labels: app: my-neo4j app.kubernetes.io/managed-by: Helm helm.neo4j.com/neo4j.name: my-neo4j helm.neo4j.com/service: neo4j name: my-neo4j-lb-neo4j namespace: neo4j resourceVersion: "272561661" uid: <redacted> spec: allocateLoadBalancerNodePorts: true clusterIP: 10.100.9.124 clusterIPs: - 10.100.9.124 externalTrafficPolicy: Local healthCheckNodePort: 31307 internalTrafficPolicy: Cluster ipFamilies: - IPv4 ipFamilyPolicy: SingleStack loadBalancerClass: service.k8s.aws/nlb ports: - name: http nodePort: 30404 port: 7474 protocol: TCP targetPort: 7474 - name: https nodePort: 31419 port: 443 protocol: TCP targetPort: 7474 - name: tcp-bolt nodePort: 31753 port: 7687 protocol: TCP targetPort: 7687 selector: app: my-neo4j helm.neo4j.com/clustering: "false" helm.neo4j.com/neo4j.loadbalancer: include sessionAffinity: None type: LoadBalancer status: loadBalancer: ingress: - hostname: k8s-<redacted>.elb.<redacted>.amazonaws.com
Anything else we need to know?:
Environment:
external-dns --version
0.13.2
6.14.1
The text was updated successfully, but these errors were encountered:
/assign
Sorry, something went wrong.
kundan2707
No branches or pull requests
What happened:
annotation on
Ingress
object on same cluster works but onService
resource doesn't seem to create the DNS name on route53.What you expected to happen:
We expect the DNS name to be
How to reproduce it (as minimally and precisely as possible):
This is the yaml config of the EKS service object for Neo4j:
Anything else we need to know?:
Environment:
external-dns --version
): Application Version:0.13.2
, Helm Chart Version:6.14.1
The text was updated successfully, but these errors were encountered: