apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:26:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-24-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-24.ec2.internal uid: aee96cab-993e-4fd4-be1f-0cb56d92fdf2 resourceVersion: "48837" uid: 73513185-6f91-41a2-8a47-c96e78053a9a spec: sourcePod: network-check-source-989f8b8dc-wlvnt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T16:33:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.304314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:01:39Z" - latency: 1.128654ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:00:39Z" - latency: 1.174068ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:59:39Z" - latency: 896.411µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:58:39Z" - latency: 851.024µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:57:39Z" - latency: 780.522µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:56:39Z" - latency: 814.399µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:55:39Z" - latency: 1.486926ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:54:39Z" - latency: 855.909µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:53:39Z" - latency: 1.011418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:52:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:26:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-24-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-24.ec2.internal uid: aee96cab-993e-4fd4-be1f-0cb56d92fdf2 resourceVersion: "49687" uid: b7c616dd-e400-49d9-89bf-65a529caab01 spec: sourcePod: network-check-source-989f8b8dc-wlvnt targetEndpoint: a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T16:32:39Z" message: 'load-balancer-api-external: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 9.324395ms message: 'load-balancer-api-external: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:02:39Z" - latency: 6.792481ms message: 'load-balancer-api-external: resolved host name a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:02:39Z" - latency: 4.586324ms message: 'load-balancer-api-external: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:01:39Z" - latency: 7.070388ms message: 'load-balancer-api-external: resolved host name a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:01:39Z" - latency: 4.229806ms message: 'load-balancer-api-external: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:00:39Z" - latency: 7.467583ms message: 'load-balancer-api-external: resolved host name a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:00:39Z" - latency: 5.541055ms message: 'load-balancer-api-external: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:59:39Z" - latency: 6.439201ms message: 'load-balancer-api-external: resolved host name a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:59:39Z" - latency: 5.903959ms message: 'load-balancer-api-external: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:58:39Z" - latency: 7.125355ms message: 'load-balancer-api-external: resolved host name a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:58:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:26:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-24-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-24.ec2.internal uid: aee96cab-993e-4fd4-be1f-0cb56d92fdf2 resourceVersion: "49686" uid: 7a4928e2-f02a-41f4-ab22-a10837eb09b9 spec: sourcePod: network-check-source-989f8b8dc-wlvnt targetEndpoint: a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T16:32:39Z" message: 'load-balancer-api-internal: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.976976ms message: 'load-balancer-api-internal: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:02:39Z" - latency: 6.722167ms message: 'load-balancer-api-internal: resolved host name a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:02:39Z" - latency: 3.997478ms message: 'load-balancer-api-internal: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:01:39Z" - latency: 7.117941ms message: 'load-balancer-api-internal: resolved host name a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:01:39Z" - latency: 4.2421ms message: 'load-balancer-api-internal: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:00:39Z" - latency: 7.550933ms message: 'load-balancer-api-internal: resolved host name a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:00:39Z" - latency: 5.57447ms message: 'load-balancer-api-internal: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:59:39Z" - latency: 6.41334ms message: 'load-balancer-api-internal: resolved host name a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:59:39Z" - latency: 6.093567ms message: 'load-balancer-api-internal: tcp connection to a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:58:39Z" - latency: 7.154196ms message: 'load-balancer-api-internal: resolved host name a9e0ed3c2f2b94e39b4691f0bbe87ee3-51e034884aa3adfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:58:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:26:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-24-to-network-check-target-ip-10-0-128-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-24.ec2.internal uid: aee96cab-993e-4fd4-be1f-0cb56d92fdf2 resourceVersion: "48836" uid: f7fc5801-8082-4246-a951-29c77104034e spec: sourcePod: network-check-source-989f8b8dc-wlvnt targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T16:33:39Z" message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.071874ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:01:39Z" - latency: 2.078714ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:00:39Z" - latency: 1.964583ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:59:39Z" - latency: 1.900767ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:58:39Z" - latency: 1.802493ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:57:39Z" - latency: 1.738046ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:56:39Z" - latency: 1.861957ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:55:39Z" - latency: 2.320732ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:54:39Z" - latency: 1.939982ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:53:39Z" - latency: 1.970333ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:52:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:26:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-24-to-network-check-target-ip-10-0-136-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-24.ec2.internal uid: aee96cab-993e-4fd4-be1f-0cb56d92fdf2 resourceVersion: "48835" uid: 6cb2f23f-5ae9-4517-bf36-2c946aa2f8d5 spec: sourcePod: network-check-source-989f8b8dc-wlvnt targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T16:33:39Z" message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.426378ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:01:39Z" - latency: 2.267937ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:00:39Z" - latency: 2.234818ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:59:39Z" - latency: 2.138256ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:58:39Z" - latency: 2.057401ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:57:39Z" - latency: 1.92744ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:56:39Z" - latency: 2.071007ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:55:39Z" - latency: 2.034021ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:54:39Z" - latency: 1.785351ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:53:39Z" - latency: 2.352211ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:52:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:26:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-24-to-network-check-target-ip-10-0-138-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-24.ec2.internal uid: aee96cab-993e-4fd4-be1f-0cb56d92fdf2 resourceVersion: "48834" uid: 111f868e-ccb7-48a9-ac0f-a48357c57d0b spec: sourcePod: network-check-source-989f8b8dc-wlvnt targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T16:33:39Z" message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.051299ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:01:39Z" - latency: 874.777µs message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:00:39Z" - latency: 822.888µs message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:59:39Z" - latency: 1.057582ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:58:39Z" - latency: 1.235465ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:57:39Z" - latency: 820.466µs message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:56:39Z" - latency: 728.043µs message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:55:39Z" - latency: 732.118µs message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:54:39Z" - latency: 876.584µs message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:53:39Z" - latency: 1.540522ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:52:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:26:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-24-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-24.ec2.internal uid: aee96cab-993e-4fd4-be1f-0cb56d92fdf2 resourceVersion: "49685" uid: d0a476fd-4bb5-49de-b0b4-34f4bc06448c spec: sourcePod: network-check-source-989f8b8dc-wlvnt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T16:32:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.094075ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:02:39Z" - latency: 1.68458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T17:02:39Z" - latency: 870.523µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:01:39Z" - latency: 1.712662ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T17:01:39Z" - latency: 1.046012ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:00:39Z" - latency: 1.880086ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T17:00:39Z" - latency: 1.005898ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:59:39Z" - latency: 1.605602ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T16:59:39Z" - latency: 1.224488ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:58:39Z" - latency: 1.631723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T16:58:39Z" kind: List metadata: resourceVersion: ""