apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:46:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: a6c5107e-f16a-403d-be1a-6ff6c8cf7933 resourceVersion: "55004" uid: 033feef3-d1ba-4f69-98ff-c8d8766c019c spec: sourcePod: network-check-source-989f8b8dc-h7mt2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T23:53:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 770.057µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:20Z" - latency: 945.799µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:20Z" - latency: 1.266011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:20Z" - latency: 1.18905ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:20Z" - latency: 769.49µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:20Z" - latency: 1.027441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:16:20Z" - latency: 1.107865ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:15:20Z" - latency: 1.196283ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:14:20Z" - latency: 1.075681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:13:20Z" - latency: 986.922µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:12:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:46:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: a6c5107e-f16a-403d-be1a-6ff6c8cf7933 resourceVersion: "56066" uid: 6b01ef9f-b3d7-4239-9912-cfe5001cef6c spec: sourcePod: network-check-source-989f8b8dc-h7mt2 targetEndpoint: af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T23:52:20Z" message: 'load-balancer-api-external: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.385741ms message: 'load-balancer-api-external: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:20Z" - latency: 8.888914ms message: 'load-balancer-api-external: resolved host name af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:22:20Z" - latency: 5.170781ms message: 'load-balancer-api-external: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:20Z" - latency: 8.773942ms message: 'load-balancer-api-external: resolved host name af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:21:20Z" - latency: 3.618818ms message: 'load-balancer-api-external: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:20Z" - latency: 7.31749ms message: 'load-balancer-api-external: resolved host name af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:20:20Z" - latency: 5.604591ms message: 'load-balancer-api-external: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:20Z" - latency: 6.878892ms message: 'load-balancer-api-external: resolved host name af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:19:20Z" - latency: 4.804819ms message: 'load-balancer-api-external: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:20Z" - latency: 7.222009ms message: 'load-balancer-api-external: resolved host name af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:18:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:46:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: a6c5107e-f16a-403d-be1a-6ff6c8cf7933 resourceVersion: "56067" uid: bff6824f-32c3-4b90-b795-9ded1a8836ad spec: sourcePod: network-check-source-989f8b8dc-h7mt2 targetEndpoint: af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T23:52:20Z" message: 'load-balancer-api-internal: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.359204ms message: 'load-balancer-api-internal: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:20Z" - latency: 8.820723ms message: 'load-balancer-api-internal: resolved host name af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:22:20Z" - latency: 5.15673ms message: 'load-balancer-api-internal: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:20Z" - latency: 8.791848ms message: 'load-balancer-api-internal: resolved host name af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:21:20Z" - latency: 3.53078ms message: 'load-balancer-api-internal: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:20Z" - latency: 7.233867ms message: 'load-balancer-api-internal: resolved host name af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:20:20Z" - latency: 5.646218ms message: 'load-balancer-api-internal: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:20Z" - latency: 6.815273ms message: 'load-balancer-api-internal: resolved host name af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:19:20Z" - latency: 4.810097ms message: 'load-balancer-api-internal: tcp connection to af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:20Z" - latency: 7.148215ms message: 'load-balancer-api-internal: resolved host name af3a7c10ef04e463da4d3fd27f039cfd-2510d405aabe0d21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:18:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:46:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-network-check-target-ip-10-0-132-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: a6c5107e-f16a-403d-be1a-6ff6c8cf7933 resourceVersion: "55001" uid: e75056d1-9f3b-49f1-8764-843389088673 spec: sourcePod: network-check-source-989f8b8dc-h7mt2 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:53:20Z" message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.322605ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:20Z" - latency: 1.0521ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:20Z" - latency: 1.346552ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:20Z" - latency: 985.678µs message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:20Z" - latency: 1.011718ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:20Z" - latency: 1.213648ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:16:20Z" - latency: 891.479µs message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:15:20Z" - latency: 927.584µs message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:14:20Z" - latency: 1.088884ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:13:20Z" - latency: 1.315925ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:12:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:46:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-network-check-target-ip-10-0-133-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: a6c5107e-f16a-403d-be1a-6ff6c8cf7933 resourceVersion: "55002" uid: c7ceaa1a-e72d-45b0-b87f-affaeaf2dd26 spec: sourcePod: network-check-source-989f8b8dc-h7mt2 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:53:20Z" message: 'network-check-target-ip-10-0-133-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.669425ms message: 'network-check-target-ip-10-0-133-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:20Z" - latency: 1.937365ms message: 'network-check-target-ip-10-0-133-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:20Z" - latency: 2.013796ms message: 'network-check-target-ip-10-0-133-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:20Z" - latency: 1.807712ms message: 'network-check-target-ip-10-0-133-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:20Z" - latency: 1.673575ms message: 'network-check-target-ip-10-0-133-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:20Z" - latency: 2.031688ms message: 'network-check-target-ip-10-0-133-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:16:20Z" - latency: 1.819327ms message: 'network-check-target-ip-10-0-133-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:15:20Z" - latency: 1.848142ms message: 'network-check-target-ip-10-0-133-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:14:20Z" - latency: 1.775961ms message: 'network-check-target-ip-10-0-133-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:13:20Z" - latency: 2.003656ms message: 'network-check-target-ip-10-0-133-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:12:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:46:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-network-check-target-ip-10-0-135-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: a6c5107e-f16a-403d-be1a-6ff6c8cf7933 resourceVersion: "55003" uid: 793514d7-b2d8-46bb-b635-cb931c44d3ee spec: sourcePod: network-check-source-989f8b8dc-h7mt2 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:53:20Z" message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.480769ms message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:20Z" - latency: 2.250917ms message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:20Z" - latency: 2.242696ms message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:20Z" - latency: 2.256321ms message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:20Z" - latency: 2.162588ms message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:20Z" - latency: 2.179152ms message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:16:20Z" - latency: 2.008896ms message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:15:20Z" - latency: 1.834885ms message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:14:20Z" - latency: 2.19596ms message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:13:20Z" - latency: 2.368509ms message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:12:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:46:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: a6c5107e-f16a-403d-be1a-6ff6c8cf7933 resourceVersion: "56065" uid: d6db399d-afb2-404c-8544-5c894e511aba spec: sourcePod: network-check-source-989f8b8dc-h7mt2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T23:52:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 833.403µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:20Z" - latency: 1.896145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:22:20Z" - latency: 988.19µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:20Z" - latency: 1.763947ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:21:20Z" - latency: 971.126µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:20Z" - latency: 1.495925ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:20:20Z" - latency: 852.289µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:20Z" - latency: 1.741622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:19:20Z" - latency: 1.150952ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:20Z" - latency: 1.809557ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:18:20Z" kind: List metadata: resourceVersion: ""