apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:45:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-69-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-69.ec2.internal uid: 66bcd7b6-5eb6-4a1b-9990-b5d4c221501c resourceVersion: "38554" uid: 136974da-3260-4baf-a552-c55a4db48e12 spec: sourcePod: network-check-source-7d88cb55d8-sh76t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T13:52:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 768.485µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:06:47Z" - latency: 1.062609ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:05:47Z" - latency: 874.817µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:04:47Z" - latency: 1.126012ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:03:47Z" - latency: 759.997µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:47Z" - latency: 1.259323ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:47Z" - latency: 1.097828ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:47Z" - latency: 1.862193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:47Z" - latency: 1.028135ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:58:47Z" - latency: 1.640669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:57:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:45:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-69-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-69.ec2.internal uid: 66bcd7b6-5eb6-4a1b-9990-b5d4c221501c resourceVersion: "34904" uid: 7e2f557f-e30c-4ea2-ab02-2f592bce3ecf spec: sourcePod: network-check-source-7d88cb55d8-sh76t targetEndpoint: adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T13:51:47Z" message: 'load-balancer-api-external: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.545937ms message: 'load-balancer-api-external: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:03:47Z" - latency: 7.037065ms message: 'load-balancer-api-external: resolved host name adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:03:47Z" - latency: 5.108272ms message: 'load-balancer-api-external: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:47Z" - latency: 6.962997ms message: 'load-balancer-api-external: resolved host name adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:02:47Z" - latency: 3.73381ms message: 'load-balancer-api-external: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:47Z" - latency: 6.749002ms message: 'load-balancer-api-external: resolved host name adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:01:47Z" - latency: 5.564526ms message: 'load-balancer-api-external: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:47Z" - latency: 14.062188ms message: 'load-balancer-api-external: resolved host name adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:00:47Z" - latency: 4.966103ms message: 'load-balancer-api-external: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:47Z" - latency: 11.19181ms message: 'load-balancer-api-external: resolved host name adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T13:59:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:45:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-69-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-69.ec2.internal uid: 66bcd7b6-5eb6-4a1b-9990-b5d4c221501c resourceVersion: "34905" uid: debb3f29-71c5-471e-ba05-3b0decbd2e9e spec: sourcePod: network-check-source-7d88cb55d8-sh76t targetEndpoint: adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T13:51:47Z" message: 'load-balancer-api-internal: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.616943ms message: 'load-balancer-api-internal: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:03:47Z" - latency: 7.123169ms message: 'load-balancer-api-internal: resolved host name adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:03:47Z" - latency: 4.208607ms message: 'load-balancer-api-internal: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:47Z" - latency: 7.015135ms message: 'load-balancer-api-internal: resolved host name adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:02:47Z" - latency: 4.428758ms message: 'load-balancer-api-internal: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:47Z" - latency: 6.842135ms message: 'load-balancer-api-internal: resolved host name adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:01:47Z" - latency: 5.553531ms message: 'load-balancer-api-internal: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:47Z" - latency: 14.134809ms message: 'load-balancer-api-internal: resolved host name adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:00:47Z" - latency: 3.52057ms message: 'load-balancer-api-internal: tcp connection to adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:47Z" - latency: 12.291875ms message: 'load-balancer-api-internal: resolved host name adc256e92e5164aa6b694e2dc000319e-19b619f0f1741e0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T13:59:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:45:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-69-to-network-check-target-ip-10-0-128-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-69.ec2.internal uid: 66bcd7b6-5eb6-4a1b-9990-b5d4c221501c resourceVersion: "38552" uid: 4e9cd938-cb1b-4c52-9d40-cd0bd1c59572 spec: sourcePod: network-check-source-7d88cb55d8-sh76t targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T13:52:47Z" message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.252743ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:06:47Z" - latency: 2.206891ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:05:47Z" - latency: 2.097519ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:04:47Z" - latency: 1.887278ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:03:47Z" - latency: 2.064576ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:47Z" - latency: 2.205301ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:47Z" - latency: 2.046402ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:47Z" - latency: 2.497097ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:47Z" - latency: 2.121824ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:58:47Z" - latency: 2.115938ms message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:57:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:45:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-69-to-network-check-target-ip-10-0-129-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-69.ec2.internal uid: 66bcd7b6-5eb6-4a1b-9990-b5d4c221501c resourceVersion: "38553" uid: ebda671e-b8e5-4f3e-bcf8-525d9b0332cd spec: sourcePod: network-check-source-7d88cb55d8-sh76t targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T13:52:47Z" message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.082002ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:06:47Z" - latency: 2.066971ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:05:47Z" - latency: 2.008731ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:04:47Z" - latency: 2.230036ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:03:47Z" - latency: 2.060324ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:47Z" - latency: 2.179557ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:47Z" - latency: 2.178271ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:47Z" - latency: 2.915183ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:47Z" - latency: 2.083451ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:58:47Z" - latency: 2.387563ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:57:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:45:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-69-to-network-check-target-ip-10-0-131-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-69.ec2.internal uid: 66bcd7b6-5eb6-4a1b-9990-b5d4c221501c resourceVersion: "38551" uid: 22e121d0-7129-445f-8118-5a4d4f29de07 spec: sourcePod: network-check-source-7d88cb55d8-sh76t targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T13:52:47Z" message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.117636ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:06:47Z" - latency: 1.027768ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:05:47Z" - latency: 1.209312ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:04:47Z" - latency: 1.370771ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:03:47Z" - latency: 815.309µs message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:47Z" - latency: 1.111997ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:47Z" - latency: 1.407351ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:47Z" - latency: 2.541839ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:47Z" - latency: 776.324µs message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:58:47Z" - latency: 1.76991ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:57:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:45:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-69-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-69.ec2.internal uid: 66bcd7b6-5eb6-4a1b-9990-b5d4c221501c resourceVersion: "34903" uid: 53b9a010-4d68-40fd-b331-31fa8300ac24 spec: sourcePod: network-check-source-7d88cb55d8-sh76t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T13:51:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.683µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:03:47Z" - latency: 1.786444ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:03:47Z" - latency: 1.080444ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:47Z" - latency: 1.808262ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:02:47Z" - latency: 1.435378ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:47Z" - latency: 1.775738ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:01:47Z" - latency: 788.662µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:47Z" - latency: 1.771825ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:00:47Z" - latency: 1.486803ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:47Z" - latency: 2.854109ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T13:59:47Z" kind: List metadata: resourceVersion: ""