Closed rlewkowicz-rcd closed 3 years ago
Version 1.3.1 of the chart
Kube versions:
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.1", GitCommit:"c4d752765b3bbac2237bf87cf0b1c2e307844666", GitTreeState:"clean", BuildDate:"2020-12-18T12:09:25Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.6", GitCommit:"fbf646b339dc52336b55d8ec85c181981b86331a", GitTreeState:"clean", BuildDate:"2020-12-18T12:01:36Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
This could be related to my other bug. According to these docs: https://github.com/avinetworks/avi-helm-charts/blob/master/docs/AKO/objects.md See: NodePort Mode
I have a service:
apiVersion: v1 kind: Service metadata: annotations: field.cattle.io/publicEndpoints: '[{"addresses":["10.2.215.244"],"port":31370,"protocol":"TCP","serviceName":"istio-system:istio-ingressgateway","allNodes":true},{"addresses":["10.2.215.244"],"port":31380,"protocol":"TCP","serviceName":"istio-system:istio-ingressgateway","allNodes":true},{"addresses":["10.2.215.244"],"port":30238,"protocol":"TCP","serviceName":"istio-system:istio-ingressgateway","allNodes":true}]' kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app":"istio-ingressgateway","install.operator.istio.io/owning-resource":"istio-controlplane","install.operator.istio.io/owning-resource-namespace":"istio-system","istio":"ingressgateway","istio.io/rev":"default","operator.istio.io/component":"IngressGateways","operator.istio.io/managed":"Reconcile","operator.istio.io/version":"1.7.6","release":"istio"},"name":"istio-ingressgateway","namespace":"istio-system"},"spec":{"ports":[{"name":"status-port","nodePort":31370,"port":15021,"targetPort":15021},{"name":"http2","nodePort":31380,"port":80,"targetPort":8080},{"name":"https","port":443,"targetPort":8443}],"selector":{"app":"istio-ingressgateway","istio":"ingressgateway"},"type":"NodePort"}} creationTimestamp: "2021-01-21T17:11:45Z" labels: app: istio-ingressgateway install.operator.istio.io/owning-resource: istio-controlplane install.operator.istio.io/owning-resource-namespace: istio-system istio: ingressgateway istio.io/rev: default operator.istio.io/component: IngressGateways operator.istio.io/managed: Reconcile operator.istio.io/version: 1.7.6 release: istio name: istio-ingressgateway namespace: istio-system resourceVersion: "250491" selfLink: /api/v1/namespaces/istio-system/services/istio-ingressgateway uid: 7c075802-1aaa-40ce-bb30-5dd584eac889 spec: clusterIP: 10.43.253.225 externalTrafficPolicy: Cluster ports: - name: status-port nodePort: 31370 port: 15021 protocol: TCP targetPort: 15021 - name: http2 nodePort: 31380 port: 80 protocol: TCP targetPort: 8080 - name: https nodePort: 30238 port: 443 protocol: TCP targetPort: 8443 selector: app: istio-ingressgateway istio: ingressgateway sessionAffinity: None type: NodePort status: loadBalancer: {}
It creates the pools:
But no servers in those pools. Type of load balancer works fine.
Actually, that pool only popped up when I create an ingress object. Still problematic that the pools are empty, but with just that service entry, it doesn't create anything
Version 1.3.1 of the chart
Kube versions:
This could be related to my other bug. According to these docs: https://github.com/avinetworks/avi-helm-charts/blob/master/docs/AKO/objects.md See: NodePort Mode
I have a service:
It creates the pools:
But no servers in those pools. Type of load balancer works fine.