apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T03:44:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-160-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-160.ec2.internal uid: 59e55c84-715f-4558-b3d9-c429135be9ee resourceVersion: "47530" uid: 253ee3db-fcc5-4eb7-9402-d494ca134b45 spec: sourcePod: network-check-source-869dcfcdcd-clzch targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T03:51:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.171194ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:12:14Z" - latency: 957.128µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:11:14Z" - latency: 1.0337ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:10:14Z" - latency: 803.925µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:09:14Z" - latency: 1.04429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:08:14Z" - latency: 754.391µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:07:14Z" - latency: 1.247752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:06:14Z" - latency: 1.24061ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:05:14Z" - latency: 949.722µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:04:14Z" - latency: 837.896µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:03:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T03:44:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-160-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-160.ec2.internal uid: 59e55c84-715f-4558-b3d9-c429135be9ee resourceVersion: "50269" uid: 145ce6fb-9978-47b3-aa26-1f06a3d916e9 spec: sourcePod: network-check-source-869dcfcdcd-clzch targetEndpoint: ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T03:50:14Z" message: 'load-balancer-api-external: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.982829ms message: 'load-balancer-api-external: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:14:14Z" - latency: 8.62901ms message: 'load-balancer-api-external: resolved host name ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T04:14:14Z" - latency: 4.325387ms message: 'load-balancer-api-external: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:13:14Z" - latency: 8.140825ms message: 'load-balancer-api-external: resolved host name ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T04:13:14Z" - latency: 5.009473ms message: 'load-balancer-api-external: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:12:14Z" - latency: 8.307121ms message: 'load-balancer-api-external: resolved host name ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T04:12:14Z" - latency: 3.863279ms message: 'load-balancer-api-external: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:11:14Z" - latency: 11.01498ms message: 'load-balancer-api-external: resolved host name ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T04:11:14Z" - latency: 4.26587ms message: 'load-balancer-api-external: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:10:14Z" - latency: 8.621594ms message: 'load-balancer-api-external: resolved host name ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T04:10:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T03:44:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-160-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-160.ec2.internal uid: 59e55c84-715f-4558-b3d9-c429135be9ee resourceVersion: "50270" uid: 0d64132d-b228-4bde-a79f-b3e2d3971c6e spec: sourcePod: network-check-source-869dcfcdcd-clzch targetEndpoint: ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T03:50:14Z" message: 'load-balancer-api-internal: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.658324ms message: 'load-balancer-api-internal: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:14:14Z" - latency: 8.67075ms message: 'load-balancer-api-internal: resolved host name ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T04:14:14Z" - latency: 4.294774ms message: 'load-balancer-api-internal: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:13:14Z" - latency: 8.221598ms message: 'load-balancer-api-internal: resolved host name ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T04:13:14Z" - latency: 3.587315ms message: 'load-balancer-api-internal: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:12:14Z" - latency: 8.271725ms message: 'load-balancer-api-internal: resolved host name ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T04:12:14Z" - latency: 3.157236ms message: 'load-balancer-api-internal: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:11:14Z" - latency: 11.106473ms message: 'load-balancer-api-internal: resolved host name ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T04:11:14Z" - latency: 4.266273ms message: 'load-balancer-api-internal: tcp connection to ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:10:14Z" - latency: 8.653458ms message: 'load-balancer-api-internal: resolved host name ad7f67ed051c740ad8a486941b6e9f40-265c47ba14adab2a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T04:10:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T03:44:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-160-to-network-check-target-ip-10-0-133-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-160.ec2.internal uid: 59e55c84-715f-4558-b3d9-c429135be9ee resourceVersion: "47528" uid: 303b4d49-bc49-43f2-a47a-053d6328ea52 spec: sourcePod: network-check-source-869dcfcdcd-clzch targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T03:51:14Z" message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.548733ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:12:14Z" - latency: 1.622513ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:11:14Z" - latency: 1.88573ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:10:14Z" - latency: 1.796498ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:09:14Z" - latency: 2.022315ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:08:14Z" - latency: 1.7765ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:07:14Z" - latency: 1.716536ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:06:14Z" - latency: 1.852308ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:05:14Z" - latency: 1.731641ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:04:14Z" - latency: 1.943437ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:03:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T03:44:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-160-to-network-check-target-ip-10-0-138-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-160.ec2.internal uid: 59e55c84-715f-4558-b3d9-c429135be9ee resourceVersion: "47527" uid: 20db194c-1373-44c1-948e-d80902d39918 spec: sourcePod: network-check-source-869dcfcdcd-clzch targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-13T03:51:14Z" message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 945.267µs message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:12:14Z" - latency: 921.784µs message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:11:14Z" - latency: 807.764µs message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:10:14Z" - latency: 1.015694ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:09:14Z" - latency: 804.142µs message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:08:14Z" - latency: 1.198603ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:07:14Z" - latency: 889.537µs message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:06:14Z" - latency: 1.315424ms message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:05:14Z" - latency: 873.058µs message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:04:14Z" - latency: 780.582µs message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:03:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T03:44:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-160-to-network-check-target-ip-10-0-141-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-160.ec2.internal uid: 59e55c84-715f-4558-b3d9-c429135be9ee resourceVersion: "47529" uid: 2ee27c03-7adb-4725-ac87-3543c7050b47 spec: sourcePod: network-check-source-869dcfcdcd-clzch targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-13T03:51:14Z" message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.236751ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:12:14Z" - latency: 2.151181ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:11:14Z" - latency: 2.221627ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:10:14Z" - latency: 2.222816ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:09:14Z" - latency: 2.36015ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:08:14Z" - latency: 2.214199ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:07:14Z" - latency: 2.384708ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:06:14Z" - latency: 2.61088ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:05:14Z" - latency: 2.022054ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:04:14Z" - latency: 2.359915ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:03:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T03:44:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-160-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-160.ec2.internal uid: 59e55c84-715f-4558-b3d9-c429135be9ee resourceVersion: "50268" uid: 9b8110fc-7980-4e14-8ea4-b56d1116b3da spec: sourcePod: network-check-source-869dcfcdcd-clzch targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T03:50:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.99µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:14:14Z" - latency: 1.833652ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T04:14:14Z" - latency: 853.126µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:13:14Z" - latency: 1.699762ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T04:13:14Z" - latency: 1.575981ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:12:14Z" - latency: 1.803681ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T04:12:14Z" - latency: 815.296µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:11:14Z" - latency: 2.182802ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T04:11:14Z" - latency: 919.262µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T04:10:14Z" - latency: 2.018054ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T04:10:14Z" kind: List metadata: resourceVersion: ""